Ms. ArmoredThirteen

  • 1 Post
  • 24 Comments
Joined 1 month ago
Cake day: December 8th, 2024
  • Ms. ArmoredThirteen@lemmy.zipOPtoSteam Deck@sopuli.xyz•Using source command for virtual Python environment [solved]English
    4·
    5 days ago

    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!

  • Ms. ArmoredThirteen@lemmy.zipOPtoSteam Deck@sopuli.xyz•Using source command for virtual Python environment [solved]English
    1·
    6 days ago

    Thank you for help with what commands to run to get more info. I’ve tried multiple virtual environments each of ones built on the command line and through VSCode and had the same results with each. The current one that I did the cat command on was built with VSCode.

    cat .venv/bin/activate

    This file must be used with “source bin/activate” from bash

    You cannot run it directly

    deactivate () { # reset old environment variables if [ -n “${_OLD_VIRTUAL_PATH:-}” ] ; then PATH=“${_OLD_VIRTUAL_PATH:-}” export PATH unset _OLD_VIRTUAL_PATH fi if [ -n “${_OLD_VIRTUAL_PYTHONHOME:-}” ] ; then PYTHONHOME=“${_OLD_VIRTUAL_PYTHONHOME:-}” export PYTHONHOME unset _OLD_VIRTUAL_PYTHONHOME fi

    # Call hash to forget past locations. Without forgetting
# past locations the $PATH changes we made may not be respected.
# See "man bash" for more details. hash is usually a builtin of your shell
hash -r 2> /dev/null

if [ -n "${_OLD_VIRTUAL_PS1:-}" ] ; then
    PS1="${_OLD_VIRTUAL_PS1:-}"
    export PS1
    unset _OLD_VIRTUAL_PS1
fi

unset VIRTUAL_ENV
unset VIRTUAL_ENV_PROMPT
if [ ! "${1:-}" = "nondestructive" ] ; then
# Self destruct!
    unset -f deactivate
fi

    }

    unset irrelevant variables

    deactivate nondestructive

    on Windows, a path can contain colons and backslashes and has to be converted:

    if [ “$OSTYPE:-}" = “cygwin” ] | [ "${OSTYPE:-” = “msys” ] ; then # transform D:\path\to\venv to /d/path/to/venv on MSYS # and to /cygdrive/d/path/to/venv on Cygwin export VIRTUAL_ENV=$(cygpath /home/deck/Repos/PysidianSiteMaker/PysidianSiteMaker/.venv) else # use the path as-is export VIRTUAL_ENV=/home/deck/Repos/PysidianSiteMaker/PysidianSiteMaker/.venv fi

    _OLD_VIRTUAL_PATH=“$PATH” PATH=“$VIRTUAL_ENV/“bin”:$PATH” export PATH

    unset PYTHONHOME if set

    this will fail if PYTHONHOME is set to the empty string (which is bad anyway)

    could use if (set -u; : $PYTHONHOME) ; in bash

    if [ -n “${PYTHONHOME:-}” ] ; then _OLD_VIRTUAL_PYTHONHOME=“${PYTHONHOME:-}” unset PYTHONHOME fi

    if [ -z “${VIRTUAL_ENV_DISABLE_PROMPT:-}” ] ; then _OLD_VIRTUAL_PS1=“${PS1:-}” PS1='(.venv) ‘“${PS1:-}” export PS1 VIRTUAL_ENV_PROMPT=’(.venv) ’ export VIRTUAL_ENV_PROMPT fi

    Call hash to forget past commands. Without forgetting

    past commands the $PATH changes we made may not be respected

    hash -r 2> /dev/null

    which python

    /usr/bin/python

    python -m pip freeze (before source)

    aiohttp==3.9.1 aiosignal==1.3.1 anyio==4.2.0 attrs==23.2.0 btrfsutil==6.7.1 certifi==2024.2.2 cffi==1.16.0 click==8.1.7 crcmod==1.7 crit==3.18 cryptography==41.0.7 dbus-next==0.2.3 dbus-python==1.3.2 distro==1.9.0 evdev==1.6.1 frozenlist==1.4.1 h11==0.14.0 hid==1.0.4 httpcore==1.0.2 httpx==0.26.0 idna==3.6 iotop==0.6 multidict==6.0.4 nftables==0.1 packaging==23.2 perf==0.1 ply==3.11 progressbar2==4.3.2 protobuf==4.25.2 psutil==5.9.8 pyalsa==1.2.7 pyaml==23.9.0 pycparser==2.21 pyelftools==0.30 pyenchant==3.2.2 PyGObject==3.46.0 python-utils==3.8.2 PyYAML==6.0.1 semantic-version==2.10.0 smbus==1.1 sniffio==1.3.0 SteamOS Atomic Updater==0.20190711.0 steamos_log_submitter @ file:///builds/holo/holo/holo/steamos-log-submitter/src/steamos-log-submitter typing_extensions==4.9.0 yarl==1.9.4

    python -m pip freeze (after source)
    No module named pip

  • Ms. ArmoredThirteen@lemmy.ziptoGreentext@sh.itjust.works•Anon visits AmericaEnglish
    51·
    10 days ago

    What era or genre are you getting the pop culture from? Twinkies at least have only been a joke in media for at least 15 years because of zombie survival stuff, and longer as a ‘haha look at the fat kid’ before that. Die Hard uses them as a comedic element to break up parts of the film but in less of a joking about Twinkies directly way, though it is part of the overweight cop’s character. That movie is nearly 40 years old though and probably marks around the time Twinkies started shifting from a snack to a meme

    Edit to add: They also originally had banana flavored filling. You can still find these sometimes and while not good they’re better than the plain ones imo

  • Ms. ArmoredThirteen@lemmy.ziptoscience@lemmy.world•'Achilles Heel' of Drug-Resistant Bacteria Has Been Found, Scientists SayEnglish
    5·
    11 days ago

    I’ve seen this show up a couple times recently and I’m hesitant to think it’s as bad as advertised. The linked video basically states mirror bacteria has no weaknesses while laser hitting all existing life’s weaknesses. Reporting extremes like that is a red flag and needs some extra scrutiny. Why would it be so one sided like that? Wouldn’t they exist in an equally hostile environment but also be seriously outnumbered?

    For sure we have to be very careful about what we’re making in labs. The warnings I’ve seen about this so far seem very sensationalized though. I’m not a germologist though someone correct me if I’m way off course please