PythonCharmers/python-future

use pasteurize in setuptools, similarly to use_2to3

Open

#266 opened on Jan 24, 2017

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

Description

Would there be a way to use pasteurize in setuptools similarly to use_2to3? i.e., only commit Py3 code, but have a setup.py that contains something like

setup(..., use_pasteurize=True)

and have the code be pasteurized when installing (and testing) on Py2.

The idea is that pasteurized code can look quite "ugly" (e.g. keyword only arguments), so I'd rather not keep it committed, but with a good test suite, I can still make sure that the pasteurized version always works on Py2.

Contributor guide

Tech stack
python
Domain
build systemtooling
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.
clear
Prerequisites
Python packagingsetuptools internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate how use 2to3 is implemented in setuptools (e.g., the setup command or build clib). Then replicate a similar mechanism for pasteurize, ensuring it runs before building on Python 2. Update setup.py configuration and documentation.