#pyenv — Public Fediverse posts

VSCode-Based Extensions Can Be Taught! https://medium.com/p/vscode-based-extensions-can-be-taught-aba138fdbf0c?source=social.tw

#direnv #vscode #cursor #extensions #environmentvariables #sdkman #nvm #pyenv

VSCode-Based Extensions Can Be Taught! https://medium.com/p/vscode-based-extensions-can-be-taught-aba138fdbf0c?source=social.tw

#direnv #vscode #cursor #extensions #environmentvariables #sdkman #nvm #pyenv

today i removed #pyenv, #rbenv, #nvm with #mise. much cleaner now

https://fundor333.com/post/2026/why-do-i-disinstall-poetry-and-use-only-uv-/

#poetry #pipenv #pyproject #pyenv #uv #makefile #make #precommit #dev #fingerfood

https://fundor333.com/post/2026/why-do-i-disinstall-poetry-and-use-only-uv-/

#poetry #pipenv #pyproject #pyenv #uv #makefile #make #precommit #dev #fingerfood

https://fundor333.com/post/2026/why-do-i-disinstall-poetry-and-use-only-uv-/

#poetry #pipenv #pyproject #pyenv #uv #makefile #make #precommit #dev #fingerfood

https://fundor333.com/post/2026/why-do-i-disinstall-poetry-and-use-only-uv-/

#poetry #pipenv #pyproject #pyenv #uv #makefile #make #precommit #dev #fingerfood

Dass es so lange gedauert hat, lag daran, dass ich an einigen Stellen für mich #Neuland betreten habe und das für meine Notizen ordentlich dokumentiert habe. Dabei habe ich aber einiges gelernt:

- über #python und #pyenv

- über #osxphotos und die Fülle an Möglichkeiten

- über die #Apple Photo-Library und ihre Struktur

- darüber, dass Zeitstempel im Dateinamen von Fotos keine Selbstverständlichkeit sind 😂

Dass es so lange gedauert hat, lag daran, dass ich an einigen Stellen für mich #Neuland betreten habe und das für meine Notizen ordentlich dokumentiert habe. Dabei habe ich aber einiges gelernt:

- über #python und #pyenv

- über #osxphotos und die Fülle an Möglichkeiten

- über die #Apple Photo-Library und ihre Struktur

- darüber, dass Zeitstempel im Dateinamen von Fotos keine Selbstverständlichkeit sind 😂

Dass es so lange gedauert hat, lag daran, dass ich an einigen Stellen für mich #Neuland betreten habe und das für meine Notizen ordentlich dokumentiert habe. Dabei habe ich aber einiges gelernt:

- über #python und #pyenv

- über #osxphotos und die Fülle an Möglichkeiten

- über die #Apple Photo-Library und ihre Struktur

- darüber, dass Zeitstempel im Dateinamen von Fotos keine Selbstverständlichkeit sind 😂

Dass es so lange gedauert hat, lag daran, dass ich an einigen Stellen für mich #Neuland betreten habe und das für meine Notizen ordentlich dokumentiert habe. Dabei habe ich aber einiges gelernt:

- über #python und #pyenv

- über #osxphotos und die Fülle an Möglichkeiten

- über die #Apple Photo-Library und ihre Struktur

- darüber, dass Zeitstempel im Dateinamen von Fotos keine Selbstverständlichkeit sind 😂

ich hätte gedacht, das geht „schnell mal eben“, aber es hat dann doch etwas länger gedauert. Ich habe das jetzt in einem #pyenv virtual environment laufen und der #shortcut ruft es auf,exportiert alle Fotos und Videos in eine Struktur /Jahr/Monat/Erstellungsdatum-Filename und benennt die Dateien passend um. So kann ich die Bilder nach Zeitpunkt sortieren. Es gibt auch andere und vielleicht einfachere Möglichkeiten der Installation z.B. über #homebrew, aber für mich war das das Mittel der Wahl

ich hätte gedacht, das geht „schnell mal eben“, aber es hat dann doch etwas länger gedauert. Ich habe das jetzt in einem #pyenv virtual environment laufen und der #shortcut ruft es auf,homebrewert alle Fotos und Videos in eine Struktur /Jahr/Monat/Erstellungsdatum-Filename und benennt die Dateien passend um. So kann ich die Bilder nach Zeitpunkt sortieren. Es gibt auch andere und vielleicht einfachere Möglichkeiten der Installation z.B. über #homebrew, aber für mich war das das Mittel der Wahl

ich hätte gedacht, das geht „schnell mal eben“, aber es hat dann doch etwas länger gedauert. Ich habe das jetzt in einem #pyenv virtual environment laufen und der #shortcut ruft es auf,exportiert alle Fotos und Videos in eine Struktur /Jahr/Monat/Erstellungsdatum-Filename und benennt die Dateien passend um. So kann ich die Bilder nach Zeitpunkt sortieren. Es gibt auch andere und vielleicht einfachere Möglichkeiten der Installation z.B. über #homebrew, aber für mich war das das Mittel der Wahl

ich hätte gedacht, das geht „schnell mal eben“, aber es hat dann doch etwas länger gedauert. Ich habe das jetzt in einem #pyenv virtual environment laufen und der #shortcut ruft es auf,homebrewert alle Fotos und Videos in eine Struktur /Jahr/Monat/Erstellungsdatum-Filename und benennt die Dateien passend um. So kann ich die Bilder nach Zeitpunkt sortieren. Es gibt auch andere und vielleicht einfachere Möglichkeiten der Installation z.B. über #homebrew, aber für mich war das das Mittel der Wahl

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.

https://github.com/pyenv/pyenv/issues/2980

#Python

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.

https://github.com/pyenv/pyenv/issues/2980

#Python

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.

https://github.com/pyenv/pyenv/issues/2980

#Python

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.

https://github.com/pyenv/pyenv/issues/2980

#Python

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.

https://github.com/pyenv/pyenv/issues/2980

#Python

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

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

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

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

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

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

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

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

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

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

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*

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*

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*

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*

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*

Today I know more about #Python #pyenv 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.

https://github.com/pyenv/pyenv?tab=readme-ov-file#understanding-shims

Today I know more about #Python #pyenv 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.

https://github.com/pyenv/pyenv?tab=readme-ov-file#understanding-shims

Today I know more about #Python #pyenv 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.

https://github.com/pyenv/pyenv?tab=readme-ov-file#understanding-shims

Today I know more about #Python #pyenv 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.

https://github.com/pyenv/pyenv?tab=readme-ov-file#understanding-shims

Today I know more about #Python #pyenv 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.

https://github.com/pyenv/pyenv?tab=readme-ov-file#understanding-shims

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 🐍 🦀

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 🐍 🦀

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 🐍 🦀

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 🐍 🦀

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 🐍 🦀

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

#nushell #pyenv #python #espidf #esp32

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

#nushell #pyenv #python #espidf #esp32

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

#nushell #pyenv #python #espidf #esp32

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

#nushell #pyenv #python #espidf #esp32

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

#nushell #pyenv #python #espidf #esp32