[Python-Dev] 2.5.2 schedule?

2007-07-06 Thread Jack Howarth
I was wondering if there is a schedule for the release of a python 2.5.2 update? I don't see anything like that on the www.python.org web site. Thanks in advance for any information. Jack ___ Python-Dev mailing list Python-Dev@python.org

Re: [Python-Dev] python, lipo and the future?

2006-09-17 Thread Jack Howarth
Martin, I believe if you use the Xcode project management the Universal binary creation is automated. Currently they support the i386/ppc binaries but once Leopard comes out you will see i386/x86_64/ppc/ppc64 binaries for shared libraries. Jack _

[Python-Dev] python, lipo and the future?

2006-09-17 Thread Jack Howarth
I am curious if there are any plans to support the functionality provided by lipo on MacOS X to create a python release that could operate at either 32-bit or 64-bit on Darwin ppc and Darwin intel? My understanding was that the linux developers are very interested in lipo as well as an approach

Re: [Python-Dev] gcc 4.2 exposes signed integer overflows

2006-08-27 Thread Jack Howarth
I believe some of the others here might be interested in some other postings on the gcc mailing list regarding this issue (which weren't cross-posted here)... http://gcc.gnu.org/ml/gcc/2006-08/msg00516.html http://gcc.gnu.org/ml/gcc/2006-08/msg00517.html It makes clear that the impact of this

Re: [Python-Dev] gcc 4.2 exposes signed integer overflows

2006-08-26 Thread Jack Howarth
Guido, You'll never win that argument with the gcc developers. If you rely on undefined behavior in the c language standard, they have in the past, and will continue to, feel free to ignore those cases. If you plan on ignoring this issue, just be prepared to see a testcase failure in the pytho

[Python-Dev] gcc 4.2 exposes signed integer overflows

2006-08-26 Thread Jack Howarth
I discovered that gcc 4.2 exposes a flaw with signed integer overflows in python. This bug and the necessary fix has been discussed in detail on the gcc mailing list. I have filed a detailed bug report and the recommended patch proposed by the gcc developers. This problem should be addressed