Clojurians Log v2

The readme states: > The python.edn will be overwritten by each JVM start. But I think, you mean the pyproject.toml is overwritten?!

I like the idea of a disposable python environment. 😃

yes....indeed. I update docu

'uv' make this feasible, because it is blazing fast (as using a host cache), so even a "re-install" of complex dependencies is fast after the first time. and "uv sync" does usually not re-install existing python libraries. So in most cases the JVM start is only marginally delayed by "uv sync" (and I have nice logging when it (re)-installs) Installing "torch" downloads nearly 1 GB (the first time) and some libraries "compile" while installing

Maven for python. 😜

indeed. To me it is a big convenience improvement for libpython-clj.

The python environment handling is my main grudge with python.

(was ....)🙂

Thanks for tackling this!

Currently it runs "uv sync" which should mostly do its job. I could add a kind of ":purge" config, which does: "uv venv --clear && uv sync" instead. This guaranties even more "disposable" venvs. Due to the aggressive "caching" of uv, this should still be fast in most cases (but it will be slower then "uv sync")

(the 'uv sync' would remove "extra" packages, not mentioned in python.edn so there should be no difference in most cases