@@ -11,15 +11,15 @@ All tasks will be inserted into the `pydra.tasks.<yourtaskpackagename>` namespac
11
11
1 . Once the repo is created and cloned, search for CHANGEME (` grep -rn CHANGEME . ` ) and
12
12
replace with appropriate name.
13
13
1 . Rename the namespace package root directory to replace ` CHANGEME ` with the name of the package:
14
- * ` src/ pydra/tasks/CHANGEME`
14
+ * ` pydra/tasks/CHANGEME `
15
15
1 . Under the newly renamed package (i.e. formerly CHANGEME) there is a directory named "v1",
16
- ` src/ pydra/tasks/<package-name>/v1` , change this to valid Python package name starting with
16
+ ` pydra/tasks/<package-name>/v1 ` , change this to valid Python package name starting with
17
17
'v' to indicate the version of the tool the Pydra interfaces will be designed for,
18
- e.g. FSL v6.0.2 could be ` src/ pydra/tasks/fsl/v6` or ` src/ pydra/tasks/fsl/v6_0` depending on
18
+ e.g. FSL v6.0.2 could be ` pydra/tasks/fsl/v6 ` or ` pydra/tasks/fsl/v6_0 ` depending on
19
19
how stable the CLI of the tool is between minor versions.
20
- 1 . Edit ` src/ pydra/tasks/<package-name>/latest.py` to update references to ` v1 ` to the
20
+ 1 . Edit ` pydra/tasks/<package-name>/latest.py ` to update references to ` v1 ` to the
21
21
tool target version
22
- 1 . Add tasks to the ` src/ pydra/tasks/<package-name>/v<package-version>` folder.
22
+ 1 . Add tasks to the ` pydra/tasks/<package-name>/v<package-version> ` folder.
23
23
1 . You may want to initialize a [ Sphinx] docs directory.
24
24
1 . Review the workflow in ` .github/workflows/pythonpackage.yml ` . Testing editable installations
25
25
is probably not useful unless you are reconfiguring namespace packages.
0 commit comments