-
-
Notifications
You must be signed in to change notification settings - Fork 16
Expand file tree
/
Copy pathtox.ini
More file actions
318 lines (286 loc) · 8.98 KB
/
tox.ini
File metadata and controls
318 lines (286 loc) · 8.98 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
# Tox (http://tox.testrun.org/) is a tool for running tests
# in multiple virtualenvs. This configuration file will run the
# test suite on all supported python versions. To use it, "pip install tox"
# and then run "tox" from this directory.
[tox]
# To use a PEP 517 build-backend you are required to configure tox to use an isolated_build:
# https://tox.readthedocs.io/en/latest/example/package.html
isolated_build = True
# These environments are run in order if you just use `tox`:
envlist =
# always keep coverage-clean first
coverage-clean
# code formatters
format
# format-docs
# Code quality assessment
pyroma
lint
lint-markdown
mypy
# Documentation quality assurance
docs-lint
docstr-coverage
docs-test
# the actual tests
py
doctests
# always keep coverage-report last
coverage-report
[testenv:update]
commands =
biomappings update
biomappings ndex
usedevelop = true
extras =
exports
passenv =
NDEX_USERNAME
NDEX_PASSWORD
[testenv]
description = Run unit and integration tests.
# Runs on the "tests" directory by default, or passes the positional
# arguments from `tox -e py <posargs_1> ... <posargs_n>
commands =
coverage run -p -m pytest --durations=20 {posargs:tests}
coverage combine
coverage xml
# See the [dependency-groups] entry in pyproject.toml for "tests"
dependency_groups =
tests
[testenv:coverage-clean]
description = Remove testing coverage artifacts.
deps = coverage[toml]
skip_install = true
commands = coverage erase
[testenv:doctests]
description = Test that documentation examples run properly.
commands =
# note that the package name is required for discovery
xdoctest -m src/biomappings
dependency_groups =
doctests
[testenv:treon]
description = Test that notebooks can run to completion
commands =
treon notebooks/
deps =
treon
semra
bioversions
extras =
exports
[testenv:format]
description = Format the code in a deterministic way using ruff. Note that ruff check should come before ruff format when using --fix (ref: https://github.com/astral-sh/ruff-pre-commit/blob/main/README.md)
dependency_groups =
lint
skip_install = true
commands =
ruff check --fix
ruff format
[testenv:format-docs]
description = Run documentation linters.
# note that this doesn't work with sphinx-click
# or any other extension that adds extra directives
# See the [dependency-groups] entry in pyproject.toml for "rstfmt"
dependency_groups =
format-docs
skip_install = true
commands =
docstrfmt src/ tests/ scripts/ docs/ --no-docstring-trailing-line
[testenv:format-markdown]
description = Run markdown formatter.
skip_install = true
allowlist_externals =
npx
commands =
npx --yes prettier --write --prose-wrap always "**/*.md"
[testenv:lint]
description = Check code quality using ruff and other tools.
skip_install = true
dependency_groups =
lint
commands =
ruff check
ruff format --check
[testenv:lint-markdown]
description = Check markdown is properly formatted.
# inspired by https://github.com/astral-sh/uv/blob/98523e2014e9a5c69706623344026d76296e178f/.github/workflows/ci.yml#L67C1-L70C61
skip_install = true
allowlist_externals =
npx
commands =
npx --yes prettier --check --prose-wrap always "**/*.md"
[testenv:pyroma]
dependency_groups =
pyroma
skip_install = true
commands = pyroma --min=10 .
description = Run the pyroma tool to check the package friendliness of the project.
[testenv:mypy]
description = Run the mypy tool to check static typing on the project. Installs the package to make sure all type stubs get recognized.
dependency_groups =
typing
commands = mypy --ignore-missing-imports --strict src/ tests/ scripts/
extras =
web
predict-lexical
predict-embeddings
exports
[testenv:docs-lint]
skip_install = true
dependency_groups =
docs-lint
commands =
doc8 docs/source/
description = Run the doc8 tool to check the style of the RST files in the project docs.
[testenv:docstr-coverage]
description = Run the docstr-coverage tool to check documentation coverage.
skip_install = true
deps =
docstr-coverage
commands =
docstr-coverage src/ tests/ --skip-private --skip-magic
[testenv:docs]
description = Build the documentation locally, allowing warnings.
dependency_groups =
# See the [dependency-groups] entry in pyproject.toml for "docs"
docs
# You might need to add additional extras if your documentation covers it
commands =
python -m sphinx -b html -d docs/build/doctrees docs/source docs/build/html
[testenv:docs-test]
description = Test building the documentation in an isolated environment. Warnings are considered as errors via -W.
changedir = docs
dependency_groups =
{[testenv:docs]dependency_groups}
commands =
mkdir -p {envtmpdir}
cp -r source {envtmpdir}/source
python -m sphinx -W -b html -d {envtmpdir}/build/doctrees {envtmpdir}/source {envtmpdir}/build/html
# python -m sphinx -W -b coverage -d {envtmpdir}/build/doctrees {envtmpdir}/source {envtmpdir}/build/coverage
# cat {envtmpdir}/build/coverage/c.txt
# cat {envtmpdir}/build/coverage/python.txt
allowlist_externals =
cp
cat
mkdir
[testenv:coverage-report]
deps = coverage[toml]
skip_install = true
commands =
coverage report
####################
# Deployment tools #
####################
[testenv:bumpversion]
description = Bump the version number
commands = bump-my-version bump {posargs}
skip_install = true
passenv = HOME
dependency_groups =
bump
[testenv:bumpversion-release]
description = Remove the -dev tag from the version
commands = bump-my-version bump release --tag
skip_install = true
passenv = HOME
dependency_groups =
bump
[testenv:build]
skip_install = true
dependency_groups =
build
commands =
uv build --sdist --wheel --no-build-isolation --clear
############
# Releases #
############
# In order to make a release to PyPI, you'll need to take the following steps:
#
# 1. Navigate to https://pypi.org/account/register/ to register for Test PyPI
# 2. Navigate to https://pypi.org/manage/account/ and request to re-send a verification email.
# This is not sent by default, and is required to set up 2-Factor Authentication.
# 3. Get account recovery codes
# 4. Set up 2-Factor Authentication
# 5. Get an API token from https://pypi.org/manage/account/token/
# 6. Install keyring with `uv tool install keyring`
# 7. Add your token to keyring with `keyring set https://upload.pypi.org/legacy/ __token__`
[testenv:release]
description = Release the code to PyPI so users can pip install it, using credentials from keyring
skip_install = true
dependency_groups =
release
commands =
{[testenv:build]commands}
uv publish --username __token__ --keyring-provider subprocess --publish-url https://upload.pypi.org/legacy/
[testenv:release-via-env]
description = Release the code to PyPI so users can pip install it, using credentials from the environment.
skip_install = true
dependency_groups =
{[testenv:build]dependency_groups}
release
commands =
{[testenv:build]commands}
uv publish --publish-url https://upload.pypi.org/legacy/
passenv =
UV_PUBLISH_USERNAME
UV_PUBLISH_PASSWORD
[testenv:finish]
description =
Run a workflow that removes -dev from the version, creates a tagged release on GitHub,
creates a release on PyPI, and bumps the version again.
skip_install = true
passenv =
HOME
dependency_groups =
bump
release
commands =
{[testenv:bumpversion-release]commands}
{[testenv:release]commands}
git push --tags
bump-my-version bump patch
git push
allowlist_externals =
git
#################
# Test Releases #
#################
# In order to test making a release to Test PyPI, you'll need to take the following steps:
#
# 1. Navigate to https://test.pypi.org/account/register/ to register for Test PyPI
# 2. Navigate to https://test.pypi.org/manage/account/ and request to re-send a verification email.
# This is not sent by default, and is required to set up 2-Factor Authentication.
# 3. Get account recovery codes
# 4. Set up 2-Factor Authentication
# 5. Get an API token from https://test.pypi.org/manage/account/token/
# 6. Install keyring with `uv tool install keyring`
# 7. Add your token to keyring with `keyring set https://test.pypi.org/legacy/ __token__`
[testenv:testrelease]
description = Release the code to the test PyPI site
skip_install = true
dependency_groups =
release
commands =
{[testenv:build]commands}
uv publish --username __token__ --keyring-provider subprocess --publish-url https://test.pypi.org/legacy/
[testenv:testfinish]
description =
Run a workflow that removes -dev from the version, creates a tagged release on GitHub,
creates a release on Test PyPI, and bumps the version again.
skip_install = true
passenv =
HOME
dependency_groups =
{[testenv:testrelease]dependency_groups}
bump
release
commands =
{[testenv:bumpversion-release]commands}
{[testenv:testrelease]commands}
git push --tags
bump-my-version bump patch
git push
allowlist_externals =
git