Re: What should we do now?

[William Famy <william.famy@noos.fr>]

Neil Schemenauer wrote:
___________________________
[wf:]
good morning
This is my first mail to this mailing list.
I use woody and potato. I use python for my coding. I am waiting to python-pyqt
under woody :-)



>
> > The problems with using "#!/usr/bin/python1.5" is threefold: first, it
> > makes dependencies that much more complicated: *all* python scripts have
> > to depend on versioned modules in every way
>
> This has nothing to do with using "/usr/bin/python(X.Y)?" vs.
> "/usr/bin/env python(X.Y)?".  If you want to use the latest packaged
> version of Python you should use "/usr/bin/python"

______________________________
[wf:]

This problem looks like the source.list with apt-get.
if you whant to use the stable version actualy you avec 2 choices.  stable or
potato
if you choose potato you are sure not to upgrade to woody when it(he) will
become stable.
if you choose potato you are sur not to upgrade.

some peaple prefere to upgrade other not to. but theire are one thing sur when
woody will become stable the simbolic lync in the ftp will change.

so why not to do the same thing with python. python package is the last one (2.2
for exemple) with name python and python2_2 . If i need python1.5: apt-get
install python1_5

now last python is python 3.0 (only for exemple the number is false ) if you
have choose the /usr/bin/python you will use python30 if /usr/bin/python(X.Y)
you will use pythonx_y.

now if we change the actual policy to have the last python in python pacquage
this may change script using python1.5 witch do not work unde thon2.2 why not
changing the header #!/usr/bin/python to #!/usr/bin/python1_5 with a script
before upgrading to the new policy?

I hope you can understand me because of my poor english.

William


>
>
> > If you install new versions of standard tools in /usr/local you have
> > to be careful. This applies to a hypothetical /usr/local/bin/dpkg, or
> > a /usr/local/bin/sed, or whatever. Going out of your way to make sure
> > it doesn't apply to a /usr/local/bin/python seems to this observer a
> > complete waste of time.
>
> The effort involved is small.  Use "/usr/bin/python" instead of
> "/usr/bin/env python".  Use "/usr/bin/pythonX.Y" instead of
> "/usr/bin/env pythonX.Y".
>
>   Neil
>
> --
> To UNSUBSCRIBE, email to debian-python-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

--
                            \\\|///
                          \\  - -  //
                           (  @ @  )
+-----------------------oOOo-(_)-oOOo--------------------+
|Famy William  36 avenue des barattes 74000 Annecy France|
|email:william.famy@noos.fr  william.famy@laposte.net    |
+--------------------------------Oooo--------------------+
                           oooO   (   )
                          (   )    ) /
                           \ (    (_/
                            \_)