Should PyPI deprecate .egg uploads?

[dustin (Dustin Ingram)]

In https://github.com/pypa/warehouse/issues/10653 I’m proposing to stop PyPI from accepting uploads of .egg distributions. TL;DR, many tools have deprecated or dropped support for eggs, and overall wheels have far outpaced eggs in terms of uploads:

Comments are welcome here or on the GitHub issue. I’d especially like to hear from anyone still building or installing eggs, or maintainers of projects that still support eggs:

Deprecate .egg uploads

[brettcannon]

Not quite sure what you’re expecting from supporters, so I just left a on the opening comment (and this comment to suggest others do the same).

[pf_moore (Paul Moore)]

I added a thumbs up to the issue, but yes, a “Like” here is probably good (so I added one as well).

[ncoghlan (Alyssa Coghlan)]

As per the comments on the GH issue, disallowing egg uploads for new projects and those that have never previously uploaded them seems like a clear win, but projects that have a history of publishing them will likely need a respectable grace period.

The overall idea still makes sense, though.

[hugovk (Hugo van Kemenade)]

See also:

Killing off the `egg=` fragment once and for all?

I’m proposing this to the packaging community, with the hopes of getting thoughts and feedback. I’m interested to hear what you all think! Background The egg= fragment is one of two ways to specify the name of a package in a requirement specifier that doesn’t “natively” contain the package name (e.g. a URL, where the base component of the URL may not match the project’s name). For example, here’s how you can tell pip that a URL requirement installs package foo: git+https://github.com/some-or…