mirror of
https://github.com/rocky/python-uncompyle6.git
synced 2024-11-30 08:30:50 +00:00
.. | ||
.gitignore | ||
check-2.4-2.7-versions.sh | ||
check-3.0-3.2-versions.sh | ||
check-3.3-3.5-versions.sh | ||
check-newest-versions.sh | ||
checkout_common.sh | ||
how-to-make-a-release.md | ||
make-dist-2.4-2.7.sh | ||
make-dist-3.0-3.2.sh | ||
make-dist-3.3-3.5.sh | ||
make-dist-newest.sh | ||
merge-for-2.4.sh | ||
merge-for-3.0.sh | ||
merge-for-3.3.sh | ||
merge-for-3.6.sh | ||
pycdc-runtests.sh | ||
pyenv-2.1-2.3-versions | ||
pyenv-2.4-2.7-versions | ||
pyenv-3.0-3.2-versions | ||
pyenv-3.3-3.5-versions | ||
pyenv-all-versions | ||
pyenv-newest-versions | ||
pyenv-versions | ||
README.md | ||
run-pyenvlib-test-all.sh | ||
setup-master.sh | ||
setup-python-2.4.sh | ||
setup-python-3.0.sh | ||
setup-python-3.3.sh | ||
setup-python-3.6.sh | ||
uncompyle2-runtests.sh |
Making a release is a somewhat tedious process so I've automated it a little
Here are tools that I, rocky, use to check and build a distribution.
They are customized to my environment:
- I use pyenv to various Python versions installed
- I have git repos for xdis, and spark parser at the same level as uncompyle6
There may be other rocky-specific things that need customization. how-to-make-a-release.md has overall how I make a release
Since this project uses python over a wide variety of release, some versions of projects that should be used for specific Python versions
for 3.2.6: pytest==2.9.2
for 3.1.5 pytset==2.1.0 py=1.8.0 and comment out line 10 of _builtin.py # callable = callable six==1.10.0