Windows support

[mcandre]

Could we port pyenv to Windows?

I imagine .bat scripts could mimic the behavior of the .sh scripts.

---

A note from the pyenv maintainers:

pyenv does not currently support Windows outside of the Windows Subsystem for Linux (WSL). We have no current plans to support Windows in the future.

@kirankotari has helpfully provided a port of pyenv for windows called pyenv-win, which hopefully will meet the needs of windows users.

[yyuu]

I'm no longer using Windows. I don't like to waste my time with such thing.

[mcandre]

Windows isn't my favorite development platform either, but it's nice to be compatible for their benefit. There are development tools that aren't Unix compatible, and it's annoying to have to go back and forth between them. You end up with a build system that needs multiple operating systems just to build the application.

[CamiloMM]

As someone who is just in need of running Python but am clueless as how things are done in it, this StackOverflow answer makes it seem like it's now simple to have support for multiple pythons in Windows. I don't know if it's true but maybe this helps someone in my situation.

[mcandre]

How granular does the Python Launcher support version numbers? Would #!python2.6.0 work, or just #!python2?

Can the Python Launcher parse the version in #!/usr/bin/env python[version] shebangs popular in Unix? It would stink to have to constantly change the shebangs back and forth between Unix and Windows.

[CamiloMM]

@mcandre fuck if I know. Python seems as easy to deploy on Windows as ksh scripts. Actually, one option is to port Python code to Objective-C to make it easier to deploy on Windows!

[ut-adamc]

I'm no longer using Windows. I don't like to waste my time with such thing.

Seems short-sighted to me, if you care about pyenv spreading. A lot of us work in places where we have to spend some of our time in Windows, and I'm more likely to prefer a tool I can use across environments than one that only runs in some of them.

I'm not a fan of Windows either, but the availability of things like virtualenvwrapper across environments has made it much easier for me to justify using them.

[ftomassetti]

I also do not use Windows but users of my open-source projects do, so it would be great to have support for pyenv on Windows. I would use it together to AppVeyor to test my software on Windows without having Windows

[chriskrycho]

As others have commented: Windows development may not be awesome, but a lot of us do use Windows for work because we have to (and some people just love it). I understand that you don't want to spend the time on it yourself, of course. Assuming someone could write Windows-friendly scripting, though, would you potentially accept PRs for it?

[autolife]

you can try pywin[https://github.com/davidmarble/pywin]

[blueyed]

Also anyenv might be an option: https://github.com/mislav/anyenv, assuming that Go on Windows works well.
Anyenv is supposed to be the successor of rbenv, pyenv etc.

[edbordin]

I'm interested in getting this working on Windows in my spare time. A couple of things I wouldn't mind feedback on though:

1. pyenv install works by compiling python from source. Building python on Windows isn't actually too hard (I just built Python 3.6 with no issues). But getting a comprehensive set of build tools installed looks like a pain. To build all versions of python 2.x.x and 3.x.x you need VC++ 9.0, 10.0 and 14.0 and they all have their own fairly convoluted installation steps. So, perhaps an easier method would just be to download the official Windows builds. Is anyone heavily relying on adding custom build flags/patches etc. to their interpreter?

2. Given how many bash scripts have been written, the easiest approach would probably be to patch pyenv so that it works in MSYS bash on Windows. I think this would still be useful, given that once an environment has been created it is relatively self-contained. Anyone see any obvious problems with this approach?