I've been using Python since like 2011 and I still read PyPy and think PyPI.
Naming things is hard but it would be nice if people tried a bit harder to avoid clashes at least within the same ecosystem.
Naming things is hard but it would be nice if people tried a bit harder to avoid clashes at least within the same ecosystem.
[edit]: After some searching, I notice that PEP 301 is actually dated Oct 2002, so perhaps I'm wrong. The public/advertised name was Cheese Shop for quite some time after that, but apparently the name PyPi was at least suggested much earlier than I thought.
This is why python has wheels.
So wheel is to cheese, as loaf is to bread.
https://www.chucklingcheese.co.uk/news/cheese-gift-guides/wh...
https://dustingram.com/talks/2018/10/23/inside-the-cheesesho... (halfway through)
PyPI is sometimes called the Cheeseshop.
This is a reference to this Monty Python skit, where a man goes into a cheeseshop which has no cheese for sale.
The joke is that when PyPI was first created, there was nothing in it. Hence, "The Cheeseshop".
But it does have stuff in it now, so it's not really even appropriate to call it that anymore.
Addendum: Every time I tried to understand Python packaging, I would come across the term "wheel" and my eyes would glaze over because I couldn't figure out what it was from context ("what the heck is a wheel?"). Maybe now I'll go back and finally understand Python packaging.
People having fun naming their projects with references or puns or whatever might make them more likely to make the project to begin with, which is probably more important. But even within Python, it's much easier for me to remember "ok, I need install numpy and requests," than "ok I need Beautiful Soup and Twist" or whatever.
that's 1 unit of a production of cheese is called a wheel.