Ms. ArmoredThirteen

  • 1 Post
  • 18 Comments
Joined 5 months ago
cake
Cake day: December 8th, 2024

help-circle










  • O’Rear used a Mamiya RZ67 medium-format camera on a tripod and Fujifilm’s Velvia color film that saturated green and blue colors.[7][10]: 2:29 [11] He credited the combination and said that if he had shot with 35 mm film, it would not have had an identical result.

    Claim is it hasn’t been edited but it did use film that saturates certain colors by default



  • Oh man a couple months ago I had to back off a topic because my therapist was obviously about to cry and just barely holding it together… I’m trans and was talking about my worries with how the US is going. They have trans kids and I think my concerns were hitting close to home for them. It was a difficult session for everyone x.x


  • I don’t have kids but this is pretty much how my dad raised me. It made me really respect when he gave me a hard no for something, it meant “no really the risk majorly outweighs the reward” and even if I didn’t understand it at the time I trusted it. I got a lot of I told you so after varying seriousness of injuries lol. Eventually I learned that the soft warning meant I was going to have a lot of fun but I needed to be ready for if it went sideways. Now I’ve got a pretty healthy sense of my own limits and when to start gauging risk/reward



  • 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






  • I consider $100k to be minimum wage in Seattle. It was just enough to not be constantly money stressed as long as I was living modestly. I could see doctors, invest in hobbies, have choices in food, build savings/retirement. Could not eat out every day, buy a house any time soon, or impulse buy particularly expensive stuff. Any time I made less than $100k here I felt like I was always two steps behind, at about that salary my life stopped focusing on scraping by. I make more now and I feel like I’m actually thriving here. Still quite a difference in what I’d consider to be middle class though like there’s no way I can get a house here and I’d for sure be much worse off if I had kids