The thing about the anti-piracy is true, at least in the original version (I don't know about re-releases).
The way it worked was you had to offer at least a few pizzas that were reasonably close to recipes from the booklet in order to get any customers. Once you had that, you could get creative with custom recipes but if you only did custom recipes, you were bound to fail.
If you want to combine a mixin with a base class you have no control over, just put the base class last in the inheritance chain. Then it does not matter if it calls its super __init__.
This is actually covered by the --locked option that uv sync provides.
If you do `uv sync --locked` it will not succeed if the lock file does not exist or is out of date.
Edit: I slightly misread your comment. I strongly agree that having no lock file or a lockfile that does not match your specified dependencies is a case where a human should intervene. That's why I suggest you should always use the --locked option in your build.
Was there any particular reason you stopped making music?
I'm listening to one of your mixes right now and I'm wondering if you were influenced by Klangkarussell at all (or maybe the other way around?) or if that was just the general 2014 vibe.
I'm not sure I understand the sequence with the rhino. Is he actually killing the rhino by drilling a hole in its back and lighting a stick of dynamite inside the hole? Or am I reading this wrong? That seems pretty out there.
I would also say absolutely. We've been using pipenv for ~6 years and have managed to build a pretty good workflow around it. But uv is just _so much faster_. So we've started moving everything over to uv and I don't think we'll ever look back.
Migrating is not super hard, we wrote a small script that moves all the information from a Pipfile to a pyproject.toml and it works like a charm.
What they mean is that in Java, for example, a method has to explicitly state which exceptions it might throw as part of its signature. Note that they said "throws", not "throw".
I noticed that for every movie on the list that I like, I can totally see how others might not. But for most movies that I dislike, I just don't get how people can genuinely enjoy them.
I don't know what that says about anything but I found it curious.
You might enjoy the podcast "372 pages we'll never get back". It's basically a bad book club. The title is a reference to the first book they cover which is Ready Player One.
They are on Book 23 or so at the moment, more or less alternating between books by "big" authors like Dan Brown or Sean Penn and super obscure stuff like Harry Potter-Twilight-crossover fan fiction.
A full circle is 360° and a curved piece makes a turn of 30°, so you need 360° / 30° = 12 pieces turning in the same direction to make a full circle.
Every time you use a piece turning the other way, you need to add an extra piece turning the way you want to complete the circle, so the difference between the directions has to be 12.
Note, however, that not every track with exactly 12 more pieces turning one way than the other necessarily makes a complete circle, straight pieces can cause the ends not to match up.