Hi Tom,
Can you specify how you passed python to the script?In any case, when reporting
a problem is always helpful to also report any kind of error message.
On https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source/Windows we
removed the description of how to setup emerge manually because it was most
often to complicated for a new user. Python is not required to be in the path
but you need to set it in the etc/kdesettings.ini.
I will read a short description of how to manually setup emerge.
If you have any questions just ask right away or join us on
irc://irc.freenode.net/kde-windows
Kind regards,
Hannah
> To: kde-windows@kde.org
> From: thomas.sisso...@gmail.com
> Subject: New kdeenv.ps1 file
> Date: Sat, 24 Sep 2016 20:03:38 -0400
>
> My system chokes on the new file. Also, there is no way to clean up
> variables that are incorrect from a failed attempt. The script cannot
> find Python even though I have 2 versions and have Python2.7 in my path.
> I try to pass it to the script and it just starts over saying it cannot
> find python.
>
> When the script doesn't like information I give it, it closes my
> PowerShell window even though I opened it before running the script.
> When it installs the version of Python it wants, it throws errors.
> Nowhere at kde.org is the preferred version of Python specified. For
> people to be able to build on Windows, you must specify all required
> tools including versions expected by the script. You would give
> dependencies for Linux, so this is the equivalent.
>
> This is just a heads up. I am not looking for help here.
>
> Also, the person updating Windows specific tools and scripts needs to be
> able to test and run them on a Windows machine, not a VM or Wine.
>
> Thanks,
> Tom Sisson
