Le dimanche 29 mars 2009 à 20:46 +0200, Karsten Hilbert a écrit : > 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...
I don’t think this is possible. First of all, python-support has not changed at all its behavior on this matter. However the document you read makes it clear that it is better, for python applications, to put the (private) modules in a private location. Both installation schemes have been available for a long time, and this issue is orthogonal to the bug I initially reported. If GNUmed uses #!/usr/bin/python as a shebang, it will not be possible to run it with two different Python versions on the same machine. Only the default one applies. If the default version changes, all .pyc files will be regenerated and they will still work fine. If GNUmed uses #!/usr/bin/python2.X as a shebang, only one version will be available at all times. In this case you should always call "dh_pysupport -V2.X" so that it knows for which Python version these files are. Cheers, -- .''`. Debian 5.0 "Lenny" has been released! : :' : `. `' Last night, Darth Vader came down from planet Vulcan and told `- me that if you don't install Lenny, he'd melt your brain.
signature.asc
Description: Ceci est une partie de message numériquement signée
