Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

99% of top Python packages are now wheels

pythonwheels.com

Post reply on HN
Print view View original

71–79 of 79 posts

Re: 99% of top Python packages are now wheels

#71

Post by Shawnj2 »

pdimitar wrote: post #70
Shawnj2 wrote: post #69

Earlier quoted context omitted.

That doesn’t make sense either because pure python packages exist and are actively less useful if distributed as wheels

And I have no clue what you just said. :D It serves only as a further confusion. But yeah, Python is notorious for its numerous (and likely all sub-optimal) approaches to packaging.

The benefit of wheels is that they’re platform specific so that you don’t need to have a lengthy and dependency ridden compile process, you just install the one that works on your OS and architecture and you’re good. Packages written entirely in Python don’t have this problem since the code is pretty much just copied into dist-packages

Re: 99% of top Python packages are now wheels

#72

Post by pdimitar »

Shawnj2 wrote: post #71
pdimitar wrote: post #70

Earlier quoted context omitted.

And I have no clue what you just said. :D It serves only as a further confusion. But yeah, Python is notorious for its numerous (and likely all sub-optimal) approaches to packaging.

The benefit of wheels is that they’re platform specific so that you don’t need to have a lengthy and dependency ridden compile process, you just install the one that works on your OS and architecture and you’re good. Packages written entirely in Python don’t have this problem since the code is pretty much just copied into dist-packages

I see, thank you, that's much better.

I'd still try to shove the platform-specific stuff in a package manager and delegate that complexity to it.

Re: 99% of top Python packages are now wheels

#73

Post by Shawnj2 »

pdimitar wrote: post #72
Shawnj2 wrote: post #71

Earlier quoted context omitted.

The benefit of wheels is that they’re platform specific so that you don’t need to have a lengthy and dependency ridden compile process, you just install the one that works on your OS and architecture and you’re good. Packages written entirely in Python don’t have this problem since the code is pretty much just copied into dist-packages

I see, thank you, that's much better. I'd still try to shove the platform-specific stuff in a package manager and delegate that complexity to it.

For various reasons that’s often not an option

Re: 99% of top Python packages are now wheels

#74

Post by fmajid »

matsemann wrote: post #57
TekMol wrote: post #29

Earlier quoted context omitted.

That is pretty awesome! Why is all the "wheels", "eggs", "PyPi" ... stuff needed then?

Because so much Python code binds to C extensions that you will need to compile for the correct platform. For instance the new version of Pydantic is now backed by Rust. To avoid everyone having to compile the rust code on their platform, you can upload it pre-compiled for linux, windows etc.

Some packages require build-time dependencies not everyone has, like cryptography now requiring Rust. Some packages like SciPy take a very long time to build, and require a Fortran compiler.

Re: 99% of top Python packages are now wheels

#75

Post by thiht »

omgmajk wrote: post #15

For people who are confused by this: "Wheel has an official standard specification. Egg did not. Wheel is a distribution format, i.e a packaging format. 1 Egg was both a distribution format and a runtime installation format (if left zipped), and was designed to be importable. Wheel archives do not include .pyc files." [1] [1] https://packaging.python.org/discussions/wheel-vs-egg/

Wtf is an egg?

Re: 99% of top Python packages are now wheels

#76

Post by mschuster91 »

jen20 wrote: post #52
mschuster91 wrote: post #47

Earlier quoted context omitted.

This is, other than the fact it violates UNIX principles, my biggest issue with Homebrew.

Which UNIX principles do you believe it violates?

Installing files in /usr/local/bin (a default path for all users) by an user that is not root. Absolute no-go.

Re: 99% of top Python packages are now wheels

#77

Post by omgmajk »

thiht wrote: post #75
omgmajk wrote: post #15

For people who are confused by this: "Wheel has an official standard specification. Egg did not. Wheel is a distribution format, i.e a packaging format. 1 Egg was both a distribution format and a runtime installation format (if left zipped), and was designed to be importable. Wheel archives do not include .pyc files." [1] [1] https://packaging.python.org/discussions/wheel-vs-egg/

Wtf is an egg?

The other type of package format from Wheel. I agree it's not very clear.

Re: 99% of top Python packages are now wheels

#78

Post by jen20 »

mschuster91 wrote: post #76
jen20 wrote: post #52

Earlier quoted context omitted.

Which UNIX principles do you believe it violates?

Installing files in /usr/local/bin (a default path for all users) by an user that is not root. Absolute no-go.

It hasn’t done that in some time.

Re: 99% of top Python packages are now wheels

#79

Post by LoganDark »

pdimitar wrote: post #4

30 years later I still love programming but people given authority opting for cutesy names for critically important terms in the ecosystem should be severely limited in their options. Flakes, pills, wheels, eggs... Come on, people. I am willing to bet good money that it won't hurt you physically if you just call them "packages".

They're not even packages. The package is the source code. A "Wheel" is a compiled distribution.
Post reply on HN