PythonCharmers/python-future

improve handling of unicode and str in python2 code when using futurize

Open

#381 opened on Sep 25, 2018

View on GitHub
 (1 comment) (1 reaction) (0 assignees)Python (1,172 stars) (327 forks)batch import
0.20help wanted

Description

If python2 code uses unicode and str (to represent bytes).

When using futurize we add from builtins import str which breaks the behavior of the old str usage.

It would be nice to make it harder to mix up the two types when using futurize.

Contributor guide

Tech stack
python
Domain
developer experiencetooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Python 2/3 compatibilityfuturize tool usagepython future library basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the futurize module in the python future repository to understand how it currently handles 'str' and 'unicode'. Look at how the 'from builtins import str' transformation is applied and identify locations where Python 2 code may mix 'str' (bytes) and 'unicode'. Examine existing tests and documentation in the repository for guidance on expected behavior. Engage with maintainers on the issue to clarify desired improvements.