Could someone give a beginner's tl;dr of wheels vs. eggs?
I use Python extensively but the "Advantages of wheels" section on this site is way over my head.
edit: Thanks everyone :)
I use Python extensively but the "Advantages of wheels" section on this site is way over my head.
edit: Thanks everyone :)
Eggs contain compiled Python bytecode which requires publishing egg versions for every version of Python. While Wheels are distribution formats that can support more than a single Python version.
https://packaging.python.org/discussions/wheel-vs-egg/
Having packaged wheels but not eggs, my understanding is somewhat limited, but eggs being unversioned and having weaker filename conventions sounds like it would be a pain.
I mainly use binary wheels for projects that include compiled C extensions, so I need a different wheel for each supported platform. There's a straightforward filename convention for that, and all the tools support it, so I don't have to even think about that when generating or uploading wheels.
Is anything in that unclear?
In practice, this bit I think it's pretty important:
> Wheel has a richer file naming convention. A single wheel archive can indicate its compatibility with a number of Python language versions and implementations, ABIs, and system architectures.