vferat / mne_tasks

Intent of this template

The intent of this repository is to help you get started with creating Pydra tasks. All tasks will be inserted into the pydra.tasks.<yourtaskpackagename> namespace.

To use this template

1. Click on new repo.
2. Select this template from the repository template drop down list.
3. Give your repo a name.
4. Once the repo is created and cloned, search for CHANGEME (grep -rn CHANGEME . ) and replace with appropriate name.
5. Rename the namespace package root directory to replace CHANGEME with the name of the package:
   • src/pydra/tasks/CHANGEME
6. Under the newly renamed package (i.e. formerly CHANGEME) there is a directory named "v1", src/pydra/tasks/<package-name>/v1, change this to valid Python package name starting with 'v' to indicate the version of the tool the Pydra interfaces will be designed for, e.g. FSL v6.0.2 could be src/pydra/tasks/fsl/v6 or src/pydra/tasks/fsl/v6_0 depending on how stable the CLI of the tool is between minor versions.
7. Edit src/pydra/tasks/<package-name>/latest.py to update references to v1 to the tool target version
8. Add tasks to the src/pydra/tasks/<package-name>/v<package-version> folder.
9. You may want to initialize a Sphinx docs directory.
10. Review the workflow in .github/workflows/pythonpackage.yml. Testing editable installations is probably not useful unless you are reconfiguring namespace packages.
11. Update this README after creating the new repository.

Features of this template

Tag-based versioning

The setuptools_scm tool allows for versioning based on the most recent git tag. The release process can thus be:

git tag -a 1.0.0
python -m build
twine upload dist/*

Note that uploading to PyPI is done via Continuous integration when a tag is pushed to the repository, so only the first step needs to be donne manually.

Note also that we assume tags will be version numbers and not be prefixed with v or some other string. See setuptools_scm documentation for alternative configurations.

Namespace packages

Namespace packages allow multiple packages to be installed in such a way that they can be imported from a common namespace. In this case, the base namespace is pydra.tasks, and each task package installs a new module, such as pydra.tasks.afni.

To do correctly, task packages must not interfere with files higher in the hierarchy. This includes adding __init__.py files in either pydra or pydra/tasks.

Tests

This package comes with a default set of test modules, and we encourage users to use pytest. Tests can be discovered and run using:

pytest --doctest-modules pydra/tasks/*

Continuous integration

This template uses GitHub Actions to run tests. To simulate several plausible development or installation environments, we test over all Python versions supported by Pydra, and install Pydra and the current package in both standard and editable modes.

The combination of standard/editable is in particular designed to ensure that namespace packaging does not break. We strongly recommend keeping these tests in place for this reason, as one non-compliant package can potentially affect Pydra or other task packages.

In addition to verifying installations do not break or conflict, pytest is run on the package, including all tests found in test/ directories and doctests.

Finally, packages are built and uploaded as artifacts for inspection. When a tag is pushed, the packages are uploaded to PyPI if a valid API token is placed in the repository secrets.

Contributing to this template

This template repository is periodically updated as we establish and best practices for task packages. We welcome contributions from the community to help set a solid baseline for all task packages.

Sample post-setup README contents

For developers

Install repo in developer mode from the source directory. It is also useful to install pre-commit to take care of styling via black:

pip install -e .[dev]
pre-commit install