search

wyuenho / emacs-pet

Tracks down the correct Python tooling executables from your virtualenvs so you can glue the binaries to Emacs and delete code in init.el
GNU General Public License v3.0
105 stars 13 forks source link

Manual venv selection? #33

Closed sho-87 closed 3 months ago

sho-87 commented 7 months ago

I realize a large part of this project is to auto identify venvs, but wondering if theres a possibility of a manual mode? Where the user can provide a path to a venv directory or choose from a list of available venvs

There are times where I'm working on a single script that doesnt have all the scaffolding of an actual project, and I just want to temporarily borrow a venv from somewhere else (as it might have linters etc setup already). Or if I'm working in a project with its own venv but want to switch to another venv temporarily as it has different versions of dependencies

The closest Ive been able to find is pyvenv, but it doesnt change the paths for all the tools (flycheck, lsp etc)

wyuenho commented 4 months ago

Not currently. Firstly there's #30 and #31, secondly I'd really like to not evolve PET to any of the dozen Emacs virtualenv tools out there. PET is not a tool for your terminal, it is a tool for your Emacs buffers.

That said, by default PET detect these patterns in your project. Why don't you just symlink the virtualenv in your new project and see if that works for you.