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’d say it was mostly the general 2014 vibe. But yes, I listened to Klangkarussell and many other German producers. I was probably most influenced by Alle Farben, who was known for his mixtapes before he started producing his own tracks (which I wasn’t really a fan of). But I also showcased a darker side in some of my mixtapes (like "Der schwerste Gang einer Ente" where I used artists like Burial).
I saw myself more as a consumer than a producer. I mainly created mixtapes because I was constantly discovering and consuming new music. When I had the chance to play at a club or an open-air event (I tried it once), I quickly realized I wasn’t too comfortable performing in front of an audience :)
Around that time, I had just started learning to code and built my first little automations to help me discover even more music on SoundCloud. So I noticed this was another (more lucrative with the similar level of passion) career path where I didn't had to be in front of an audience.
His main policy seems to be to show the world that he's a big man with big genitalia. And in fairness, he is quite successful at that because much of the world thinks him a gigantic dick.
I'm not really joking, because that really does seem to be the underlying philosophy in what he does: it's whatever he thinks makes him the "big man tough guy". Trying to analyse things beyond that just doesn't make much sense.
Not particularly "show the world" because he's been very demonstrably weak internationally. He's a showman who makes very bold sounds, but his actions show that he will give in to China on Taiwan, like he gave into them on Hong Kong, like he gave in to Russia on Ukraine, like he gave into North Korea on nukes...
Now on Taiwan, he's already stated previously that he will _tax_ China if they invade Taiwan. This contradicts long standing US policy of not stating exactly what action the US will take in the event of invasion, and has had the result of pushing up projections of exactly WHEN China will invade Taiwan to be within the next two years, during Trump's presidency.
The only thing that will possibly make this change is as a condition of financial supporter Elon Musk, who needs those NVIDIA cards that come out of Taiwan so he can pursue his religious mission of winning the AI race. And that's only if TSMC manufacturing capabilities can't be dragged out of Taiwan and set up elsewhere in a sufficient timeframe to reduce the impact if China were to invade Taiwan.
> he's been very demonstrably weak internationally
What you or I view as "big man tough guy" doesn't necessarily align with what Trump views as "big man tough guy". In Trump's view, "solving" the problem of Taiwan one way or the other, when so many other presidents have "failed" to do so, makes him the big man. Whether he completely screws over American interests in the process – never mind the people of Taiwan – doesn't really enter in the calculation.
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".
Ah, I understand now. Well, by default Python doesn't declare a return type either yet the tools are able to infer it in many cases; I see no reason why tools like mypy couldn't similarly infer the raised exception types as well.
Plus, the typing annotations could presumably be expanded to include some notification to declare raised exception types explicitly.
reply