This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author benjamin.peterson
Recipients benjamin.peterson, kayhayen
Date 2010-08-27.13:18:12
SpamBayes Score 7.565897e-09
Marked as misclassified No
Message-id <AANLkTim6QUbWBcfCHFwVBENeEw3MyC=x7YoJPQQmjGrX@mail.gmail.com>
In-reply-to <1282892652.69.0.771151771927.issue9690@psf.upfronthosting.co.za>
Content
2010/8/27 Kay Hayen <report@bugs.python.org>:
>
> Kay Hayen <kayhayen@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.

I see. I'm not really sure what you're problem is again because if
unicode_literals is in effect, the AST will have decoded the literal
into unicode.

"Module(body=[ImportFrom(module='__future__',
names=[alias(name='unicode_literals', asname=None)], level=0),
Expr(value=Tuple(elts=[Str(s=u's'), Str(s=u's')], ctx=Load()))])"
History
Date User Action Args
2010-08-27 13:18:13benjamin.petersonsetrecipients: + benjamin.peterson, kayhayen
2010-08-27 13:18:12benjamin.petersonlinkissue9690 messages
2010-08-27 13:18:12benjamin.petersoncreate