On Mon, Sep 20, 2010 at 14:28, Antoine Pitrou wrote:
> On Mon, 20 Sep 2010 09:31:45 -0500
> Tom Browder wrote:
>>
>> Can anyone explain the two different "default" installations I got?
>>
>> It seems to me I should force the Ubuntu-style installation by the
>> "--with-universal-archs=64-bit" con
On Mon, 20 Sep 2010 09:31:45 -0500
Tom Browder wrote:
>
> Can anyone explain the two different "default" installations I got?
>
> It seems to me I should force the Ubuntu-style installation by the
> "--with-universal-archs=64-bit" configure option, and I will try that
> on Debian while I await
On Mon, Sep 20, 2010 at 13:05, Terry Reedy wrote:
> On 9/20/2010 10:31 AM, Tom Browder wrote:
> ...
>>
>> I see that the configure file has some architecture choices
>> (--with-universal-archs=ARCH) but no explanation about the
>> consequences.
>>
>> Can anyone explain the two different "default"
On Mon, Sep 20, 2010 at 13:05, Terry Reedy wrote:
> On 9/20/2010 10:31 AM, Tom Browder wrote:
> ...
>>
>> I see that the configure file has some architecture choices
>> (--with-universal-archs=ARCH) but no explanation about the
>> consequences.
>>
>> Can anyone explain the two different "default"
On 20 Sep, 2010,at 04:31 PM, Tom Browder wrote:Continuing on with investigating Python 2.7 build problems, one
problem I just discovered is a different installation on one 64-bit
system (Debian Lenny) versus another (Ubuntu 10.04.1 LTS).
I used gcc-4.5.1 on both systems, with no *PY* environment
On 9/20/2010 10:31 AM, Tom Browder wrote:
...
I see that the configure file has some architecture choices
(--with-universal-archs=ARCH) but no explanation about the
consequences.
Can anyone explain the two different "default" installations I got?
At the moment, this appears to be question abou
On Mon, Sep 20, 2010 at 10:12, Ronald Oussoren wrote:
>
>
> On 20 Sep, 2010,at 04:31 PM, Tom Browder wrote:
>
> Continuing on with investigating Python 2.7 build problems, one
> problem I just discovered is a different installation on one 64-bit
> system (Debian Lenny) versus another (Ubuntu 10.0
Continuing on with investigating Python 2.7 build problems, one
problem I just discovered is a different installation on one 64-bit
system (Debian Lenny) versus another (Ubuntu 10.04.1 LTS).
I used gcc-4.5.1 on both systems, with no *PY* environment variables set.
On Debian I got two directories:
Le vendredi 17 septembre 2010 00:09:09, Tom Browder a écrit :
> I did, and eventually discovered the problem: I tried to "nosy" Barry
> as requested by adding his e-mail address, but that causes an error in
> the tracker. After I finally figured that out, I successfully entered
> the original bug
USAOn Thu, Sep 16, 2010 at 16:36, Victor Stinner
wrote:
> Le jeudi 16 septembre 2010 23:10:22, Tom Browder a écrit :
>> I'm attempting to file a bug but keep getting:
>
> File another bug about this bug!
I did, and eventually discovered the problem: I tried to "nosy" Barry
as requested by adding
Le jeudi 16 septembre 2010 23:10:22, Tom Browder a écrit :
> I'm attempting to file a bug but keep getting:
File another bug about this bug!
--
Victor Stinner
http://www.haypocalc.com/
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.pytho
I'm attempting to file a bug but keep getting:
An error has occurred
A problem was encountered processing your request. The tracker
maintainers have been notified of the problem.
-Tom
Thomas M. Browder, Jr.
Niceville, Florida
USA
___
Python-Dev mailin
On Sep 16, 2010, at 02:56 PM, Tom Browder wrote:
>On Thu, Sep 16, 2010 at 14:36, Barry Warsaw wrote:
>> When you say "installed python 2.7" do you mean the one you
>> installed to /usr/local from a from-source build, or something else
>> (e.g. a Python 2.7 package perhaps)?
>
>It was the released
On Thu, Sep 16, 2010 at 14:36, Barry Warsaw wrote:
> On Sep 16, 2010, at 01:41 PM, Tom Browder wrote:
>
>>I am trying to rebujild the 2.7 maintenance branch and get this error
>>on Ubuntu 10.04.1 LTS:
>
> I just tried this on my vanilla 10.04.1 system. I checked out release27-maint
> ran configur
On Sep 16, 2010, at 01:41 PM, Tom Browder wrote:
>I am trying to rebujild the 2.7 maintenance branch and get this error
>on Ubuntu 10.04.1 LTS:
I just tried this on my vanilla 10.04.1 system. I checked out release27-maint
ran configure && make. It built without problem.
>XXX lineno: 743, opcod
Please file the bug and it can be discussed further there.
On Thu, Sep 16, 2010 at 12:05, Tom Browder wrote:
> On Thu, Sep 16, 2010 at 13:48, Brett Cannon wrote:
>> Go ahead and file the bug, but chances are that some other installed
>> Python is executing the code and picking up the .pyc files
On Thu, Sep 16, 2010 at 13:48, Brett Cannon wrote:
> Go ahead and file the bug, but chances are that some other installed
> Python is executing the code and picking up the .pyc files which have
> bytecode new to Python 2.7.
But isn't that a problem with the build system? It seems to me it
should
Go ahead and file the bug, but chances are that some other installed
Python is executing the code and picking up the .pyc files which have
bytecode new to Python 2.7.
On Thu, Sep 16, 2010 at 11:41, Tom Browder wrote:
> I am trying to rebujild the 2.7 maintenance branch and get this error
> on Ubu
I am trying to rebujild the 2.7 maintenance branch and get this error
on Ubuntu 10.04.1 LTS:
XXX lineno: 743, opcode: 0
Traceback (most recent call last):
File "/usr/local/src/python-2.7-maint-svn/Lib/site.py", line 62, in
import os
File "/usr/local/src/python-2.7-maint-svn/Lib/os.py", line
19 matches
Mail list logo
