Decide what to do with the PyPI ets package

[mdickinson]

There's an ets package on PyPI, but it's uninstallable with Python 3: pip install ets fails on a use of execfile in the setup script.

Deleting packages from PyPI isn't something that should be done lightly - someone somewhere might have a workflow that still depends on this package. Instead I'd suggest that we update the README and make a bugfix "release", so that the PyPI description indicates clearly that the package is no longer supported.

[rahulporuri]

... and make a bugfix "release", ...

Does this mean that the bugfix release will make ets installable from PyPI again?

[mdickinson]

Does this mean that the bugfix release will make ets installable from PyPI again?

That wasn't what I had in mind. No changes to the core code at all; just a version number bump and an updated README.

[mdickinson]

Deleting packages from PyPI isn't something that should be done lightly

Another reason not to delete the project from PyPI is that we likely want to keep the ets name, and the ets package may be reborn in some other form (e.g., providing common tooling for the various ETS projects).

[mdickinson]

just a version number bump and an updated README.

I had a brief thought that at the same time we should update the python_requires field in the setup.py to indicate that Python 2 is required. But that doesn't help for Python 3 users: pip install ets would just pick up the previous release that didn't include the Python 2-only restriction.

[mdickinson]

We also have the option of "yank"ing releases on PyPI: https://www.python.org/dev/peps/pep-0592/