Issue 2495: tokenize doesn't handle __future__.unicode_literals correctly - Python tracker

➜

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
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: amaury.forgeotdarc, christian.heimes
Priority: normal Keywords:

Created on 2008-03-27 11:50 by christian.heimes, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Pull Requests
URL Status Linked Edit
PR 6572 closed lukasz.langa, 2018-04-23 01:09
Messages (2)
msg64582 - (view) Author: Christian Heimes (christian.heimes) * (Python committer) Date: 2008-03-27 11:50 
See r61976

Clear the blacklist and run the test with 

  ./python Lib/test/regrtest.py -uall test_tokenize

to reproduce the issue.
msg64609 - (view) Author: Amaury Forgeot d'Arc (amaury.forgeotdarc) * (Python committer) Date: 2008-03-27 23:24 
Actually, the problem is that untokenize does not put spaces between two
consecutive string literals:

'' '' => ''''

Corrected with r61979.
Will backport