Sorry, the tools are there, I’m impressed at your ability to over complicate this. You come bitching, and snarky - so.. enjoy your misery? Not sure what you want here.
You will notice I did not use virtualenvwrapper-win because you should not be using it. You obviously do not understand how things are working here (which I will say is normal, not everyone can be an expert at everything) and yet at the same time you seem to want to maintain some sense of superiority by disregarding the advice of people who know more than you. The fact that you could not get the above working for weeks tells me that you are not willing to simply RTFM and gain an understanding of the tools you use.
The entire point of everything I'm trying to set up here is to avoid having to type the full path to every binary on my system every time I want to use it.
For example, in my Linux setup with virtualenvwrapper, if I want to create and activate a virtual environment named "testenv", I will simply type:
> mkvirtualenv testenv
> workon testenv
Similarly, it's not really correct to have the full binary path in your shebang lines, as that destroys cross-platform support (a crucial doctrine of Python). It was after I RTFM that I discovered that the cross-platform shebangs can work if you configure Python Launcher For Windows. Yet, as I described, set-up of PLFW didn't work exactly according to TFM.
0
u/meandertothehorizon It works on my machine May 01 '18
Sorry, the tools are there, I’m impressed at your ability to over complicate this. You come bitching, and snarky - so.. enjoy your misery? Not sure what you want here.