Discovered [nushell](https://www.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
Switching from Pyenv to Uv
https://bluesock.org/~willkg/blog/dev/switch_pyenv_to_uv.html
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
Use #pyenv 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])"'
I know, I know, I'm late to the party
#UV is awesome 
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.
Using pyenv and pyenv-virtualenv to install Python and create a virtual environment on MacOS https://www.andreagrandi.it/posts/install-python-with-pyenv-and-pyenvvirtualenv-create-virtual-environment-with-specific-python-version-macos/
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 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: https://www.python.org/ftp/python/2.7.18/Python-2.7.18.tar.xz
EDIT: not just me: https://github.com/python/cpython/issues/127307
EDIT #2: here's a workaround:
wget https://ftp2.osuosl.org/pub/blfs/conglomeration/Python/Python-2.7.18.tar.xz -P ~/.pyenv/cache/
pyenv install 2.7.18
@fst I also experienced this as well. I was using standard #pip and #pyenv for our tools. Another team was using #poetry.
What really sold me is that uv speed up our pipeline by 2.5x compared to pip (both were using caching). The hype around #uv is real and the problems is solves so effectively is why it will be the new standard.
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.
Attached is yet another article that tries to clarify the options for python package management. The problem is that this space is dynamic and overpopulated, so any article quickly becomes out of dare. https://salas.com/2024/11/15/niels-cautaerts---python/#python #python-package #explainer #dependencies #package #pyenv #uv
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.
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.
3.13 not found on #pyenv
All right, I guess I will have to wait (yes, I did upgrade pyenv already) 
gihyo.jp 
