Hi @petobens ,

You should have an example script in your

c:\winpython\scripts\env.bat

You can also launch

c:\winpython\scripts\cmd.bat

to get a dos windows with the previous script executed.

Hi @stonebig , thanks for the quick reply. Let me first apologize for the fact that my following question is quite elementary but I can't get this to work. I want to permanently alter the %PATH%, adding the directories in env.bat. If I run env.bat I believe this will modifiy the %PATH temporarily because if after running the batch file I close the cmd.exe and re open it an run python I get the error saying it is not recognized as an internal command.
So my question is: how do I permanently add to the %PATH% the same directories that env.bat adds temporarily?
Once again sorry for the inconvenience and thanks for the help.

well,
looking at http://stackoverflow.com/questions/8358265/how-to-update-path-variable-permanently-from-cmd-windows

There is them manual change of the path method, described here:
http://geekswithblogs.net/renso/archive/2009/10/21/how-to-set-the-windows-path-in-windows-7.aspx#540517

Or there is this method, that I didn't try

rem (call winpython\script\cmd.bat, to launch the env.bat and have the dos command prompt)
rem then try this (from https://technet.microsoft.com/en-us/library/cc755104.aspx)
setx MYPATH %PATH%

Does anyone of this fit your problem ?

@stonebig thanks for the references. I was able to set the user variable using the method described by the SO question (unfortunately I still have to set system variables manually because the /M flag suggested in SO doesn't seem to work at least in my case). Since you include the possibility to register the distribution and state that:

these actions are exactly the same as those performed when installing Python with the official installer for Windows

and since the official installer gives the user the option (during installation) to automatically add the python executable to the %PATH% variable I was wondering if you could also add this option for winpython.

One last question: I installed jedi with by doing pip install jedi, however jedi is not listed in the uninstall package list of the WinPython Control Panel. Is this correct?

One again thanks for the help!

Yes, packages are listed only if you use WinPython Control Panel.exe

You can do pip uninstall jedi then re-install it via WinPython Control Panel.exe if you want to see it in WinPython Control Panel.

Thanks for clarifying that point. Regarding my other question, will you consider adding an option to automatically add python to the path from within the winpython control panel (something the official python offers during installation ) ? Or do you want me to close this issue?

I didn't have time to think about that part of winpython yet, so I have no opinion. You can keep it open.

Ok. Thanks again for the help.

+1 for @petobens proposal for adding WinPython in PATH, since without it, python-packages requiring DLLs fail.

Related to #28

Hi, I would like to see something like this as well. It is quite tedious to manually insert / update python in the PATH each time that I move from one version of winpython to the next. Please consider it.

Being curious - is it that we are planning to do this in the future via changing the windows registry (http://stackoverflow.com/questions/2121795/programmatically-modifiy-environment-variables), or are we holding this off because chaning the registry will cause other bugs?

PS: remember that we need to change HOME to settings dir as well... It's probably just me but I missed it earlier today.

PS: remember that we need to change HOME to settings dir as well... It's probably just me but I missed it earlier today.

@yw5aj if I change/create a HOME env variable and set it to the settings dir then when I fire up from the cmd prompt a program that requires python, such asvim, such program doesn't know where to find its config file,vimrc, which lives in the %USERPROFILE% directory (in my case, C:\Users\Pedro).

The only way I found to get gvim (not vim) to work is to create a PYTHONHOME env variable set to C:\winpython\python-3.4.3.amd64. Your solution allows vim to work but I have no idea how to have it working and also loading the correct config file from my %USERPROFILE% directory.

I don't know what the standard python installation does but when I chose to add python to the path then I could use both vim and gvim without problems (i.e loading the correcting config file).

Maybe this link is relevant.

EDIT: I don't use vim in the cmd prompt and I therefore don't mind it doesn't work there. What I do want to point out that in order to use gvim I had to set explicitly the PYTHONHOME variable (whereas with the official python installer there is no need to do this).

@petobens Thanks! That's a good point. It almost look like that we want this:

When installing/configuring WinPython, we can select a irreversible option about whether to move the settings folder to the system %USERPROFILE% directory.

Not sure whether we'd like to do that, but that would solve the gvim issue (just an example) I guess?

Shawn

@yw5aj sorry for the late reply.

I don't know if the solution is to move the settings folder to the home directory (if I do that I believe that I can't open gvim or vim from the standard cmd prompt).

What I (and others) want is just to have the option to add Winpython to the path env variable during installation (the way the regular python installer does). Hope @stonebig can implement this wanted feature.

I still don't have a strong opinion on this and feel technically uncomfortable.

Okay. No Problem! Thanks for the quick reply.

Dear @stonebig I receive at least once a month an "angry" request from people that i have recommended them using WinPython due to this issue.

The sequence of events is like this:

1. They want to run a python project of mine with native libs and DLLs (i.e. numpy & win32api).
2. I tell them "install WinPython and don't forget to manually update your PATH" .
3. They fail to do it :-) and i help them over the phone into achieving the above task.
4. Months later, when they upgrade their WinPython (i.e. to get more recent pandas).
5. THEY FORGET TO FIX THE PATH.
6. After days of trying to fix it, they come back shouting at me that my code is broken!

So, would it be possible to fix this once and for all?
It should have little to do with HOME and Settings.

My suggestion of how this capability should work is this:

A) The WinPython-installer on start-up checks existing PATH for locating a (win)python.exe.

B.a) If python.exe exists in PATH, it provides the user with this choice:

Update python-X.Y.V --> Python-XX.YY.ZZ into your PATH environment variable ?

and possibly add another one, whether to try and set this for all users).

B.b) Otherwise, if no python.exe exists in PATH, the choice should read:

Add python-X.Y.V into your PATH environment variable?

C. Before exiting installer, if user had checked the above options, it will:

• i) gather all path-elements containing the identified (win)python.exe.
• ii) Construct a setx PATH=... batch-script to prepend PATH with the new python (or use win32api registry-code) and
• iii) (depending on the 2nd choice) try running this with admin-rights or failback updating user-path env-var only.

I still have one issue unresolved, what to do if a python.exe from a different distribution is found (ie from cygwin or anaconda).

Hi @ankostis,

What you suggest doesn't look a good idea to me.

Maybe Winpython is not currently the right solution for your users / your use case.

I didn't try it myself but maybe, maybe, pyzo would better fit your particular need ?

I would think that the problem is nowodays solved per tweaking ./settings/winpython.ini
re-open if not.