Packages are wheels? lolwut? > Wheels are the new standard of Python distribution and are intended to replace eggs. Ahhh... ???
The linked page has hyperlinks that you can click to get to the specification for at least Wheels.
99% of top Python packages are now wheels
31–40 of 79 posts
Re: 99% of top Python packages are now wheels
#32Earlier quoted context omitted.
Well these are at least more or less known and widely used (though I agree if you never worked with Java that .JAR and .WAR will be confusing). But when a language ecosystem opts for cutesy niche names then they just end up confusing everybody, including some of their own users.
I think JAR (Java Archive) and WAR (Web Archive) make sense. But wheel? It's a wheel of cheese, because pypi used to be called cheeseshop? I mean sure, but doesn't it feel a bit like that 20-year-old tatoo that you got during your teens that you got mixed feelings about today? My suggestion: Call them pypacks -- extension: .pyp
> I mean sure, but doesn't it feel a bit like that 20-year-old tatoo that you got during your teens that you got mixed feelings about today?
That's exactly how I view all these "quirky" names btw.
Re: 99% of top Python packages are now wheels
#33Earlier quoted context omitted.
Well these are at least more or less known and widely used (though I agree if you never worked with Java that .JAR and .WAR will be confusing). But when a language ecosystem opts for cutesy niche names then they just end up confusing everybody, including some of their own users.
I think JAR (Java Archive) and WAR (Web Archive) make sense. But wheel? It's a wheel of cheese, because pypi used to be called cheeseshop? I mean sure, but doesn't it feel a bit like that 20-year-old tatoo that you got during your teens that you got mixed feelings about today? My suggestion: Call them pypacks -- extension: .pyp
Ooooo I like that. pypacks
Re: 99% of top Python packages are now wheels
#34Earlier quoted context omitted.
I think JAR (Java Archive) and WAR (Web Archive) make sense. But wheel? It's a wheel of cheese, because pypi used to be called cheeseshop? I mean sure, but doesn't it feel a bit like that 20-year-old tatoo that you got during your teens that you got mixed feelings about today? My suggestion: Call them pypacks -- extension: .pyp
JAR itself is a cutesy reference. You put your code in a jar, get it? WAR is perhaps not a cute reference, but it hints at what you'll be facing...
That's why I said jar/war are kind of the exception. They are still recognizable for many though, whereas Nix and Python's names are just WTF.
Re: 99% of top Python packages are now wheels
#35Earlier quoted context omitted.
> But let's be serious, they could have just said "99% of the top Python packages upgraded to our new packaging system" which would be much more informative and interesting title How about "99% of the top Python packages don't require being compiled to install them". That's one of the biggest wins of wheels. They have pre-compiled binaries for all supported platforms of that package. This typically applies to Python…
And I would have never understood that from a cursory look at the article. Learned it just now from you.
It's number 3 in "advantages of wheels", which is above the fold on my screen and exactly 50 words into the page, including titles.
Re: 99% of top Python packages are now wheels
#3630 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".
> I am willing to bet good money that it won't hurt you physically if you just call them "packages". So, "Packages are the new standard of distributing packages, and replace packages" is clearer to you?
"99% of top Fooz packages are using new package system"
vs
"99% of top Fooz packages are lame"
Re: 99% of top Python packages are now wheels
#37Is it possible to publish Python code for others to use simply by putting a repo on a webserver? In other words, can someone put a line like this into their requirements.txt file? https://somewhere.com/some/git/repo.git
Yes https://github.com/iree-org/iree-samples/blob/main/requireme... You can do even better using GitHub releases: the GET for a releases page with assets (ie use inspector) functions as an index url. So you can have a repo that publishes wheels to a release called eg `latest` that can function as the index for that package/wheel. You can even have multiple repos that publish to a single such wheel repo release repo (…
I don't know what "GitHub releases" are. And I don't want to know :)
I prefer to use as few technologies as possible. And completely stay away from propriatary technologies.
Re: 99% of top Python packages are now wheels
#38Earlier quoted context omitted.
> But let's be serious, they could have just said "99% of the top Python packages upgraded to our new packaging system" which would be much more informative and interesting title How about "99% of the top Python packages don't require being compiled to install them". That's one of the biggest wins of wheels. They have pre-compiled binaries for all supported platforms of that package. This typically applies to Python…
And I would have never understood that from a cursory look at the article. Learned it just now from you.
So without understanding the reasoning why they are not simply called "python packages" but "wheels", so they have distinct meaning, you chose to go on a tirade about why they are not simply called "packages" instead?
The confidence of some HN commentators never ceases to surprise me
Re: 99% of top Python packages are now wheels
#3930 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".
We are not even able to align all of this shit in one great platform.
There is 0 reason why all of this is so unaligned.
Alone how many people maintain packages for different Linux distirs etc.
Maintain it once together and only promote it for your distri when you like it.
Soooo much energy wasted