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 kayhayen
Recipients benjamin.peterson, kayhayen
Date 2010-08-26.06:38:46
SpamBayes Score 1.2866763e-05
Marked as misclassified No
Message-id <1282804728.82.0.36792139194.issue9690@psf.upfronthosting.co.za>
In-reply-to
Content
You didn't understand. Please tell me, how to decide if this is a unicode literal or a str (2.x) literal:

value=Str(s='d')

It's just not possible. When I found a "from __future__ import unicode_literals" in the code before, it means I should convert "value.s" to unicode fine. But the syntax allows with b"d" to make an exception for some strings. Your test "test_compile.py" contains it.

May I ask you to not "close" this bug therefore, as your proposal is not feasible? I really need ast.parse() to return different nodes for the string literals "d" and b"d" or else I cannot detect the non-unicode literals with unicode literals as default.
History
Date User Action Args
2010-08-26 06:38:49kayhayensetrecipients: + kayhayen, benjamin.peterson
2010-08-26 06:38:48kayhayensetmessageid: <1282804728.82.0.36792139194.issue9690@psf.upfronthosting.co.za>
2010-08-26 06:38:47kayhayenlinkissue9690 messages
2010-08-26 06:38:46kayhayencreate