11–20 of 79 posts
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".
Earlier quoted context omitted.
Which would make the article completely redundant, and that works for me. :D 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 and would make me read it in full, as opposed to now when I just facepalmed.
> 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…
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".
Rpms, apks, debs, msi, exe, tarballs, zips, jars, wars...
But when a language ecosystem opts for cutesy niche names then they just end up confusing everybody, including some of their own users.
What does this mean?
"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]
Earlier quoted context omitted.
Rpms, apks, debs, msi, exe, tarballs, zips, jars, wars...
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.
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
Earlier quoted context omitted.
Yes, but if we just called them packages the headline would be "99% of top Python packages are now packages"
Which would make the article completely redundant, and that works for me. :D 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 and would make me read it in full, as opposed to now when I just facepalmed.
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".
You're completely right. The site doesn't even bother to explain what "eggs" are. And while it lists the benefits of wheels, there is no word about the apparent downsides of eggs, or maybe a little comparison table.
In other words, can someone put a line like this into their requirements.txt file?
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".
So, "Packages are the new standard of distributing packages, and replace packages" is clearer to you?