Kay Hayen <kayha...@gmx.de> added the comment:
This is to inform you that I worked around the bug by reading the source file
in question and checking the indicated position. This is currently the only way
to decide if a literal should be unicode or str with unicode_literals from
future imported.
It goes like this:
kind = _sources[ filename ][ node.lineno - 1][ node.col_offset ]
if kind != 'b':
value = unicode( node.s )
else:
value = node.s
I don't see how removing the ambgious representation of what I presume is a
wanted language construct can be considered a new feature. But that is your
decision to make.
Best regards,
Kay Hayen
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue9690>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
