Karsten Hilbert wrote: >> You're missing a 'export' before setting the variable (or call python in >> the >> same line you set it). > > Ah, thanks. Emilio, you are clearly a better expert on > packaging Python code under Debian than me :-)
That was shell ;) >>> I really wonder how this new python-support stuff >>> really works. It installs *.pyc files in the same location as the >>> *.py files - how can this work for different Python versions? >> Because different versions don't break the syntax (at least AFAIK), so if >> your >> program works with Python 2.4, it will work with 2.5 and 2.6 too. > > I believe Andreas was wondering about the pre-compiled pyc files being > installed alongside the py files. If they are stored there they can > only be precompiled by one particular Python version at a time. This made > us wonder what, for example, happens if user A runs GNUmed with Python > 2.5 at the same time that user B runs GNUmed with Python 2.6 on the same > machine... In that case the .pyc files won't be loaded, but the .py ones, I guess (please somebody correct me if I'm wrong). Nothing to worry about as people will usually be using the default interpreter. >> You don't need it, you can remove it (I've seen you've added it back). > That was one of my ill-fated suggestions - it would have worked but it > is clearly better if things work without it. That would defeat the purpose of placing the modules in a private location, so yes, better to remove it :) Cheers, Emilio
signature.asc
Description: OpenPGP digital signature
