- Original Message -
> From: Oscar Benjamin
> To: Steven D'Aprano
> Cc: "Tutor@python.org"
> Sent: Wednesday, September 25, 2013 11:58 AM
> Subject: Re: [Tutor] ImportError: No module named '_sysconfigdata_m'
>
> On 25 September 2013 00:
On 25 September 2013 00:25, Steven D'Aprano wrote:
> On Tue, Sep 24, 2013 at 01:33:23PM +0100, Oscar Benjamin wrote:
>
>> If you want to mess with your system 'sudo rm -rf' is definitely the
>> way to go. Don't bother reporting this as a bug since you've
>> *definitely* voided the warranty (that y
On 24/09/13 19:22, Prasad, Ramit wrote:
Why uninstall via Synaptic? If he manually installed from source
He installed 3.3 from source.
3.2 was already there courtesy of Mint.
Therefore, he should have uninstalled 3.2 via Synaptic.
Reinstalling 3.2 via synaptic and then uninstalling it,
may cl
On Tue, Sep 24, 2013 at 06:20:37AM -0700, Albert-Jan Roskam wrote:
> > If you want to mess with your system 'sudo rm -rf' is definitely the
> > way to go. Don't bother reporting this as a bug since you've
> > *definitely* voided the warranty (that your free software didn't come
> > with).
>
> And
On Tue, Sep 24, 2013 at 01:33:23PM +0100, Oscar Benjamin wrote:
> If you want to mess with your system 'sudo rm -rf' is definitely the
> way to go. Don't bother reporting this as a bug since you've
> *definitely* voided the warranty (that your free software didn't come
> with).
I first read that
On Tue, Sep 24, 2013 at 1:42 PM, Albert-Jan Roskam wrote:
> I did not use "--prefix". I just reinstalled Python 3.2 via the package
> manager, and
> it everything is working again --THANK YOU ALL!
>
> antonia@antonia-HP-2133 ~ $ which python3.3
> /usr/local/bin/python3.3
This is the version you
Alan Gauld wrote:
>
> On 24/09/13 14:20, Albert-Jan Roskam wrote:
>
> >> "python", python 2.7 fires up. Also, I entirely removed python 3.2
> >> (sudo rm -rf $(which python3.2), IIRC), which came with Linux Mint.
>
> That's almost never the right way to remove a package that came with the OS.
>
- Original Message -
> From: eryksun
> To: Albert-Jan Roskam
> Cc: Python Mailing List
> Sent: Tuesday, September 24, 2013 5:25 PM
> Subject: Re: [Tutor] ImportError: No module named '_sysconfigdata_m'
>
> On Tue, Sep 24, 2013 at 8:18 AM, Albert-Jan
On 24 September 2013 16:25, eryksun wrote:
>
> The "command-not-found" script uses 3.x on Ubuntu/Mint:
>
> http://packages.ubuntu.com/saucy/command-not-found
>
> It's 2.x on Debian, but thankfully it isn't part of the default install.
I actually find it useful. I wish I could get the same for imp
On 24/09/13 14:20, Albert-Jan Roskam wrote:
"python", python 2.7 fires up. Also, I entirely removed python 3.2
(sudo rm -rf $(which python3.2), IIRC), which came with Linux Mint.
That's almost never the right way to remove a package that came with the OS.
You should have used the package mana
On Tue, Sep 24, 2013 at 8:18 AM, Albert-Jan Roskam wrote:
> am using Linux Mint XFCE. I have to look up the exact version number. I
> recently
> downloaded and installed Python 3.3. I downloaded the tarball
> and compiled, tested and installed everything as per instructions in the
> (readme? inst
On Tue, Sep 24, 2013 at 2:25 AM, Steven D'Aprano wrote:
> Unless this was at the Python prompt, it's not really a Python question.
> It's a question about your Linux installation, and why "gigt" ends up
> calling Python. Start with:
>
> man gigt
>
> which gigt
>
> locate gigt
>
As far as I know
On 24/9/2013 09:20, Albert-Jan Roskam wrote:
> I just didn't want to have more versions than I actually need. Python 3.3 is
> closer to Python 2.7 than earlier Python 3 versions.
> I am now planning to reinstall Python 3.2 using "sudo apt-get install python3"
I suspect you'd be better off tryin
- Original Message -
> From: Oscar Benjamin
> To: Albert-Jan Roskam
> Cc: Python Mailing List
> Sent: Tuesday, September 24, 2013 2:33 PM
> Subject: Re: [Tutor] ImportError: No module named '_sysconfigdata_m'
>> I was planning to reply after I h
On 24/9/2013 08:18, Albert-Jan Roskam wrote:
>, everything appears to work normally (phew) If I type "python", python
> 2.7 fires up. Also, I entirely removed python 3.2 (sudo rm -rf $(which
> python3.2), IIRC), which came with Linux Mint.
Right there is your mistake.
>
>
> OoooOoOoh, I h
On 24 September 2013 13:18, Albert-Jan Roskam wrote:
>>
>>On 23 September 2013 20:28, Albert-Jan Roskam wrote:
>>> Hi,
>>>
>>> I just wanted to type "git status" in my Linux terminal but I made a typo
>>> and I got a long Python 3.3 traceback message. Just curious: What does it
>>> mean?
>>>
>>>
> From: Oscar Benjamin
>To: Albert-Jan Roskam
>Cc: Python Mailing List
>Sent: Tuesday, September 24, 2013 1:47 PM
>Subject: Re: [Tutor] ImportError: No module named '_sysconfigdata_m'
>
>
>On 23 September 2013 20:28, Albert
On 23 September 2013 20:28, Albert-Jan Roskam wrote:
> Hi,
>
> I just wanted to type "git status" in my Linux terminal but I made a typo
> and I got a long Python 3.3 traceback message. Just curious: What does it
> mean?
>
> gigt status
> Traceback (most recent call last):
> File "/usr/lib/pytho
On Mon, Sep 23, 2013 at 12:28:10PM -0700, Albert-Jan Roskam wrote:
> Hi,
>
> I just wanted to type "git status" in my Linux terminal but I made a
> typo and I got a long Python 3.3 traceback message. Just curious: What
> does it mean?
Unless this was at the Python prompt, it's not really a Pyth
On Mon, Sep 23, 2013 at 3:28 PM, Albert-Jan Roskam wrote:
> I just wanted to type "git status" in my Linux terminal but I made a typo
> and I got a long Python 3.3 traceback message. Just curious: What does it
> mean?
>
> gigt status
> Traceback (most recent call last):
"gigt"? Why is that trying
Hi,
I just wanted to type "git status" in my Linux terminal but I made a typo and I
got a long Python 3.3 traceback message. Just curious: What does it mean?
gigt status
Traceback (most recent call last):
File "/usr/lib/python3.3/site.py", line 631, in
main()
File "/usr/lib/python3.3/si
21 matches
Mail list logo
