[issue2920] Patch to print symbolic value or errno in EnvironmentError.__str__()

Change by Zackery Spytz : -- pull_requests: +14755 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/14988 ___ Python tracker ___

[issue2920] Patch to print symbolic value or errno in EnvironmentError.__str__()

Antoine Pitrou pit...@free.fr added the comment: This would still be a helpful improvement. -- stage: patch review - needs patch versions: +Python 3.3 -Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2920

[issue2920] Patch to print symbolic value or errno in EnvironmentError.__str__()

Łukasz Langa luk...@langa.pl added the comment: Alexander is right that this should be considered as part of PEP 3151. Plus, changes to interpreter core are subject to the moratorium. I am -1 on this. I would propose to create a superseding issue for implementing PEP 3151 and gathering

[issue2920] Patch to print symbolic value or errno in EnvironmentError.__str__()

Antoine Pitrou pit...@free.fr added the comment: PEP 3151 is already large enough and I don't want to add orthogonal changes to it. Furthermore, this change is only about the string representation of exceptions, and may be accepted for 3.2 even despite the moratorium. --

[issue2920] Patch to print symbolic value or errno in EnvironmentError.__str__()

Changes by Terry J. Reedy tjre...@udel.edu: -- versions: -Python 2.6, Python 2.7, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2920 ___

[issue2920] Patch to print symbolic value or errno in EnvironmentError.__str__()

Alexander Belopolsky belopol...@users.sourceforge.net added the comment: This looks like something that can become part of PEP 3151. -- assignee: belopolsky - nosy: -Alexander.Belopolsky stage: - patch review ___ Python tracker

[issue2920] Patch to print symbolic value or errno in EnvironmentError.__str__()

Amaury Forgeot d'Arc amaur...@gmail.com added the comment: I don't like the import errno while printing an exception... It would be much more robust to store errorcode_dict in a static variable when python starts, and reuse it directly. -- nosy: +amaury.forgeotdarc

[issue2920] Patch to print symbolic value or errno in EnvironmentError.__str__()

Antoine Pitrou pit...@free.fr added the comment: Agreed with Amaury. Module import could fail for various reasons (perhaps the same ones which led to the exception being raised!), or could deadlock if the import lock is being held. Also, having __str__ fail is usually very annoying for users

[issue2920] Patch to print symbolic value or errno in EnvironmentError.__str__()

Alexander Belopolsky alexander.belopol...@gmail.com added the comment: The patch already checks for failed import and falls back to printing numerical error code. However, I don't like the import either. I will think about the alternatives. On May 28, 2010, at 8:27 AM, Antoine Pitrou

[issue2920] Patch to print symbolic value or errno in EnvironmentError.__str__()

Changes by Alexander Belopolsky belopol...@users.sourceforge.net: -- assignee: - belopolsky nosy: +belopolsky ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2920 ___

[issue2920] Patch to print symbolic value or errno in EnvironmentError.__str__()

New submission from Yannick Gingras [EMAIL PROTECTED]: EnvironmentError and its subclass OSError add the value of errno in their error message. This value is an integer but the specific value in an implementation detail and the C runtime recommends that programmers use the symbolic values

[issue2920] Patch to print symbolic value or errno in EnvironmentError.__str__()

Alexandre Vassalotti [EMAIL PROTECTED] added the comment: Overall, the patch looks good. I made a couple of fixes to make the changes more robust. -- nosy: +alexandre.vassalotti priority: - normal type: - feature request Added file: http://bugs.python.org/file10378/symbolic-errno.diff