I wanted to mention something that came up recently in Ubuntu, where
lsb_release is a Python 3 script. This isn't specific to Python 3, since
Python 2 scripts can also be affected.
The Launchpad bug is symptomatic of the more general problem:
* Barry Warsaw ba...@python.org, 2012-10-25, 10:56:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/938869
When you write system scripts like 'lsb_release' that use
/usr/bin/python{,3} in the #! line, please remember to include -Es
switches. This prevents the crash in question, where a
The attached patch is a first stab at packaging SymPy 0.7.2, which
supports Python 3. There's some polishing to be done, such as adding
an isympy3 script, but it at least builds.
I assume that building the binary packages from a single source
package is preferred? The upstream releases on Google
On Oct 25, 2012, at 07:05 PM, Jakub Wilk wrote:
* Barry Warsaw ba...@python.org, 2012-10-25, 10:56:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/938869
When you write system scripts like 'lsb_release' that use
/usr/bin/python{,3} in the #! line, please remember to include -Es
switches.
On Thu, Oct 25, 2012 at 10:56:05AM -0400, Barry Warsaw wrote:
This doesn't requires a mass freakout, but it might be useful for a mass bug
filing (of non-urgent priority, I think). I don't have time before UDS-R to
look into that, so I at least wanted to send this email to put it on the
On Oct 25, 2012, at 11:18 AM, Steve Langasek wrote:
On Thu, Oct 25, 2012 at 10:56:05AM -0400, Barry Warsaw wrote:
This doesn't requires a mass freakout, but it might be useful for a mass bug
filing (of non-urgent priority, I think). I don't have time before UDS-R to
look into that, so I at
[Steve Langasek, 2012-10-25]
On Thu, Oct 25, 2012 at 10:56:05AM -0400, Barry Warsaw wrote:
Using -E fixed the immediate bug, but I think it is generally useful to
include -s also, so as to avoid any potential breakage of system scripts by
things users may have added locally.
If there's
7 matches
Mail list logo