Is it the pickling / serialization that is sensitive to even minor version changes in Python ? I think adding 3.4 might be fine as it is probably in the top-3 of versions used (see https://hynek.me/articles/python3-2016 for example), but maintaining more versions does make testing etc. more expensive
Agree on that testing is one huge concern here.
However, I still don't want to have nightmares of those 3.4 users struggling and suffering.
One potential solution I'm thinking, is that can we:
1, only test 2.6 and 3.6 for development -- this even reduces our current testing time
2, testing all sub-versions for releases
The hope here is that differences between subversion should be small and easy to fix.
We have users with python 3.4. Should we build and upload 3.4 runtime? and other python versions?
The text was updated successfully, but these errors were encountered: