Dual install modes: Py3.6+ modern build (drop lib2to3), legacy Py2 via setup.py #25
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tup.py); drop lib2to3 on Py3; update README, tox, classifiers; bump to 0.6.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
pyproject.toml(PEP 621/517) withrequires-python >=3.6, console script, classifiers. Build backend switched to setuptools.lib2to3use on Python 3; keep it only for legacy Python 2 path. Encoding detection now usestokenize.detect_encodingon Py3.setup.pyfor legacy installs; loosened version gate to allow local installs while upstream modern metadata governs Py3 wheels.README.rst.tox.inito test Py3.6–3.12 with pytest.Impacts:
pip install unify. Nolib2to3dependency; compatible with Python 3.11+.setup.py.Upstream repo reference:
myint/unify.