[issue16514] Cryptic traceback when sys.path[0] is None

2012-11-21 Thread Jesús Cea Avión
Changes by Jesús Cea Avión : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue16514] Cryptic traceback when sys.path[0] is None

2012-11-20 Thread Barry A. Warsaw
Changes by Barry A. Warsaw : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue16514] Cryptic traceback when sys.path[0] is None

2012-11-20 Thread Roundup Robot
Roundup Robot added the comment: New changeset 291406748217 by Barry Warsaw in branch '3.3': - Issue #16514: Fix regression causing a traceback when sys.path[0] is None http://hg.python.org/cpython/rev/291406748217 New changeset a82ee9a1457a by Barry Warsaw in branch 'default': - Issue #16514: F

[issue16514] Cryptic traceback when sys.path[0] is None

2012-11-20 Thread Barry A. Warsaw
Changes by Barry A. Warsaw : -- title: Cryptic traceback when sys.path -> Cryptic traceback when sys.path[0] is None ___ Python tracker ___ _

[issue16514] Cryptic traceback when sys.path

2012-11-20 Thread Barry A. Warsaw
Barry A. Warsaw added the comment: On Nov 20, 2012, at 04:51 PM, Eric V. Smith wrote: >I agree it's a bug. And the fix looks good to me. Thanks. >Having said that: I haven't looked at the import.c version to verify what is >happening. Does the test pass under 3.2? Yep. See below. When you t

[issue16514] Cryptic traceback when sys.path[0] is None

2012-11-20 Thread Chris Jerdonek
Changes by Chris Jerdonek : -- nosy: +chris.jerdonek ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue16514] Cryptic traceback when sys.path[0] is None

2012-11-20 Thread Barry A. Warsaw
Barry A. Warsaw added the comment: Oh, btw, I intend to add documentation that makes explicit: * sys.path entries must be strings or bytes, everything else is ignored * path importers should expect strings or bytes * the encoding of bytes is left to the individual path hooks to define, however

[issue16514] Cryptic traceback when sys.path[0] is None

2012-11-20 Thread Eric V. Smith
Eric V. Smith added the comment: I agree it's a bug. And the fix looks good to me. Having said that: I haven't looked at the import.c version to verify what is happening. Does the test pass under 3.2? -- ___ Python tracker

[issue16514] Cryptic traceback when sys.path[0] is None

2012-11-20 Thread Barry A. Warsaw
Changes by Barry A. Warsaw : -- nosy: +brett.cannon, eric.smith, eric.snow, jason.coombs ___ Python tracker ___ ___ Python-bugs-list m

[issue16514] Cryptic traceback when sys.path[0] is None

2012-11-20 Thread Barry A. Warsaw
Barry A. Warsaw added the comment: Oh, the patch includes the removal of some unused imports from test_path.py, thanks to pyflakes. -- ___ Python tracker ___ ___

[issue16514] Cryptic traceback when sys.path[0] is None

2012-11-20 Thread Barry A. Warsaw
Barry A. Warsaw added the comment: Patch for 3.3, omitting the requisite importlib.h change. -- keywords: +patch Added file: http://bugs.python.org/file28051/16514.diff ___ Python tracker __

[issue16514] Cryptic traceback when sys.path[0] is None

2012-11-20 Thread Barry A. Warsaw
New submission from Barry A. Warsaw: When sys.path[0] is None, attempting to import a module produces a cryptic chained traceback. This is a regression from 3.2 where the import would succeed. The basic issue is that in 3.2's import.c, non-string/bytes items on sys.path are essentially ignor