pip installing etils spews warnings about etils HOT 2 CLOSED

Thanks for the feedback. The plan for etils is to be the home of various self-contained utils without having to create a new independent project each time.

Once one of those util become mature enough, they can be moved to their own self-contained project. Indeed this seemed like a good idea for epath (though I do not own the epath PyPI project, so I might have to rename it).

I'm confused though why you have to call pip install etils[all] manually. Installing pip install jax should install the required etils deps. Also I wasn't able to reproduce the issue. etils is at version 0.6.0 so not sure why your PyPI try to install 0.3.3.

from etils.

I was trying to install an older version of jax to run some research code, and I guess that jax / project referenced 0.3.3.

The root problem here is that etils has so many sub-targets. For enterprise users, I'm sure there's patience for such a complicated build, but for research, this sort of ancillary complexity is a non-starter. I'm not a Googler, but I'm pretty sure this library violates the design recommendation of "don't try to do too many things in one library." I guess this project grew organically due to these sorts of problems: https://www.youtube.com/watch?v=3t6L-FlfeaI

i dunno, I'm gonna stick to pytorch. I can barely get Jax to work with modern GPUs....

from etils.