Python Envy Jnr

NOTE: Fork of Python Envy

Automatically activate Python virtual environments as you navigate the source code.

This is useful if you are working with a monorepo that contains sub-projects, modules, libraries or deployments with different Python dependencies. Or perhaps you want to automatically activate a development environment when you click on a test file.

Josh's edit: needed to configure python envy for my needs, hence: python envy junior. A folder structure on a monorepo project I am on doesn't use the .venv and there is no way to remove it and get the desired result hence, extending mine to work without configuring the default. Would have love to suggest to the main - Python Envy. Turns out it wasn't unstable, but I couldn't run it alongside the main Python Envy extension - so I had to disable it.

Much Thanks to you, Sir Robert Smith - teticio for Python Envy!

May also consider:

• walking the tree to support other envs just like is the default on ST4 for me.
• looking to cache the environments per workspace to make the call faster (not sure if it is possible but if it is, sure why not!)
• looking for other ways to make this faster.

Features

As you can see in the following demo, the active Python environment changes as soon as a file is loaded into the editor. You may want to consider only enabling the extension for specific workspaces.

Requirements

The Python extension must be enabled for this to work.

Extension Settings

This extension has the following setting:

• pythonEnvyJnr.venv: Location of the virtual environments. Set to "" (read: empty) by default. (depending on your workspace environment, do add .venv or whatever path is used for your virtual environment setup. This project is assuming, all repos in the monorepo are using the same setup)

Known Issues

N/A

Release Notes

[0.1.10]

• Feature: allowing users set virtual environment path per workspace or defaulting to empty.
• Feature: some attempt to speed up.