Pype setup refactor

[antirotor]

Pype setup rework

For 3.0 release we change pype-setup so it acts as installer only, all other functionality should be moved to pype (see #205).

It should wrap all dependencies using something cx_freeze.

Local installation

How to tell the installer what to install? Compare "local version" with "studio vesion"
if they don't match update all repositories by copying from studio to local.

Installing Git and Python along with all other pype-setup files able to pack all dependent data files (json, ffmpeg, plugins_folder). We could append studio local sub-releases to pype-setup/version.py
everytime local changes should be pushed to artist, we add local version token to pype-setup/config.ini

Example:

3.0.0
3.0.0-client1 (version + local_subversion)
3.0.1-client1 (version + local_subversion)
3.0.2
3.1.1
3.1.1-client1 (version + local_subversion)
3.1.1-client2 (version + local_subversion)

Move deploy.json to setup.py and config.ini
Artist shouldn't need to update pype-setup itself often. Only with any major changes, in which case he get's new zip.

[issue-label-bot]

Issue-Label Bot is automatically applying the label feature_request to this issue, with a confidence of 0.88. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[create-issue-branch]

Branch feature/211-Pype_setup_refactor created!

[antirotor]

Right now it is in shell scripts (pype.ps1 and pype) for the python independent part and in pypeapp/PypeLauncher for python specifics. If we bundle our own python, we don't need most of the code in shell scripts as that can be written in python. But there is other side - if we put commands to pype repo, they (as rest of the code) depends on virtual environment set by pype-setup. Little case of egg and chicken.

I still vote to move all those command to pype and add sanity checks to prevent its run without correct environment.