Message115055
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 |
|
Date |
User |
Action |
Args |
2010-08-27 07:04:13 | kayhayen | set | recipients:
+ kayhayen, benjamin.peterson |
2010-08-27 07:04:12 | kayhayen | set | messageid: <1282892652.69.0.771151771927.issue9690@psf.upfronthosting.co.za> |
2010-08-27 07:04:11 | kayhayen | link | issue9690 messages |
2010-08-27 07:04:10 | kayhayen | create | |
|