Re: Status report on python2 transition
On 12 Jul 2001, Jérôme Marant wrote:
> Bruce Sass <bsass@freenet.edmonton.ab.ca> writes:
>
> > Surely adopting a convention of...
> >
> > #!/usr/bin/env python[major.minor]
> >
> > ...is preferable.
> >
> > It does the same thing without additional runtime overhead and
> > without creating a class of Debian-specific Python programs.
>
> I object to this. It make scripts not portable to other systems as
> it currently does with current python 2.0 scripts in Debian.
> We shall end up with this trick as soon as possible.
How not portable?
Any build of Python I have done installs both:
bin/python<major>.<minor>
and
bin/python
as hardlinks...
...calling "python-wrapper" to execute the program is definately not
portable to other systems.
- Bruce
Reply to: