I don't see why you need a singleton, just use use a global variable if you really need one. A singleton has all the same downsides but just hides them by not looking like a global.
https://nedbatchelder.com/blog/202204/singleton_is_a_bad_idea.html
Nice job creating this community!
I'm always interested to hear in any tips or tricks, or just in general workflows people have found work for them.
VSCode is my main editor, but I feel I haven't explored or learned it's features as much as I could (I could really do with learning some more keyboard shortcuts). Anything to remind me or help me with that would be super cool :)
Thanks for the info on crossposting! I thought I'd seen someone mention a cross posting feature but couldn't see any button to do it. I'm using the Jerboa app on Android which I guess doesn't have that button, but I see it on the website now as you say.
It's also good to know that linking to the original URL is generally better and the rest can be handled by the UI - that does seem nicer.
Great TIL, I hate it.
Excellent how the page alludes to other horrible things to imagine, like "don't pour hot oil into your ear", and "don't pour it in if there's a hole in your eardrum"
I find it funny how the updates slowly seem to realise that people can't access the GitLab issue because it's down.
Starts with "details in", then "details will be posted", then "will be posted once available" then "once availability has been restored"
My general opinion for libraries is that it's fair to stop supporting Python versions as soon as they're EOL. It's unfair to ask maintaners to have to juggle supporting 6 or more Python versions at once, mostly for the benefit of a few companies who haven't updated yet.
I think it's also fair here, you'll still be able to use older versions, you just won't get the newest features, which clearly isn't your number 1 priority if you're still using Python 3.7.
I'd be happy if we'd just accepted "referer" as the correct spelling for everything, but instead we have the "Referrer-Policy" header, so now I need to check the correct spelling for anything involving referring..
I do sort of like the idea that because we want to keep backwards compatibility on software we just change the language instead since that's easier.
You still need to import the type before using it in a stringified type annotation for it to be valid though, so you'd need the import in an if TYPE_CHECKING:
block either way, no?
@qwop
@programming.dev