To me, this is a clear case of trying to fix a broken system whereas starting from scratch would be much better.
There are a lot of great things about Python, but dependency management is right there under the GIL on the list of things that are very painful.
Additionally, for anyone coming from almost all compiled native languages, a native environment like Rust with better dependency management than Python (which, as you say, and in retrospect, is pretty broken) is a bit of a mind screw.
Cargo should even be better than npm.
On the other hand I always asked myself if they couldn't simply use Nix?
Regardless, while it's cool and useful, it's not really actual Windows support.
Didn't take you for a Windows guy, hehe
It's due to video games... but I'm actually enjoying Windows 10.
Off topic, but it shouldn't be better than "even Python", because Python has a really, really broken dependency system. Far more so than Java, which has Maven/Gradle which are both infinitely better than the pip/virtualenv disaster.
People complain about things like shading in Maven being complicated. What they might not realize is that pip doesn't even try to address conflicting dependencies, it will just silently give you the wrong version! You ask for A==0.2 and it will give you A==0.1 if another dependency asked for A==0.1 first. And it won't even warn you even though it's straight up broken behavior. Virtualenv makes packaging annoying since it's almost vendoring but not quite. To totally understand the packaging system forces you into the world of eggs, wheels, disutils, conflicting versions, condas, etc.
Sorry for tangent, just thought it was funny you would hold Python up as a standard of dependency excellence when it's probably the worst overall ecosystem of major languages.