Message10532

Author jaraco
Recipients CecilWesterhof, fwierzbicki, irmen, jaraco, pjac, zyasoft
Date 2015-12-12.16:06:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1449936385.61.0.305348231142.issue2007@psf.upfronthosting.co.za>
In-reply-to
Content
I'm seeing this behavior not at the interactive prompt. I'm using Jython in Moneydance (using the latest Extension patched for Jython 2.7.0 final https://bitbucket.org/infinitekind/moneydance_open/src/165efb396faffc05618900a7f2cd835f6c582d19?at=master) and I'm importing a module that's in sys.path whose header has `from future import print_function, unicode_literals`. When the program runs, literal strings are unicode but print is an expression. For example,

print("all's", "well")

renders as

(u"all's", u'well')

but should render as 

all's well

So it seems that it's more than just the interactive prompt affected by the print_function future not being recognized.
History
Date User Action Args
2015-12-12 16:06:25jaracosetmessageid: <1449936385.61.0.305348231142.issue2007@psf.upfronthosting.co.za>
2015-12-12 16:06:25jaracosetrecipients: + jaraco, fwierzbicki, irmen, zyasoft, pjac, CecilWesterhof
2015-12-12 16:06:25jaracolinkissue2007 messages
2015-12-12 16:06:24jaracocreate