[Python-Dev] Compatibility between Python 2.3.x and Python 2.4.x
Hi, I'm involved with the team that's working towards installing Python 2.4.x as part of a future release of the Solaris O/S. We currently have Python 2.3.x installed. We are trying to determine just how compatible these two release are (at both the binary and source levels). In other words, with Python 2.3.x .py, .pyc and .pyo files work correctly with Python 2.4.x ? Can somebody point me at this information please? Thanks. -- Rich Burridge Email: [EMAIL PROTECTED] Sun Microsystems Inc. (MPK14-260), Phone: +1.650.786.5188 4150 Network Circle,AIM/YAHOO: RicBurridge Santa Clara, CA 95054 Blog: http://blogs.sun.com/richb ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Compatibility between Python 2.3.x and Python 2.4.x
Hi Neal, Ray, Neal wrote: > The binary versions (.pyc and .pyo) are not compatible, their magic > number is different. I don't know the details, but if you want to > investigate yourself. Get a CVS version, cd python/dist/src ; cvs > diff -r r23 -r r24 Python/import.c > > That shows the magic number changing. You will need to read CVS logs > to figure out why. It's possible the numbers don't really *need* to > change. I see two comments in the logs are: > > * Bump the magic number to avoid sharing bytecode between 2.3 and 2.4. > Revise the long comment that explained details of the magic number > in gory detail. > > * With Guido's okay, bumped up the magic number so that this patch gets > widely exercised before the alpha goes out. > > There are other patches which may have bumped the magic number for > other reasons. Thanks! >>Can somebody point me at this information please? > And I forgot to give you this link: > http://docs.python.org/whatsnew/whatsnew24.html That lists the changes. It's not clear (at least to me) whether these changes are incompatible. > BTW, this list probably isn't the best place to post this question. > comp.lang.python (python-list@python.org) is generally preferred for > details about implementation. Understood. I'll try there tomorrow. > If you are really interested in finding out more about Python, perhaps > you can come to the BayPIGGIES (Python Users Group) meeting at Google > tonight (7.30pm) in Mt. View. Contact me off-list if you want more > info. Thanks for the pointer. Unfortunately I have other plans for tonight. Raymond wrote: > The new LIST_APPEND opcode won't run on Py2.3. It was more a case of wondering whether Python 2.3.x .py, .pyo, .pyc files should "just work" with the Python 2.4.x run-time environment. We are not too concerned with 2.4.x files working with the Python 2.3.x runtime. This sort of binary incompatibly is common. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] vendor-packages directory
Hi, Recently I asked about the inclusion of a "vendor-packages" directory for Python on the Python mailing list. See the thread started at: http://mail.python.org/pipermail/python-list/2005-September/300029.html for the full reasoning behind this request, and the replies I received. I then approached Guido for his take on this suggestion. He recommended I submit the patch to the Python patch manager at SourceForge, and inform the folks on python-dev mailing list. So I have. You can find the patch submission at: http://sourceforge.net/tracker/index.php?func=detail&aid=1298835&group_id=5470&atid=305470 Thanks. -- Rich Burridge Email: [EMAIL PROTECTED] Sun Microsystems Inc. (MPK14-260), Phone: +1.650.786.5188 4150 Network Circle,AIM/YAHOO: RicBurridge Santa Clara, CA 95054 Blog: http://blogs.sun.com/richb ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] vendor-packages directory
Phillip J. Eby wrote: >> Recently I asked about the inclusion of a "vendor-packages" >> directory for Python on the Python mailing list. >> >> See the thread started at: >> >> >> http://mail.python.org/pipermail/python-list/2005-September/300029.html >> >> for the full reasoning behind this request, and the replies >> I received. > > > I'm with Terry on this, it needs a better rationale. Why can't you just > add a .pth file to the site-packages directory? It seems that would > address the issue nicely. > > (See http://docs.python.org/lib/module-site.html for documentation of > the .pth mechanism, which would let you implement a separate > vendor-packages directory without modifying Python, and would still > allow local overrides of your vendor packages.) I understand how .pth files work. The rationale for requesting the "vendor-packages" approach, is that Python files, as supplied by the vendor (Sun, Apple, RedHat ...) with their operating system software, should go in a totally separate base directory, to differentiate them from Python files installed specifically at one site. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
