Change by Colin Watson :
--
keywords: +patch
pull_requests: +29507
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/31357
___
Python tracker
<https://bugs.python.org/issu
New submission from Colin Watson :
In https://bugs.debian.org/1005803, Matthew Vernon reports that the library
documentation for sys.excepthook doesn't mention the detail that that
sys.excepthook isn't called for uncaught SystemExit exceptions, although
help(sys) does mention this.
(He also
Change by Colin Watson :
--
keywords: +patch
pull_requests: +22682
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/23822
___
Python tracker
<https://bugs.python.org/issu
New submission from Colin Watson :
In Python 2, it was possible to use `except` with a nested tuple, and
occasionally natural. For example, `zope.formlib.interfaces.InputErrors` is a
tuple of several exception classes, and one might reasonably think to do
something like this (this is real
Colin Watson added the comment:
Here's a reasonably minimal reproduction recipe reduced from real code in the
Launchpad test suite that doesn't require compiling a separate C extension. It
fails on Ubuntu 18.04 with the gir1.2-gtk-3.0, python3-gi, and xvfb packages
installed. (The xvfb
Colin Watson added the comment:
FWIW I just ran into what I believe to be this bug with the Launchpad test
suite on Python 3.6.9. The output shows some normal test output followed by:
No entry for terminal type "unknown";
using dumb terminal settings.
bind: Invalid command `enabl
New submission from Colin Watson:
Python 3.3 added the dir_fd and follow_symlinks keyword arguments to os.chown;
it also added the shutil.chown function. Unfortunately the latter, while
useful, does not support these new keyword arguments. It would be helpful if
it did
New submission from Colin Watson cjwat...@users.sourceforge.net:
The file-like object returned by TarFile.extractfile can't be wrapped in an
io.TextIOWrapper (which would be rather convenient in some cases to get
something that reads str rather than bytes).
The attached patch demonstrates
Colin Watson cjwat...@users.sourceforge.net added the comment:
Yes, the same symptoms are still present.
I'd argue that it generally isn't an error in practice for applications, and
thus the net effect of this exception is negative; it's extraordinarily rare
for a crash to be preferable
Colin Watson cjwat...@users.sourceforge.net added the comment:
Is there anything more I can do to move this along? Thanks.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1652
Colin Watson [EMAIL PROTECTED] added the comment:
2.6 is fine if that's what the release process dictates; I don't want it
to be lost, that's all.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1652
Colin Watson added the comment:
To be quite honest I can't think of any incompatibilities that wouldn't
have the basic result of improving matters. I put the migration stuff in
my bug report in case somebody else could, because I don't want the bug
fix to stall on that.
My preference would
New submission from Colin Watson:
On Unix, Python sets SIGPIPE to SIG_IGN on startup, because it prefers
to check every write and raise an IOError exception rather than taking
SIGPIPE. This is all well and good for Python itself. However,
non-Python Unix subprocesses generally expect to have
13 matches
Mail list logo
