About Python 2.7
Hello, Python 2.7 is available in the Experimental repository, and I use it as the default Python interpreter. All modules and software I use works Python 2.7, but, modules and libraries installed with aptitude are installed for Python 2.6, and I have to update the PYTHONPATH variable to use them. Is it currently planned to fix that? Best regards, ProgVal -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktim51bi6arc7qaht2udw42nht_yh8bfcxqtjr...@mail.gmail.com
Re: About Python 2.7
On Friday, March 04, 2011 08:30:02 am ProgVal wrote: Hello, Python 2.7 is available in the Experimental repository, and I use it as the default Python interpreter. All modules and software I use works Python 2.7, but, modules and libraries installed with aptitude are installed for Python 2.6, and I have to update the PYTHONPATH variable to use them. Is it currently planned to fix that? Yes. We're waiting on some of the post-squeeze release toolchain updates to get done and python2.7 doesn't build on all architectures. Once those are dealt with it will go into Unstable and will become a supported Python version (timing may also depend on release team clearance if there are other transitions to consider). Scott K -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201103040835.09159.deb...@kitterman.com
Re: request to join a team
[Tiago Saboga, 2011-03-04] I'd like start helping the debian python community too. I wonder if there is a list of help-needing packages, or recommendations for beginners to help with debian python. I don't want to package new modules, as I see we already have some trouble with the existing ones. I don't mind triaging bugs, or making trivial tasks, if they are useful. Any ideas? If you can, join #debian-python IRC channel on OFTC network, various problems are mentioned there from time to time. Current /topic contains these links: http://deb.li/pybugs http://deb.li/py27 http://deb.li/py26 If you know how to fix one of those bugs or at least want to try to fix one, let us know on the channel. -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110304135005.gt30...@piotro.eu
Re: request to join a team
On Fri, Mar 4, 2011 at 10:50 AM, Piotr Ożarowski pi...@debian.org wrote: [Tiago Saboga, 2011-03-04] I'd like start helping the debian python community too. I wonder if there is a list of help-needing packages, or recommendations for beginners to help with debian python. I don't want to package new modules, as I see we already have some trouble with the existing ones. I don't mind triaging bugs, or making trivial tasks, if they are useful. Any ideas? If you can, join #debian-python IRC channel on OFTC network, various problems are mentioned there from time to time. I have never been able to follow irc for more than a week. I'll try again, let's see if I can handle it now. Current /topic contains these links: http://deb.li/pybugs http://deb.li/py27 http://deb.li/py26 If you know how to fix one of those bugs or at least want to try to fix one, let us know on the channel. Great! I'll hve a look at these asap and come back. Cheers, Tiago. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimufpm+xpkpro4m+b13x6uf7fjufduh2g9cy...@mail.gmail.com
shebang lines for Python scripts
So I know many of you are on python-dev, so you might have seen this come up, but traffic there can be pretty heavy at times. Upstream Python recommends that the shebang line for scripts should be #!/usr/bin/env python however, this should only apply to *developer* packages, not operating system packages. Doing the above in packages provided by the distro can cause those scripts to break, if say a user installs their own Python sooner in $PATH, and which is not compatible with the script. It's also unnecessary for distros because we should know exactly which version of Python our scripts work with. And finally, setuptools will rewrite the shebang line when it installs scripts (FSVO 'setuptools' ;). There's about two such scripts in /usr/bin on my Squeeze machine. Debian policy should be clear that system installed Python scripts should have a shebang line hardcoded to a Python executable. Whether that should be /usr/bin/python, /usr/bin/python2, /usr/bin/pythonX.Y or something else is a different discussion. ;) Personally /usr/bin/python seems fine to me for now. -Barry signature.asc Description: PGP signature
Re: About Python 2.7
On Fri, Mar 4, 2011 at 14:35, Scott Kitterman deb...@kitterman.com wrote: On Friday, March 04, 2011 08:30:02 am ProgVal wrote: Hello, Python 2.7 is available in the Experimental repository, and I use it as the default Python interpreter. All modules and software I use works Python 2.7, but, modules and libraries installed with aptitude are installed for Python 2.6, and I have to update the PYTHONPATH variable to use them. Is it currently planned to fix that? Yes. We're waiting on some of the post-squeeze release toolchain updates to get done is there some toolchain changes preventing python2.7 upload? can we have additional details about this waiting period? and python2.7 doesn't build on all architectures. Doesn't experimental provide a good testbed to fix those build issues? Once those are dealt with it will go into Unstable and will become a supported Python version (timing may also depend on release team clearance if there are other transitions to consider). Was elease team contacted about the upcoming transition, in order to have a preventive evaluation and possible ack? Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktinkabsxjfdhctw1tfbinezje5a8rc7nzdzdo...@mail.gmail.com
Re: shebang lines for Python scripts
On Friday, March 04, 2011 01:23:40 pm Barry Warsaw wrote: So I know many of you are on python-dev, so you might have seen this come up, but traffic there can be pretty heavy at times. Upstream Python recommends that the shebang line for scripts should be #!/usr/bin/env python however, this should only apply to *developer* packages, not operating system packages. Doing the above in packages provided by the distro can cause those scripts to break, if say a user installs their own Python sooner in $PATH, and which is not compatible with the script. It's also unnecessary for distros because we should know exactly which version of Python our scripts work with. And finally, setuptools will rewrite the shebang line when it installs scripts (FSVO 'setuptools' ;). There's about two such scripts in /usr/bin on my Squeeze machine. Debian policy should be clear that system installed Python scripts should have a shebang line hardcoded to a Python executable. Whether that should be /usr/bin/python, /usr/bin/python2, /usr/bin/pythonX.Y or something else is a different discussion. ;) Personally /usr/bin/python seems fine to me for now. -Barry Currently Python policy says: 1.4.2. Interpreter Location --- The preferred specification for the Python interpreter is `/usr/bin/python' or `/usr/bin/pythonX.Y'. This ensures that a Debian installation of python is used and all dependencies on additional python modules are met. If a maintainer would like to provide the user with the possibility to override the Debian Python interpreter, he may want to use `/usr/bin/env python' or `/usr/bin/env pythonX.Y'. However this is not advisable as it bypasses Debian's dependency checking and makes the package vulnerable to incomplete local installations of python. Is that strong enough? Scott K -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201103041415.21944.deb...@kitterman.com
Re: shebang lines for Python scripts
On Mar 04, 2011, at 02:15 PM, Scott Kitterman wrote: Currently Python policy says: 1.4.2. Interpreter Location --- The preferred specification for the Python interpreter is `/usr/bin/python' or `/usr/bin/pythonX.Y'. This ensures that a Debian installation of python is used and all dependencies on additional python modules are met. If a maintainer would like to provide the user with the possibility to override the Debian Python interpreter, he may want to use `/usr/bin/env python' or `/usr/bin/env pythonX.Y'. However this is not advisable as it bypasses Debian's dependency checking and makes the package vulnerable to incomplete local installations of python. Is that strong enough? It's good, but not quite strong enough, because it doesn't give me clear guidance on what to do when I find a script with a /usr/bin/env shebang line. How would I know whether it's a deliberate use, or a bug? Or should I just file a bug on the offending packages and let the maintainer sort it out? Cheers, -Barry signature.asc Description: PGP signature
Re: shebang lines for Python scripts
any objections to change all shebangs (that do not match /usr/bin/python\d(\.\d+) but do math .+python.* regexp) to /usr/bin/python¹ in dh_python2 and to /usr/bin/python3 in dh_python3? (+ an option to disable this behaviour in both helpers) if yes, should options (-OO, etc.) be removed as well? [¹] or /usr/bin/python2, depends on PEP 394 status -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110304222346.gu30...@piotro.eu
Re: shebang lines for Python scripts
Hi Piotr (2011.03.05_00:23:46_+0200) any objections to change all shebangs (that do not match /usr/bin/python\d(\.\d+) but do math .+python.* regexp) to /usr/bin/python¹ in dh_python2 and to /usr/bin/python3 in dh_python3? Grumble. I quite like being able to use light (not --no-site-packages) virtualenvs for development, and being able to execute things like unit2, twistd, trial, or nose inside the virtualenv. But I do understand why this is wanted. SR -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110304225248.gi24...@bach.rivera.co.za
Re: shebang lines for Python scripts
Piotr Ożarowski pi...@debian.org wrote: any objections to change all shebangs (that do not match /usr/bin/python\d(\.\d+) but do math .+python.* regexp) to /usr/bin/python¹ in dh_python2 and to /usr/bin/python3 in dh_python3? (+ an option to disable this behaviour in both helpers) if yes, should options (-OO, etc.) be removed as well? [¹] or /usr/bin/python2, depends on PEP 394 status -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110304222346.gu30...@piotro.eu I think it's reasonable, but if you think you should do that I think we should make the Python policy language on it stronger. 2to3 doesn't seem to convert shebangs, so it would be good if dh_python3 did. Scott K
Re: shebang lines for Python scripts
* Piotr Ożarowski pi...@debian.org, 2011-03-04, 23:23: any objections to change all shebangs (that do not match /usr/bin/python\d(\.\d+) but do math .+python.* regexp) to /usr/bin/python¹ in dh_python2 and to /usr/bin/python3 in dh_python3? dh_python2 would change /usr/bin/env python3 to /usr/bin/python; dh_python3 would change /usr/bin/env python to /usr/bin/python3. No, thank you, that's wrong. if yes, should options (-OO, etc.) be removed as well? No. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110305001618.ga9...@jwilk.net
Re: shebang lines for Python scripts
[Jakub Wilk, 2011-03-05] * Piotr Ożarowski pi...@debian.org, 2011-03-04, 23:23: any objections to change all shebangs (that do not match /usr/bin/python\d(\.\d+) but do math .+python.* regexp) to /usr/bin/python¹ in dh_python2 and to /usr/bin/python3 in dh_python3? dh_python2 would change /usr/bin/env python3 to /usr/bin/python; dh_python3 would change /usr/bin/env python to /usr/bin/python3. No, thank you, that's wrong. dh_python2 and dh_python3 cannot be used for the same files at the same time (that's why dh_python2 igores python3-* packages, that's why dh_python3 ignores python-* packages and that's why you have to use -N/-p in all other packages if you want to invoke both helpers) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110305002006.gw30...@piotro.eu
Re: shebang lines for Python scripts
* Piotr Ożarowski pi...@debian.org, 2011-03-05, 01:20: any objections to change all shebangs (that do not match /usr/bin/python\d(\.\d+) but do math .+python.* regexp) to /usr/bin/python¹ in dh_python2 and to /usr/bin/python3 in dh_python3? dh_python2 would change /usr/bin/env python3 to /usr/bin/python; dh_python3 would change /usr/bin/env python to /usr/bin/python3. No, thank you, that's wrong. dh_python2 and dh_python3 cannot be used for the same files at the same time (that's why dh_python2 igores python3-* packages, that's why dh_python3 ignores python-* packages and that's why you have to use -N/-p in all other packages if you want to invoke both helpers) Wait, what, I cannot have a package that ship both python and python3 *scripts*? -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110305003530.ga2...@jwilk.net
Re: shebang lines for Python scripts
[Jakub Wilk, 2011-03-05] * Piotr Ożarowski pi...@debian.org, 2011-03-05, 01:20: dh_python2 and dh_python3 cannot be used for the same files at the same time (that's why dh_python2 igores python3-* packages, that's why dh_python3 ignores python-* packages and that's why you have to use -N/-p in all other packages if you want to invoke both helpers) Wait, what, I cannot have a package that ship both python and python3 *scripts*? you can: Piotr Ożarowski wrote: (+ an option to disable this behaviour in both helpers) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110305003920.gy30...@piotro.eu
Re: shebang lines for Python scripts
* Piotr Ożarowski pi...@debian.org, 2011-03-05, 01:39: dh_python2 and dh_python3 cannot be used for the same files at the same time (that's why dh_python2 igores python3-* packages, that's why dh_python3 ignores python-* packages and that's why you have to use -N/-p in all other packages if you want to invoke both helpers) Wait, what, I cannot have a package that ship both python and python3 *scripts*? you can: Piotr Ożarowski wrote: (+ an option to disable this behaviour in both helpers) If you're going to push this forward, please call the option --without-bugs. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110305010655.ga5...@jwilk.net
Re: shebang lines for Python scripts
On Friday, March 04, 2011 08:06:55 pm Jakub Wilk wrote: * Piotr Ożarowski pi...@debian.org, 2011-03-05, 01:39: dh_python2 and dh_python3 cannot be used for the same files at the same time (that's why dh_python2 igores python3-* packages, that's why dh_python3 ignores python-* packages and that's why you have to use -N/-p in all other packages if you want to invoke both helpers) Wait, what, I cannot have a package that ship both python and python3 *scripts*? you can: Piotr Ożarowski wrote: (+ an option to disable this behaviour in both helpers) If you're going to push this forward, please call the option --without-bugs. I get that you're not in favor of this. What is the problem with the fixing shebangs by default? If you believe what policy says, /usr/bin/env python is something we should only have in Debian packages due to the maintainer deciding it's needed for some reason. Scott K -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201103042115.05173.deb...@kitterman.com
