➜

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.

classification
Title: from __future__ import unicode_literals, print_function doesn't work
Type: Stage:
Components: Interpreter Core Versions: Python 2.7, Python 2.6
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: barry, benjamin.peterson, christian.heimes, georg.brandl
Priority: release blocker Keywords: patch

Created on 2008-10-26 17:09 by benjamin.peterson, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
fix_multiple_features.patch benjamin.peterson, 2008-10-26 17:09
Messages (3)
msg75237 - (view) Author: Benjamin Peterson (benjamin.peterson) * (Python committer) Date: 2008-10-26 17:09 
This is because parser.c's future_hack breaks out of the loop when it
finds one feature. Patch with test is attached.
msg75245 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2008-10-26 19:48 
Looks fine.

As a bonus, you can find out why "unicode_literals" doesn't work when
used in an exec'd string -- this is why I didn't upload my fix yet.
msg75247 - (view) Author: Benjamin Peterson (benjamin.peterson) * (Python committer) Date: 2008-10-26 20:22 
Fixed in r67030.
History
Date User Action Args
2022-04-11 14:56:40adminsetnosy: + barry
github: 48459
2008-10-26 20:22:40benjamin.petersonsetstatus: open -> closed
resolution: accepted -> fixed
messages: + msg75247
2008-10-26 19:48:58georg.brandlsetresolution: accepted
messages: + msg75245
nosy: + georg.brandl
2008-10-26 18:53:13benjamin.petersonsetnosy: + christian.heimes
2008-10-26 17:09:42benjamin.petersoncreate