SKA Python Skeleton Project Status

Briefly describe your project here


The system used for development needs to have Python 3, pip and Poetry installed.

Install pip

Always use a virtual environment. Pipenv is now Python’s officially recommended method, but we are not using it for installing requirements when building on the CI Pipeline. You are encouraged to use your preferred environment isolation (i.e. pip, conda or pipenv while developing locally.

For working with Pipenv, follow these steps at the project root:

First, ensure that ~/.local/bin is in your PATH with:

> echo $PATH

In case ~/.local/bin is not part of your PATH variable, under Linux add it with:

> export PATH=~/.local/bin:$PATH

or the equivalent in your particular OS.

Then proceed to install pipenv and the required environment packages:

> pip install pipenv # if you don't have pipenv already installed on your system
> pipenv install
> pipenv shell

You will now be inside a pipenv shell with your virtual environment ready.

Use exit to exit the pipenv environment.

Install Poetry

First we need to install Poetry: curl -sSL | python3 - The script described here will be replaced in Poetry 1.2 by From Poetry 1.1.7 onwards, you can already use this script as described as below: curl -sSL | python3 - To manage application dependencies Poetry supports pyproject.toml config file. This .toml file have three sections:

  • [tool.poetry] — fields that describe our application, some of them are required,
  • [tool.poetry.dependencies] —a list of all the required packages with version numbers,
  • [] — a list of the required packages for development purposes: pytest for running unit tests, black for code linting and mypy for static type check.To install all those dependencies simply run: “poetry install”. The dependencies will be installed to the virtual environment created and managed by Poetry by creating poetry.lock file which will resolve and install all the dependencies that are listed in pyproject.toml file. In this way, Poetry handles both the dependencies of our application in one go.


  • Put tests into the tests folder
  • Use PyTest as the testing framework
  • Run tests with python test
    • Configure PyTest in and setup.cfg
  • Running the test creates the htmlcov folder
    • Inside this folder a rundown of the issues found will be accessible using the index.html file
  • All the tests should pass before merging the code

Code analysis

  • Use Pylint as the code analysis framework
  • By default it uses the PEP8 style guide
  • Use the provided script in order to run the code analysis in the module and tests
  • Code analysis should be run by calling pylint ska_python_skeleton. All pertaining options reside under the .pylintrc file.
  • Code analysis should only raise document related warnings (i.e. #FIXME comments) before merging the code

Writing documentation

  • The documentation generator for this project is derived from SKA’s SKA Developer Portal repository
  • The documentation can be edited under ./docs/src
  • If you want to include only your file, create a symbolic link inside the ./docs/src directory if the existing one does not work:
$ cd docs/src
$ ln -s ../../
  • In order to build the documentation for this specific project, execute the following under ./docs:
$ make html
  • The documentation can then be consulted by opening the file ./docs/build/html/index.html



As this project uses a src folder structure, under Preferences > Project Structure, the src folder needs to be marked as “Sources”. That will allow the interpreter to be aware of the package from folders like tests that are outside of src. When adding Run/Debug configurations, make sure “Add content roots to PYTHONPATH” and “Add source roots to PYTHONPATH” are checked.