Drekin added the comment:
Since this issue was fixed, shouldn't it be marked fixed here?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13758
___
STINNER Victor added the comment:
Closed.
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13758
___
STINNER Victor added the comment:
This issue has been fixed in issue #11619 by:
New changeset df2fdd42b375 by Victor Stinner in branch 'default':
Close #11619: The parser and the import machinery do not encode Unicode
http://hg.python.org/cpython/rev/df2fdd42b375
Thanks for the report!
(I
Drekin added the comment:
Hello. Will this be fixed? It's really annoying that you cannot pass valid
unicode filename to compile(). I'm using a workaround: I just pass
placeholder and then “update” the resulting code object recursively to set
the correct co_filename. Afterwards the code
Terry J. Reedy added the comment:
Victor, do you have any opinion on this unicode filename issue?
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13758
___
STINNER Victor added the comment:
Victor, do you have any opinion on this unicode filename issue?
I closed the issue #11619 in january 2013 before there was no user requesting
the feature. I just reopened the issue because users now ask for it.
--
Terry J. Reedy tjre...@udel.edu added the comment:
My supposition that compile() rejects some real file names appears correct:
from python-list
ME: Is this a filename that could be an actual, valid filename on your system?
OP: Yes it is. open works on that file.
--
New submission from Terry J. Reedy tjre...@udel.edu:
The 3.2.2 doc for compile() says The filename argument should give the file
from which the code was read; pass some recognizable value if it wasn’t read
from a file ('string' is commonly used).
I am not sure what 'recognizable' is supposed
