Search
1000 results for “diazona”
-
@diazona @nazokiyoubinbou @RamenCatholic @Taweret I was just thinking "they should make a 70s bad trashy space opera but with modern special effects" but that's Rebel Moon and I'm not interested in that.
It's not camp enough from what I can see -
@diazona two bears walked into a bar which was stupid because the second one shoulda seen it coming
-
@diazona You'll be FINE
-
@diazona having to sacrifice a dog to jump to the next star system would be pretty dark 😬 #Monsterdon #Wormholes
-
@diazona @RobynGoodfellow Didn't Hillary Clinton have one of those? The National Enquirer said so.
-
@diazona I would take her invasion any day over the moon creatures.
-
@diazona I missed having a lot of the squares you have, or they weren't arranged well, when I did have them, so I didn't get a bingo this week.
-
@diazona Wow, well done
-
One brief note: when David says the "new way" is to use Python virtual environments, that's extremely relative. It has been best practice (and the only way to save your sanity because of dependency hell in any nontrivial project) in the Python community for, I dunno, 20 years? But Python's been around for >30, so it is the "new" way. Long before the `virtualenv` tool I was accomplishing the same thing with symlink trees to isolate interpreters.
There are lots of opinions on where you should keep your venvs, i.e. what the path to them should be. I personally like putting them in the project directory, typically `<project>/.venv`, but others like to stash them away someplace, like in ~/.local/share. Project tools that handle virtualenv management (e.g. poetry, uv, etc) will generally give you a way to control where they create the venvs.
-
@diazona Thanks -- I really want to watch (these increasingly hateful*) people, but maybe I should just crash... #TheCatGirl 🐆 #Monsterdon
* #BarbaraShelley's character is DA BOMB thō
-
I've spent the last couple of hours trying to set up an abandonware project that is purely setup.py-based. I don't miss these at all.
