15 | | * Have python **3.8 or 3.9** installed on your machine, for use with the pythonpartiesserver. This must be a full python installation. We recommend downloading python from [https://www.python.org/downloads python.org], either run an installer or to build the sources. Especially if you build from sources, you can place the python executable anywhere you like, so you can place it where it does not interfere with your standard installation. Some package installers appear to not support pip, venv etc out of the box. GeniusWebPythonPartiesServer does not work with such partial installations. |
| 15 | * Have a FRESH python **3.8 or 3.9** installed on your machine, for use with the pythonpartiesserver. This must be a full python installation. We recommend downloading python from [https://www.python.org/downloads python.org], either run an installer or to build the sources. Especially if you build from sources, you can place the python executable anywhere you like, so you can place it where it does not interfere with your standard installation. Some package installers appear to not support pip, venv etc out of the box. GeniusWebPythonPartiesServer does not work with such partial installations. |
| 16 | * The python installation must be fresh, meaning it should not have pip-installed modules and {{{pip list}}} should only return {{{pip}}} and {{{setuptools}}}. This is important because pre-installed modules might make your party work on *your machine only* despite missing dependency information in the setup.py file. That would lead to failure when your party would be deployed somewhere else, eg for a competition. |