coding for multiple versions of python
"Martin v. Löwis"
martin at v.loewis.de
Sat Aug 15 00:40:56 CEST 2009
>> Specifically, put the source code into /net/source/python/foo/*.py.
>> Then, on each system, put symlinks to all .py files into
>> lib/site-packages/foo. Then Python will place the .pyc files next
>> to the symlinks, not next to the actual .py files.
> Why would he need two sets of .py files?
As Dave explains:
So that the Python 2.4 installation on HP can write its own .pyc
files on disk next to the source files, and Python 2.6 can write
its .pyc files next to the sources on Linux.
More information about the Python-list