Skip Navigation
InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)MA
Ms. ArmoredThirteen @ ArmoredThirteen @lemmy.zip
Posts
1
Comments
57
Joined
2 mo. ago
  • My grandpa's open air basement toilet had a brick on the lid to keep rats from getting in. The rare times I had to use it I was always so scared of a rat showing up and half the time I couldn't even go because of it

  • Out of curiosity about how old are you? Back in my day sometimes saving just didn't work which is where I built up the habit of saving a couple times. For really important saves using two slots was best just in case one spontaneously corrupted as well

  • I'm incredibly lucky right now this is exactly what my current boss does. It's wonderful and I actually feel like I can get a lot of work done (at least when we're not bogged down with the corporate mandated giant 'scrum' meetings)

  • For me, bouldering has helped a lot. If you already have chronic pain definitely talk with a doctor or physical therapist first though. If you aren't paying attention to your body it's also very easy for climbing to fuck you up more. It's a great combo of core and back strength though that can really help with a lot of things

  • Okay so I wiped the .venv that VSCode made again and this time ran the venv creation using python3 -m venv venv. It's working with command line now but not within VSCode (running into the same issue that I had before but in reverse, so VSCode isn't recognizing pip or other installed modules like markdown that I added in command line).

    This is starting to feel like maybe a difference in how VSCode handles the virtual environment vs the command line. When I create the venv in one it breaks the other

    Edit: Yeah idk what VSCode is up to. I uninstalled, remade the venv with Konsole, and installed PyCharm instead. Commands through Konsole and the PyCharm terminal are all working as expected now.

    Thank you for the help!

  • Steam Deck @sopuli.xyz

    Using source command for virtual Python environment

    I've been trying to code python on my deck and I can't for the life of me figure out how to activate the virtual environment. I keep using "source .venv/bin/activate" and it does nothing. No errors, no feedback, doesn't hang, doesn't use the environment, nothing.

    I've tried installing Kitty to see if it was an issue with Konsole but the exact same thing happens. It works fine in Visual Studio Code but I do t want to have to open that every time I try and run a command.

    Anyone know why this could be or what I could do to fix it?

    Edit to add: This is my first real attempt at Linux idk what I'm doing in a very broad way. Only other time I tried was nearly 15 years ago dual booting Windows/Ubuntu but that lasted like a week because Windows kept blowing up the config and I needed some Windows only programs for school

    Solved edit: I don't exactly know what was up. If I made the venv with the terminal, it would work in the terminal but not work with VSCode's terminal. If I made it in VSCo