[issue2477] parser support for future import of unicode_strings

Neal Norwitz <[EMAIL PROTECTED]> added the comment: Christian checked this in a few days ago in r61953 and a few other revisions. -- resolution: -> accepted status: open -> closed __ Tracker <[EMAIL PROTECTED]>

[issue2477] parser support for future import of unicode_strings

Christian Heimes <[EMAIL PROTECTED]> added the comment: Slightly better patch * removed bzr hack * simplified parsestr() * updated NEWS Added file: http://bugs.python.org/file9855/unicode_literals2.patch __ Tracker <[EMAIL PROTECTED]>

[issue2477] parser support for future import of unicode_strings

Changes by Christian Heimes <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file9846/unicode_literals.patch __ Tracker <[EMAIL PROTECTED]> __

[issue2477] parser support for future import of unicode_strings

Christian Heimes <[EMAIL PROTECTED]> added the comment: > Also Christian - the posted patch accidentally included your hack to make the version info a bit more non-SVN checkout friendly. I'm still learning bzr. I just have figured out how to merge changes from the upstream trunk into my branch.

[issue2477] parser support for future import of unicode_strings

Nick Coghlan <[EMAIL PROTECTED]> added the comment: The patch actually isn't all that complicated - the main structural change to make it possible to process the strings correctly is converting the parser functions to have treat the flags argument as an I/O variable, rather than just an input. Ot

[issue2477] parser support for future import of unicode_strings

Changes by Ralf Schmitt <[EMAIL PROTECTED]>: -- nosy: +schmir __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe:

[issue2477] parser support for future import of unicode_strings

Christian Heimes <[EMAIL PROTECTED]> added the comment: Working patch I had to introduce yet another PyParser Ex method for string parsing. I also renamed the future feature to "unicode_literals" Added file: http://bugs.python.org/file9846/unicode_literals.patch ___

[issue2477] parser support for future import of unicode_strings

Marc-Andre Lemburg <[EMAIL PROTECTED]> added the comment: The flag should be named "unicode_literals" since that what changes. Unicode strings are already available in Python 2.x :-) BTW: I'm not convinced that these future imports are all that useful - the ratio between usefulness and added com

[issue2477] parser support for future import of unicode_strings

Christian Heimes <[EMAIL PROTECTED]> added the comment: I've carefully examined both version. I agree that update_flags_from_node is too fragile. I haven't verified my theory but I *think* the current code does neither support from __future__ import egg, spam nor from __future__ import egg

[issue2477] parser support for future import of unicode_strings

Changes by Eric Smith <[EMAIL PROTECTED]>: -- nosy: +eric.smith __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe

[issue2477] parser support for future import of unicode_strings

Christian Heimes <[EMAIL PROTECTED]> added the comment: I'll check it out today. -- assignee: -> tiran nosy: +tiran __ Tracker <[EMAIL PROTECTED]> __ _

[issue2477] parser support for future import of unicode_strings

New submission from Neal Norwitz <[EMAIL PROTECTED]>: This is a patch that modifies the parser to allow getting the future import flags into the AST. There are 2 approaches that are embedded within the patch. Both approaches can be seen in Python/pythonrun.c. 1) update_flags_from_node() - this