The package was renamed upstream: https://github.com/PyCQA/pycodestyle https://github.com/PyCQA/pycodestyle/issues/466
There's already a dev-python/pycodestyle available. Adding the maintainer to CC.
CC'ing python@ since they maintain pep8. While pycodestyle is the successor to pep8, I recommend we keep things as they are until pycodestyle is stable everywhere pep8 is/was. The version numbers are exclusive, i.e. there is no pep8-x.y.z if there is a pycodestyle-x.y.z and vice versa, so there isn't really a pkgmove or the like we could do seamlessly, AIUI. So I think we should get pycodestyle stable on all the arches we have a stable pep8 on (alpha, amd64, arm, hppa, ia64, ppc, ppc64, sparc, x86) and then make a news item so people can move. Also, IIUC, while pycodestyle may be a drop-in replacement for pep8 right now (1.7.0 vs. 2.0.0), that is not guaranteed to be true for future versions of pycodestyle (or pep8, if there will be any). If python@ wants in on the maintainership of pycodestyle, that's splendid. I mostly added it to the tree since newer versions of flake8 needed it. Comments/Proposals/Better ideas?
Should this be turned into a tracker for packages to switch to dev-python/pycodestyle then?
We have them as separate packages now, and pep8 has only one revdep, so no tracker needed.
