![](https://feddit.de/pictrs/image/ce089e38-842d-4442-ac7f-25531382ab83.jpeg)
![](https://programming.dev/pictrs/image/1d99f7cb-50e7-4994-94c4-fd23f30209b7.png)
python -m http.server
came in handy so many times!
python -m http.server
came in handy so many times!
Yes, that’s a good alternative for Collection[str]
but not so much for Iterable[str]
as you lose the lazyness of Generators.
Maybe something like passing in a list of patterns which should match some data, or a list of files/urls to download would be examples of where I would like to be generic, but taking in a string would be bad.
But the real solution be to convert it to foo(*args: str)
. But maybe if you take 2 Container[str]
as input so you can’t use . But no real world example comes to mind.
Yes, you’re right. It also a lot of benefits.
This + an assert seems like the way to go. I think that str
should never have fulfilled these contracts in the first place and should have a .chars
property that returns a list of one-character-strings.
But this change would break existing code, so it is not going to happen.
str
matches most of these contracts, though, requiring additional checks if a str
was passed or one of these collections containing strings.
But what if you actually don’t want str
to be valid?
I know that Iterable
and Collection
aren’t the same. My point is, that if you use Iterable[str]
or Collection[str]
as a more flexible alternative to list[str]
you no longer have any type-hinting support protecting against passing in a plain string and you could end up with a subtle bug by unexpectedly looping over ['f', 'o', 'o']
instead of ['foo']
.
For now. YouTube constantly changes stuff, requiring changes to newpipe. As no one will merge these into the fork, it will stop working when that happens.
Seems like it is no longer maintained. Unfortunately that means it is only a matter of time until it breaks forever.
Firefox, Neovim, Tmux, Various KDE applications, Nextcloud, Wine, Signal, OpenSSH
Probably many more
It’s a bit trickier since that is a neovim plugin so a bunch of people will automatically have updated to this tag using their plugin manager. Removing it will probably just make it worse.
I assume the accident was not to force push, but to the wrong branch
What a terrible visualization
Just use poetry then
Because it stops them from feeling like shit because of withdrawal.
If you connect songkick to last.fm you will get notifications for any artists you listen to, without explicitly following each one.
Why not use from __future__ import annotations
?
Looks very broken on mobile.