python-uncompyle6/admin-tools
2021-10-23 09:03:29 -04:00
..
check-newest-versions.sh Administrivia 2021-10-21 02:31:59 -04:00
check-older-versions.sh Python 3.0 fixes + administrivia 2018-06-12 08:29:13 -04:00
how-to-make-a-release.md Get ready for release 3.7.4 2020-09-05 06:06:40 -04:00
make-dist-newer.sh Administrivia - generalize shell code 2017-10-12 20:36:24 -04:00
make-dist-older.sh Administrivia - generalize shell code 2017-10-12 20:36:24 -04:00
pycdc-runtests.sh Testing with other decompiler tools 2018-04-12 19:57:53 -04:00
pyenv-all-versions ops coverage on 3.{0,1} 2017-11-30 12:38:08 -05:00
pyenv-newest-versions Add pyston-2.3 in testing 2021-10-21 14:15:26 -04:00
pyenv-older-versions Administrivia 2019-05-03 23:25:25 -04:00
pyenv-oldest-versions Administrivia and more coverage 2017-11-29 10:12:09 -05:00
README.md More Administrivia 2020-01-07 10:13:25 -05:00
run-pyenvlib-test-all.sh Administrivia... 2018-03-05 23:27:11 -05:00
setup-master.sh Version twiddling 2021-10-21 16:33:09 -04:00
setup-python-2.4.sh Administrivia 2021-10-23 09:03:29 -04:00
setup-python-3.3.sh Adminsitrivia 2021-10-21 16:36:46 -04:00
uncompyle2-runtests.sh Testing with other decompiler tools 2018-04-12 19:57:53 -04:00

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