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 amaury.forgeotdarc
Recipients amaury.forgeotdarc, benjamin.peterson, georg.brandl
Date 2008-10-29.22:43:40
SpamBayes Score 8.401747e-05
Marked as misclassified No
Message-id <1225320221.76.0.741321076647.issue4225@psf.upfronthosting.co.za>
In-reply-to
Content
The newer patch is good.

I found another use of PyAST_FromNode() with NULL flags, and which has 
the same problem:

import parser
s=parser.suite(
     "from __future__ import unicode_literals; print type('')")
eval(s.compile())

But I don't know how to correct this: the CO_FUTURE_UNICODE_LITERALS 
flag is determined during the parse phase (in parser.suite), but this 
value is lost and not passed to s.compile().
Maybe PyST_Object could grow a "st_flags" attribute.
History
Date User Action Args
2008-10-29 22:43:42amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, georg.brandl, benjamin.peterson
2008-10-29 22:43:41amaury.forgeotdarcsetmessageid: <1225320221.76.0.741321076647.issue4225@psf.upfronthosting.co.za>
2008-10-29 22:43:41amaury.forgeotdarclinkissue4225 messages
2008-10-29 22:43:40amaury.forgeotdarccreate