One case I could see is the use of the requires_python metadata. It was not included in the recent release of Django 2.0 (which is py 3 only) and making a new release will be useless as pip on py2 will still see Django 2.0.0 as Py 2 compatible download it and crash.

I'm going to assume with time more packages will be affected even with minor version of Python.

-- 
M


On Dec 19, 2017 21:17, "Sumana Harihareswara" <sh@changeset.nyc> wrote:
For those who want to track the relevant GitHub issues:

* supporting Markdown https://github.com/pypa/warehouse/issues/869
* staged releases https://github.com/pypa/warehouse/issues/726
* advising packagers to run `python setup.py check -r -s`
https://github.com/pypa/python-packaging-user-guide/issues/210

--
Sumana Harihareswara
Changeset Consulting
https://changeset.nyc
_______________________________________________
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig