On Wed, May 22, 2002 at 01:09:02PM -0000, Moshe Zadka wrote: > Situation: > python2.1, python2.2, python2.2-foo and python-foo are all installed. > python2.1 is the default. > All dependancies are resolved, right? > > #!/usr/bin/python > import foo > > equivalent to > > #!/usr/bin/python2.1 > import foo > > But, alas, python2.1's search path *does not contain* foo.py > ImportError: foo not found. Ok, thats a problem. There is no way out for this; you'd have to have two binaries.
To sum it up, I would do the following: Provide library packages: python2.1-foo, python2.2-foo. Provide *one* binary package for the default python version: python-foo (or just foo). This way you have the best of all worlds: developers using the library can test and code for all versions they like. People who use the binary install it and run it. Remember that most users dont care about versions, they install and click yes for any dependencies. Greetings from Munich, Bastian
pgpiynNHuxFJj.pgp
Description: PGP signature
