Post

multi-pwsh 0.7.0 is out with initial #PowerShell virtual environment (venv) support, through runtime hooking of PowerShell, PowerShellGet and PSResourceGet! Try it out now, let me know what you think 👇 github.com/Devolutions/...

Josh Hendricks | MVP

@joshooaj.com

27 Mar

Cool! I don't do a lot of python dev but when I use venv there I'm used to creating a .venv/ folder at the root of the workspace/repo (and adding it to .gitignore). It looks like the primary usage pattern here is to create a named env under ~/.pwsh right?

Marc-André Moreau

@awakecoding.com

Yes, I'm creating them under ~/.pwsh/venv by default when specifying just the name, but I have added support for environment variables to override the paths, and also accept a full path to the venv. I'm trying to make it easy but flexible for various use cases

27/3/26, 4:36 am0 reposts1 like

Josh Hendricks | MVP

@joshooaj.com

27 Mar

I really dig this, definitely trying it out soon. Thanks!

Marc-André Moreau

@awakecoding.com

27 Mar

Tell me what you think! I'd like to keep improving it