homepage

> Can we consider 3.6.0 rather than 3.6.1 as broken release?
In the last week, pypi downloads were about evenly split between 3.6.0 and 3.6.1 (2269969 for "3.6.1", 1927189 for "3.6.0", and those two were ~2 orders of magnitude more common than other strings like "3.6.1+", "3.6.0b2", etc. [1]). Not sure what that to conclude from that, but certainly if people start uploading 3.6.1-only wheels right now then it will break things for a lot of end users.
With my manylinux docker image maintainer hat on: we're currently shipping 3.6.0. I'm extremely confident that if we stick with this we'll never get any complaints about the obscure bug with malicious __index__ implementations that's being fixed here. OTOH if we upgrade to 3.6.1, or any version with this ABI change, then we'll definitely get many complaints so long as there's anyone at all still using 3.6.0, which is probably forever. So I'm not sure not sure what incentive we would have to ever upgrade to 3.6.1+ if this ABI change is kept?
(This isn't saying the bug is unimportant! But it sure is hard to sell its importance to folks trying to ship packages and support end-users...)
--------
[1] Somewhat crude query I used in case it's useful for future reference:
SELECT
 REGEXP_EXTRACT(details.python, r"^([^\.]+\.[^\.]+\.[^\.]+)") as python_version,
 COUNT(*) as download_count,
FROM
 TABLE_DATE_RANGE(
 [the-psf:pypi.downloads],
 DATE_ADD(CURRENT_TIMESTAMP(), -7, "day"),
 DATE_ADD(CURRENT_TIMESTAMP(), 0, "day")
 )
WHERE
 REGEXP_MATCH(details.python, r"^3\.6\.")
GROUP BY
 python_version,
ORDER BY
 download_count DESC
LIMIT 100