Re: Packaging, supporting both 2.1 and 2.2

[Moshe Zadka <m@moshez.org>]

On Wed, 22 May 2002, Bastian Kleineidam <reflexionsniveau@web.de> wrote:

> On Wed, May 22, 2002 at 12:09:11PM -0000, Moshe Zadka wrote:
> > > a) python2.1-foo: python foo.py module for 2.1
> Depends: python2.1
> 
> > > b) python2.2-foo: python foo.py module for 2.2
> Depends: python2.2

Of course
You do not understand me.

> > > c) python-foo: /usr/bin/foo binary with #!/usr/bin/python
> > >    Depends: python2.1-foo | python2.2-foo
> >=20
> > Doesn't work.
> > What if the user installed python2.2-foo but /usr/bin/python
> > is /usr/bin/python2.1, or vice versa?
> Ah, I forgot: python2.x-foo has to depend on python2.x package.

So what?

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.


-- 
To UNSUBSCRIBE, email to debian-python-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org