Check for compatible python version and create virtual python enviroment to avoid conflicts in run.sh

[itsmartinhi]

#46

[itsmartinhi]

@snipem what's your opinion on that?

[snipem]

Anyone is free to create their own pyenv. The run scripts are mainly for beginners who have not ever used Python. So this is just a basic helper, advanced users may run the script directly. Creating a pyenv for non advanced users seems a little bit intrusive.

[itsmartinhi]

Fair point.
But isn't it less intrusive to encapsulate into a separate environment?

That way a simple uninstall script could just delete the venv.

It's your repository, so it's your call. I just tried to take the perspective of a non technical user and saw some things that might be confusing (e.g. conflicts with already installed packages).

I'd be glad to contribute more to make the (un)install process even simpler.

[snipem]

Fair point too. I think the past way would be to use py2exe or similar to provide a Windows executable and delete the run scripts. From my observation most inexperienced users use Windows, so this would solve the issue for most of the users.

Edit: providing a run.sh is fair, but providing compatible run scripts for Mac and Windows is even heavier on testing. So far I would like to reduce the platform specific code because this branches out testing on every new Python release etc.

[snipem]

@itsmartinhi What about putting the info about pyenv in a beginner friendly way into the README.md? run.sh will still work at the bare minimum of freshly installed Python instances.

[itsmartinhi]

sry, I've been under the weather the last two of weeks.
Haven't tried py2exe stuff myself so far, so I don't know if that would be a good idea (without a certificate the app would also get flagged by windows right? afaik these certificates are a bit of a pain in the ass to get, or at least pretty expensive).

I think it boils down to the question if you even want to cater to less technical users. If it's not really a priority, I think just having a comprehensive guide in the readme is sufficient.

Whats your experience so far in how users use the software (and how technical they usually are)?