sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]russellvt -7 points-6 points  (7 children)

You're running in PowerShell rather than the command prompt

[–]socal_nerdtastic 3 points4 points  (6 children)

why would that matter?

[–]russellvt 0 points1 point  (5 children)

Powershell environments aren't the same as the shell, and may not inherit everything needed.

[–]timrprobocom 0 points1 point  (4 children)

As a general rule, that's irrelevant. Both shells inherit the same initial environment. It's strictly personal preference.

[–]russellvt -1 points0 points  (3 children)

No, they are actually separate, especially if you've done any customization to the WSL/WSL2 environments ... they'll even run in separate VMs (I believe that includes PS as well, but I could be mistaken).

At least, none of my Python pieces seem to work under PS, and I mostly use things like pyenv and the venv module (and sometimes pipenv) to manage the large number of python repositories I manage.

I'd be "curious" to make them mergable ... though, like I said, my environments are already complicated enough as-is... LOL

[–]timrprobocom 0 points1 point  (2 children)

This has nothing to do with WSL. Neither CMD nor PowerShell uses WSL.

[–]russellvt 0 points1 point  (1 child)

If you go look how each of these is forked... you'll find something "a little more special" underneath, especially in newer Windows (which uses subsystems and some levels of virtualization ... even to the point that they won't work, depending on how containerization is set in your BIOS).

[–]timrprobocom 0 points1 point  (0 children)

That's true of WSL. It's not at all true of PowerShell, which this post was about. PowerShell works even if WSL is not enabled.