Closed carltongibson closed 4 years ago
Hey @carltongibson 👋
Looks like it only breaks the Python 2 build which is expected. Given tests already pass on Python 2 simply removing tested support (tox.ini, .travis.yml, setup.py) and adding a section for in the README.rst release notes under a new 3.0 section would do.
Removal of Python support code can be done in a following PR.
Hi @charettes 👋
I dropped PY2 in a separate commit, if you're happy to take that.
If you're happy with these I can rebase and drop 1.11 too whilst I'm here.
If you're happy with these I can rebase and drop 1.11 too whilst I'm here.
Totally open to that if you're up to it! I can take care of releasing 3.0 afterwards. It looks like the tox.ini
still has references to Django 2.0 and 2.1 if you want to remove these as well.
OK, I'll add it here. 10 mins.
Looks like Travis is taking a ☕ break.
I don't blame it. 😀
I'll check back on this later. Hopefully the lint builds work with python3.6
, apparently they couldn't find python3.7
...
We could run it against 3.7 (or even 3.8) if the .travis-ci.yml
file is adjusted
It seems to be OK now. https://travis-ci.org/github/gintas/django-picklefield/builds/695030386
Perfect thanks!
Not sure it dropping PY2 is on the cards now that it's EOL but, if so I think it would be fair to bump the default protocol version.
WIP because they'll be lots that breaks on tox/travis. I will check back on that later.