coding for multiple versions of python
invalid at invalid
Fri Aug 14 16:09:35 CEST 2009
On 2009-08-14, Martin v. L?wis <martin at v.loewis.de> wrote:
>> I'm guessing I need to configure cvs to copy files to both
>> locations whenever I commit. Does that sound right? Is there a
>> better way I'm not thinking of?
Just use one set of source files.
> If the set of files doesn't change too often, you can use symlinks.
> That's how Debian currently installs Python packages for multiple
> versions on a single system.
> 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?
Grant Edwards grante Yow! I'm EMOTIONAL
at now because I have
visi.com MERCHANDISING CLOUT!!
More information about the Python-list