autoenv

I have a somewhat particular setup where I use conda to manage my envs, and autoenv[0] to ensure the env for a given project is active once I'm in the folder structure. So there's a .env file containing "conda activate <env_name>" in each. I also use Emacs as my sole IDE, but there are quite a few instances where support falls short for modern workflows. I use the pylsp language server, and it's only able to provide completions, etc for native libraries, since by default it doesn't know how to find the envs containing extra 3p packages. And so I wrote a patcher[1] that searches the project folder and parents until it finds an appropriate .env file, and uses it to resolve the path to the project's env. With the latest changes to the patcher it now uses the output from "uv sync", which is the path to a standalone script's env, as well as th

I'm using autoenv - https://github.com/inishchith/autoenv. The workaround that I've found for this problem is to set "AUTOENV_ENV_FILENAME=.env.user" and then inside the project folder, I'm now using ".env.user" instead of just ".env". I'll use this hack until Docker guys fix Docker Compose.

Sure, but I still don't get why it is missing from the project list. The list is not that curated. It includes Autoenv for example, a project whose Github README [0] says, "Note: you should probably use direnv instead. Simply put, it is higher quality software. But, autoenv is still great, too. Maybe try both? :)" [0] https://github.com/kennethreitz/autoenv

I'm asking as someone who is mid level Python & DS experienced and out of real curiosity (not a "mine is better than yours" thought): Could you elaborate what in your opinion makes anaconda superior? I am frequently doing data munging & low level ML things and - so far - I am more happy with the pip side of things as a combination of virtualenv, autoenv [1], pip tools [2], pyup [3] and the rest of the eco system. Standard procedure, takes two minutes and I have a Jupyter notebook up, smartly automated base processes for dependency management, full control of environment variables and can deploy/ integrate this in any other Python setup (if I were to port IPython code to pure Python). Is this more a thing of each his own or am I missing a crucial advantage of Anaconda? [1] https://github.com/kennethreitz/autoenv [2] https://github.com/ja

There are a couple of tools to automatically manage virtualenv activation/deactivation, like autoenv[0] & detect_virtualenv[1]; [0]: https://github.com/kennethreitz/autoenv [1]: https://github.com/dgholz/detect_virtualenv

Thanks for sharing, will definitely use it! As a somewhat related tool, I started using autoenv (https://github.com/kennethreitz/autoenv) a while ago (automatically sources a .env file when you cd into the directory). I use it to set environment variables, start docker images...

There isn't an builtin way to do this in bash but what you are asking for is 2 things: * Trigger an action on changing a directory * That action should be to change your bash history file The second part is pretty easy to do -- you just change the $HISTFILE environment variable and export it. For the first part though, you can either use a naive little function that replaces bash's builtin `cd`[1] or you can use any one of the many tools specifically created for this sort of a thing: http://swapoff.org/ondir.html https://github.com/kennethreitz/autoenv http://direnv.net/ https://github.com/cxreg/smartcd Note however, that most unix tools are angnostic to the current working dir so... $ /path/to/cmd /some/other/path/to/argument $ cd /path/to && ./cmd /some/other/path/to/argument $ cd /some/other/path/to && /path/to/cmd argum

Not the most responsive maintainer - still waiting on him to tag a 1.0.0 release for autoenv - https://github.com/kennethreitz/autoenv/issues/82

Awesome, thank you for trying this. Please make a github issue or email me if you have any suggestions informed by the experience :) edit: That one feature reminded me of Kenneth Reitz's autoenv (https://github.com/kennethreitz/autoenv). I can't do anything to futz with cd, but it could be possible to reverse that and cd to a project directory when a virtualenv is activated, I am just not sure yet mechanically the right way to choose which one. Worth considering.

I wonder why pythonbrew gets no love - http://stacktoheap.com/blog/2013/03/11/why-use-virtualenv-wh... For me, pythonbrew + autoenv ( https://github.com/kennethreitz/autoenv ) is must for development.