Interpreter wasn't displaying the location of a SyntaxError
Issue1692
This commit is contained in:
parent
4c3eda3a84
commit
43b15097cc
|
@ -12,6 +12,8 @@ What's New in Python 3.0a3?
|
|||
Core and Builtins
|
||||
-----------------
|
||||
|
||||
- Issue #1692: Interpreter was not displaying location of SyntaxError
|
||||
|
||||
- Improve some exception messages when Windows fails to load an extension
|
||||
module. Now we get for example '%1 is not a valid Win32 application' instead
|
||||
of 'error code 193'. Also use Unicode strings to deal with non-English
|
||||
|
|
|
@ -1103,7 +1103,7 @@ parse_syntax_error(PyObject *err, PyObject **message, const char **filename,
|
|||
goto finally;
|
||||
if (v == Py_None)
|
||||
*filename = NULL;
|
||||
else if (! (*filename = PyString_AsString(v)))
|
||||
else if (! (*filename = PyUnicode_AsString(v)))
|
||||
goto finally;
|
||||
|
||||
Py_DECREF(v);
|
||||
|
|
Loading…
Reference in New Issue