This is a library of control scripts and experiments for use with the kRPC mod for Kerbal Space Program.
Instructions for contributing to this project are shown here.
This section will take you through the procedure to take your development environment from zero to hero.
-
Install python from the official website.
The project runs on python
3.10
. -
Install git.
-
Install poetry.
The project uses poetry as its package manager. Poetry allows you to run a single command to install all the dependencies for the project. Install it through the Windows Powershell via:
(Invoke-WebRequest -Uri https://install.python-poetry.org -UseBasicParsing).Content | python -
On Linux/MacOS with:
curl -sSL https://install.python-poetry.org | python3 -
Once poetry is installed, if it does not say it has automatically add itself to your PATH, add its executible directory to your PATH:
Windows:
%APPDATA%\Python\Scripts
Linux/MacOS:
$HOME/.local/bin
For instructions on adding directories to your machine's PATH, check out this (Windows) or this (Linux/MacOS). You'll need to close all instances of your terminals for the PATH changes to take effect.
Confirm poetry was installed correctly by typing the following in your terminal:
poetry --version
Configure poetry to create its virtual environments within the project's directory. This makes it easier to clean your machine when you delete the project. The
.venv
folders can get pretty big.poetry config virtualenvs.in-project true
-
Clone the repository.
It is recommended that you use Github Desktop to clone the project repository.
-
Install project dependencies
From a terminal within the cloned repository, run poetry's install command:
poetry install
Then install the project's pre-commit hooks using:
pre-commit install --install-hooks
Pre-commit's cache will be stored at
~/.cache/pre-commit
(this folder can grow very large).The kRPC package requires setuptools 57.5.0 to install correctly. Setuptools cannot currently be version-locked in poetry, execpt in the beta 1.2 release (see issue). For now, you must run:
poetry run pip install --upgrade setuptools==57.5.0
To install the compatible version of setuptools for kRPC. Poetry does not yet support version-pinning of
setuptools
, so this cannot be done in thepyproject.toml
file. -
Configure IDE interpreter
It is recommended you use VSCode as your integrated development environment (IDE). Configure your IDE to use the virtual environment poetry has created at
C:\Users\<USERNAME>\AppData\Local\pypoetry\Cache\virtualenvs
(you can also find it with the commandpoetry show -v
).In the case of VSCode, enter the command pallet by going to
View>Command Palette
and search forPython:Select Interpreter
. Select the appropriate poetry virtual environment for the repository. Restart VSCode if you do not see it listed. Once the intepreter is changed, restart your terminal by closing the old one and launching it again.For Windows Powershell users, you might need to change the PS execution policy to allow the script to run. Run a Powershell terminal as administrator and run the following:
Set-ExecutionPolicy -ExecutionPolicy Bypass
You're now ready to start contributing!
To add a new package to the poetry virtual environment, install it via:
poetry add <package>
This is poetry's version of pip install <package>
.
This repo uses pytest for unit testing. To run all unit tests, call:
pytest -v
This is also a good check to make sure your environment is properly set up. If the tests fail to run, check to confirm you followed the setup instructions correctly.
You can find an interactive report of test results in ./logs/pytest/pytest-report.html
.
Individual tests can also be specified as follows:
pytest tests/test_<filename>.py::<function name>
Groups of tests can be run using markers. Assign a marker decorator to the group of functions you want to test, like this:
@pytest.mark.foo
def my_test_function():
# some test
To use the custom marker foo
, it must be added to the list of custom pytest markers in pyproject.toml>[tool.pytest.ini_options]>markers
. The tests marked with foo
can then be run by calling:
pytest -v -m foo
Or to avoid all tests with a particular marker, call:
pytest -v -m "not foo"
Check out the pytest docs for more neat tricks.
This project is configured to use pre-commit hooks. A hook is a script that performs some operation on the repository before every commit. Hooks are used to autoformat and lint code. Pre-commit will not let you push your commit until all hooks pass. When a hook fails, they can be run manually to delint using:
pre-commit run --all-files
Hooks can be updated using:
pre-commit autoupdate
Branches are organized as follow:
-
main
: the branch containing the most recent working release. All code in this branch should run perfectly without any known errors. -
dev
: branched off ofmain
; the most updated version of the project with the newest features and bug fixes. -
features/<feature-name>
: branched off ofdev
; a feature branch. Features must be tested thoroughly before being merged into dev
Check out the issues tab to see all open tickets.
When the project changes python version, it is neccesary to create a new poetry environment with the updated python installation. To do so, proceed as follows:
-
Download and install the required python version from the official website.
-
Within the current poetry environment, call:
poetry env use /full/path/to/new/python.exe
You can get this path from your environment variables. Poetry will then generate a new empty environment assigned to run using the new python version.
-
Switch to the new empty environment and call:
poetry install
and
pre-commit install --install-hooks
To install all the dependencies within this new environment.
You're now ready to start development with the new version of python!