home.social

#pyenv — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #pyenv, aggregated by home.social.

fetched live
  1. Looks like #pyenv releases will now be more closely in sync with #CPython releases thanks to some newly implemented automation. That's great news!

    Thanks to the devs for making this happen.

    github.com/pyenv/pyenv/issues/

    #Python

  2. One Open-source Project Daily

    pyenv is a simple python version management tool. It lets you easily switch between multiple versions of Python. It's simple, unobtrusive, and follows the UNIX tradition of single-purpose tools that do one thing well.

    https://github.com/pyenv-win/pyenv-win

    #1ospd #opensource #pyenv #pyenvalternative #pyenvforwindows #pyenvwin #pyenvwindows #python #pythonversionmanagement #windowspyenv #windowspython

  3. Not that anyone has asked, or cares, about my podunk, backwater processes. There's a few reasons why I haven't migrated my #Python work to use #uv

    1. I don't care about performance. My work is done on a potato machine and it won't make much difference, to me. For now.
    2. I prefer to keep the VC funded company Astral at arms length, pay attention, and see how the tool development plays out.
    3. I actually like watching individual projects like #pyenv #pipx and the rest. How they work as a community, handle bugs and new features.

    I did the same with the flake8 module projects before I commited to using ruff several years ago. YMMV

  4. Huh. This is a new one.

    Somehow, I've managed to pollute my #Python pip userspace with a bunch of packages from a #Poetry project I normally work on.

    Fortunately, I could just easily rebuild with #pyenv and #pipx. Just kinda weird that it happened in the first place. I might have to go back to explicitly using `poetry shell` for isolation. *shrug*

  5. Today I know more about shim's fall through to the system default than I did yesterday.

    Stumbled upon a problem I didn't realize that I was having. Testing against an older version of an older version(3.11.2 vs 3.11.12) because it wasn't specified in the pyenv global. 🤦 Now I know.

    So...I've got that going for me.

    github.com/pyenv/pyenv?tab=rea

  6. Throughout the years, I switched from #conda -> #pyenv + #poetry -> #uv, and I think I'm finally settling down now. uv made me even ditch #pipx as a global #python tool manager. The #astral folks have done a really superb job 🐍 🦀

  7. Discovered [nushell](nushell.sh) this weekend. Looks pretty cool. Tried it, but there are two things that prevent me from making it my new default shell:
    1. pyenv: pyenv init does not work with nushell
    2. ESP-IDF: ESP IDF's export scripts do not work with nushell

    #nushell #pyenv #python #espidf #esp32

  8. 671 - Descubre la herramienta que cambiará como usas Python

    #uv es la herramienta perfecta para gestionar proyectos y dependencias de #python y que viene a sustituir a #pip #poetry #pyenv #virtualenv y otras

    Como ya te he comentado en mas de una ocasión, la llegada de Rust, está suponiendo una auténtica revolución. Los desarrolladores apoyados en Rust se ha

    youtube.com/watch?v=Jb-9QII_E1Y

    #atareaoConLinux #podcastesp

  9. Use but only the CPython releases?

    A bash alias to filter on the latest, supported versions:

    alias pyenv_list='pyenv install --list | grep -E " 3\.([9]|1[0-4])"'

  10. After programming a good 2 months in #python finally found the tool #poetry which is quite similar to how #nodejs bundles libraries into a directory either locally or globally in the cache directory.

    I have tried the other tools from #pyenv to #venv and/or #virtualenv. Where I thought they were used to deal with library dependency management only to realize that they are more like #nvm.

    I did use #conda for some time, though preferred a python only solution. I do realize that poetry won't resolve all issues and might need to look into to containerization later on, though for the time period it looks like a good solution.

  11. Using pyenv and pyenv-virtualenv to install Python and create a virtual environment on MacOS andreagrandi.it/posts/install-

    I keep referring to this blog post of mine a lot. I'm glad I took some time to note all my process so I can reuse it int he future (and hopefully it's useful for other people too)

    #Python #pyenv #virtualenv

  12. Update: 0.5.9 solves this problem ! This means I can (almost) use uv everywhere in my workflows. The only remaining exceptions are debug builds, pre-releases and versions older than 3.8, all of which I can still get through !

  13. #Python #pyenv folks: are downloads returning 403 for anyone else, or just me?

    Running `pyenv install 2.7` is giving me a HTTP 403 error when trying to hit the URL: python.org/ftp/python/2.7.18/P

    EDIT: not just me: github.com/python/cpython/issu

    EDIT #2: here's a workaround:
    wget ftp2.osuosl.org/pub/blfs/congl -P ~/.pyenv/cache/
    pyenv install 2.7.18

  14. Just tried the #uv #Python management tool. At first I thought: Oh no, not another Python package manager. But this one seems different. It combines all the pip-tools, #pyenv, #poetry, #virtualenv, etc in one.
    And it's damn fast. This likely will stay with me for a while.

    docs.astral.sh/uv/

  15. CW: Essential Python Programming Tip

    Do not use system #python in your projects. System python and its related packages are for other system packages to depend on.

    I recommend using #pyenv to install python versions for use in your projects.

    it goes something like this:

    (install #homebrew)
    $ brew install pyenv
    (do the shell integration thing)
    respawn shell
    $ pyenv install 3.12.7
    $ pyenv global 3.12.7

    #asdf can also install pyenv.

    I am not your consultant.

  16. Okay, I got my coding tools sorted out on both my #windows half and my #archlinux half now.

    So far that consists of #rustup (for #rustlang vers), #gcc, and #pyenv (for #python vers).

    ...I'm *not* sure if I should look into a version manager for #nodejs or #php just yet, since that affects the web dev stuff I do on the side.

  17. One nice thing about switching from #pyenv and #pyenvvirtualenv to #uv is that #CleanMyMacX used to throw away my pyenv virtual envs. They lived in a cache directory. That doesn’t happen any more.

  18. 3.13 not found on #pyenv

    All right, I guess I will have to wait (yes, I did upgrade pyenv already) 🤷🏻‍♂️

    #python