2019-01-22 20:25:04 +00:00
|
|
|
#
|
2023-02-09 11:13:24 +00:00
|
|
|
# This file is autogenerated by pip-compile with Python 3.7
|
2023-02-06 21:10:33 +00:00
|
|
|
# by the following command:
|
2019-01-22 20:25:04 +00:00
|
|
|
#
|
2020-01-13 21:33:12 +00:00
|
|
|
# pip-compile requirements/dev.in
|
2019-01-22 20:25:04 +00:00
|
|
|
#
|
feat: strongly typed hooks
Now that the mypy bugs have been resolved, we are able to define more precisely
and cleanly the types of Actions and Filters.
Moreover, can now strongly type named actions and hooks (in consts.py). With
such a strong typing, we get early alerts of hooks called with incorrect
arguments, which is nothing short of awesome :)
This change breaks the hooks API by removing the `context=...` argument. The
reason for that is that we cannot insert arbitrary arguments between `P.args,
P.kwargs`: https://peps.python.org/pep-0612/#the-components-of-a-paramspec
> A function declared as def inner(a: A, b: B, *args: P.args, **kwargs:
> P.kwargs) -> R has type Callable[Concatenate[A, B, P], R]. Placing
> keyword-only parameters between the *args and **kwargs is forbidden.
Getting the documentation to build in nitpicky mode is quite difficult... We
need to add `nitpick_ignore` to the docs conf.py, otherwise sphinx complains
about many missing class references. This, despite upgrading almost all doc
requirements (except docutils).
2022-10-06 10:05:01 +00:00
|
|
|
altgraph==0.17.3
|
2021-02-04 08:31:48 +00:00
|
|
|
# via pyinstaller
|
|
|
|
|
appdirs==1.4.4
|
2021-09-23 04:10:05 +00:00
|
|
|
# via -r requirements/base.txt
|
2023-02-27 07:41:02 +00:00
|
|
|
astroid==2.14.2
|
2021-02-04 08:31:48 +00:00
|
|
|
# via pylint
|
2023-02-09 10:57:26 +00:00
|
|
|
attrs==22.2.0
|
2022-11-21 15:35:14 +00:00
|
|
|
# via scriv
|
2023-02-09 10:57:26 +00:00
|
|
|
black==23.1.0
|
2021-02-04 08:31:48 +00:00
|
|
|
# via -r requirements/dev.in
|
2023-02-09 10:57:26 +00:00
|
|
|
bleach==6.0.0
|
2021-02-04 08:31:48 +00:00
|
|
|
# via readme-renderer
|
2023-02-09 10:57:26 +00:00
|
|
|
build==0.10.0
|
2022-09-29 11:53:19 +00:00
|
|
|
# via pip-tools
|
2023-02-09 10:57:26 +00:00
|
|
|
cachetools==5.3.0
|
2021-02-04 08:31:48 +00:00
|
|
|
# via
|
|
|
|
|
# -r requirements/base.txt
|
|
|
|
|
# google-auth
|
2022-11-22 12:53:29 +00:00
|
|
|
certifi==2022.12.7
|
2021-02-04 08:31:48 +00:00
|
|
|
# via
|
|
|
|
|
# -r requirements/base.txt
|
|
|
|
|
# kubernetes
|
|
|
|
|
# requests
|
feat: strongly typed hooks
Now that the mypy bugs have been resolved, we are able to define more precisely
and cleanly the types of Actions and Filters.
Moreover, can now strongly type named actions and hooks (in consts.py). With
such a strong typing, we get early alerts of hooks called with incorrect
arguments, which is nothing short of awesome :)
This change breaks the hooks API by removing the `context=...` argument. The
reason for that is that we cannot insert arbitrary arguments between `P.args,
P.kwargs`: https://peps.python.org/pep-0612/#the-components-of-a-paramspec
> A function declared as def inner(a: A, b: B, *args: P.args, **kwargs:
> P.kwargs) -> R has type Callable[Concatenate[A, B, P], R]. Placing
> keyword-only parameters between the *args and **kwargs is forbidden.
Getting the documentation to build in nitpicky mode is quite difficult... We
need to add `nitpick_ignore` to the docs conf.py, otherwise sphinx complains
about many missing class references. This, despite upgrading almost all doc
requirements (except docutils).
2022-10-06 10:05:01 +00:00
|
|
|
cffi==1.15.1
|
2021-02-04 08:31:48 +00:00
|
|
|
# via cryptography
|
2023-02-09 10:57:26 +00:00
|
|
|
charset-normalizer==3.0.1
|
2021-02-04 08:31:48 +00:00
|
|
|
# via
|
|
|
|
|
# -r requirements/base.txt
|
|
|
|
|
# requests
|
feat: strongly typed hooks
Now that the mypy bugs have been resolved, we are able to define more precisely
and cleanly the types of Actions and Filters.
Moreover, can now strongly type named actions and hooks (in consts.py). With
such a strong typing, we get early alerts of hooks called with incorrect
arguments, which is nothing short of awesome :)
This change breaks the hooks API by removing the `context=...` argument. The
reason for that is that we cannot insert arbitrary arguments between `P.args,
P.kwargs`: https://peps.python.org/pep-0612/#the-components-of-a-paramspec
> A function declared as def inner(a: A, b: B, *args: P.args, **kwargs:
> P.kwargs) -> R has type Callable[Concatenate[A, B, P], R]. Placing
> keyword-only parameters between the *args and **kwargs is forbidden.
Getting the documentation to build in nitpicky mode is quite difficult... We
need to add `nitpick_ignore` to the docs conf.py, otherwise sphinx complains
about many missing class references. This, despite upgrading almost all doc
requirements (except docutils).
2022-10-06 10:05:01 +00:00
|
|
|
click==8.1.3
|
2021-02-04 08:31:48 +00:00
|
|
|
# via
|
|
|
|
|
# -r requirements/base.txt
|
|
|
|
|
# black
|
2022-11-21 15:35:14 +00:00
|
|
|
# click-log
|
2021-02-04 08:31:48 +00:00
|
|
|
# pip-tools
|
2022-11-21 15:35:14 +00:00
|
|
|
# scriv
|
|
|
|
|
click-log==0.4.0
|
|
|
|
|
# via scriv
|
2023-02-27 07:41:02 +00:00
|
|
|
coverage==7.2.1
|
2021-11-23 08:25:09 +00:00
|
|
|
# via -r requirements/dev.in
|
2023-02-09 10:57:26 +00:00
|
|
|
cryptography==39.0.1
|
2021-02-04 08:31:48 +00:00
|
|
|
# via secretstorage
|
feat: strongly typed hooks
Now that the mypy bugs have been resolved, we are able to define more precisely
and cleanly the types of Actions and Filters.
Moreover, can now strongly type named actions and hooks (in consts.py). With
such a strong typing, we get early alerts of hooks called with incorrect
arguments, which is nothing short of awesome :)
This change breaks the hooks API by removing the `context=...` argument. The
reason for that is that we cannot insert arbitrary arguments between `P.args,
P.kwargs`: https://peps.python.org/pep-0612/#the-components-of-a-paramspec
> A function declared as def inner(a: A, b: B, *args: P.args, **kwargs:
> P.kwargs) -> R has type Callable[Concatenate[A, B, P], R]. Placing
> keyword-only parameters between the *args and **kwargs is forbidden.
Getting the documentation to build in nitpicky mode is quite difficult... We
need to add `nitpick_ignore` to the docs conf.py, otherwise sphinx complains
about many missing class references. This, despite upgrading almost all doc
requirements (except docutils).
2022-10-06 10:05:01 +00:00
|
|
|
dill==0.3.6
|
|
|
|
|
# via pylint
|
2021-05-12 08:01:50 +00:00
|
|
|
docutils==0.17.1
|
feat: strongly typed hooks
Now that the mypy bugs have been resolved, we are able to define more precisely
and cleanly the types of Actions and Filters.
Moreover, can now strongly type named actions and hooks (in consts.py). With
such a strong typing, we get early alerts of hooks called with incorrect
arguments, which is nothing short of awesome :)
This change breaks the hooks API by removing the `context=...` argument. The
reason for that is that we cannot insert arbitrary arguments between `P.args,
P.kwargs`: https://peps.python.org/pep-0612/#the-components-of-a-paramspec
> A function declared as def inner(a: A, b: B, *args: P.args, **kwargs:
> P.kwargs) -> R has type Callable[Concatenate[A, B, P], R]. Placing
> keyword-only parameters between the *args and **kwargs is forbidden.
Getting the documentation to build in nitpicky mode is quite difficult... We
need to add `nitpick_ignore` to the docs conf.py, otherwise sphinx complains
about many missing class references. This, despite upgrading almost all doc
requirements (except docutils).
2022-10-06 10:05:01 +00:00
|
|
|
# via
|
|
|
|
|
# -r requirements/dev.in
|
|
|
|
|
# readme-renderer
|
2023-02-27 07:41:02 +00:00
|
|
|
google-auth==2.16.1
|
2021-02-04 08:31:48 +00:00
|
|
|
# via
|
|
|
|
|
# -r requirements/base.txt
|
|
|
|
|
# kubernetes
|
feat: strongly typed hooks
Now that the mypy bugs have been resolved, we are able to define more precisely
and cleanly the types of Actions and Filters.
Moreover, can now strongly type named actions and hooks (in consts.py). With
such a strong typing, we get early alerts of hooks called with incorrect
arguments, which is nothing short of awesome :)
This change breaks the hooks API by removing the `context=...` argument. The
reason for that is that we cannot insert arbitrary arguments between `P.args,
P.kwargs`: https://peps.python.org/pep-0612/#the-components-of-a-paramspec
> A function declared as def inner(a: A, b: B, *args: P.args, **kwargs:
> P.kwargs) -> R has type Callable[Concatenate[A, B, P], R]. Placing
> keyword-only parameters between the *args and **kwargs is forbidden.
Getting the documentation to build in nitpicky mode is quite difficult... We
need to add `nitpick_ignore` to the docs conf.py, otherwise sphinx complains
about many missing class references. This, despite upgrading almost all doc
requirements (except docutils).
2022-10-06 10:05:01 +00:00
|
|
|
idna==3.4
|
2021-02-04 08:31:48 +00:00
|
|
|
# via
|
|
|
|
|
# -r requirements/base.txt
|
|
|
|
|
# requests
|
2023-01-06 18:02:17 +00:00
|
|
|
importlib-metadata==6.0.0
|
2021-02-25 08:09:14 +00:00
|
|
|
# via
|
2023-02-09 11:13:24 +00:00
|
|
|
# -r requirements/base.txt
|
|
|
|
|
# build
|
|
|
|
|
# click
|
2021-02-25 08:09:14 +00:00
|
|
|
# keyring
|
2023-02-09 11:13:24 +00:00
|
|
|
# pyinstaller
|
2021-02-25 08:09:14 +00:00
|
|
|
# twine
|
2023-02-27 07:41:02 +00:00
|
|
|
importlib-resources==5.12.0
|
2023-02-09 11:13:24 +00:00
|
|
|
# via keyring
|
|
|
|
|
isort==5.11.5
|
2021-02-04 08:31:48 +00:00
|
|
|
# via pylint
|
feat: strongly typed hooks
Now that the mypy bugs have been resolved, we are able to define more precisely
and cleanly the types of Actions and Filters.
Moreover, can now strongly type named actions and hooks (in consts.py). With
such a strong typing, we get early alerts of hooks called with incorrect
arguments, which is nothing short of awesome :)
This change breaks the hooks API by removing the `context=...` argument. The
reason for that is that we cannot insert arbitrary arguments between `P.args,
P.kwargs`: https://peps.python.org/pep-0612/#the-components-of-a-paramspec
> A function declared as def inner(a: A, b: B, *args: P.args, **kwargs:
> P.kwargs) -> R has type Callable[Concatenate[A, B, P], R]. Placing
> keyword-only parameters between the *args and **kwargs is forbidden.
Getting the documentation to build in nitpicky mode is quite difficult... We
need to add `nitpick_ignore` to the docs conf.py, otherwise sphinx complains
about many missing class references. This, despite upgrading almost all doc
requirements (except docutils).
2022-10-06 10:05:01 +00:00
|
|
|
jaraco-classes==3.2.3
|
|
|
|
|
# via keyring
|
|
|
|
|
jeepney==0.8.0
|
2021-02-04 08:31:48 +00:00
|
|
|
# via
|
|
|
|
|
# keyring
|
|
|
|
|
# secretstorage
|
feat: strongly typed hooks
Now that the mypy bugs have been resolved, we are able to define more precisely
and cleanly the types of Actions and Filters.
Moreover, can now strongly type named actions and hooks (in consts.py). With
such a strong typing, we get early alerts of hooks called with incorrect
arguments, which is nothing short of awesome :)
This change breaks the hooks API by removing the `context=...` argument. The
reason for that is that we cannot insert arbitrary arguments between `P.args,
P.kwargs`: https://peps.python.org/pep-0612/#the-components-of-a-paramspec
> A function declared as def inner(a: A, b: B, *args: P.args, **kwargs:
> P.kwargs) -> R has type Callable[Concatenate[A, B, P], R]. Placing
> keyword-only parameters between the *args and **kwargs is forbidden.
Getting the documentation to build in nitpicky mode is quite difficult... We
need to add `nitpick_ignore` to the docs conf.py, otherwise sphinx complains
about many missing class references. This, despite upgrading almost all doc
requirements (except docutils).
2022-10-06 10:05:01 +00:00
|
|
|
jinja2==3.1.2
|
2022-11-21 15:35:14 +00:00
|
|
|
# via
|
|
|
|
|
# -r requirements/base.txt
|
|
|
|
|
# scriv
|
2023-02-09 10:57:26 +00:00
|
|
|
keyring==23.13.1
|
2021-02-04 08:31:48 +00:00
|
|
|
# via twine
|
2023-02-27 07:41:02 +00:00
|
|
|
kubernetes==26.1.0
|
2021-02-04 08:31:48 +00:00
|
|
|
# via -r requirements/base.txt
|
2023-02-09 10:57:26 +00:00
|
|
|
lazy-object-proxy==1.9.0
|
2021-02-04 08:31:48 +00:00
|
|
|
# via astroid
|
2023-02-27 07:41:02 +00:00
|
|
|
markdown-it-py==2.2.0
|
2023-02-09 10:57:26 +00:00
|
|
|
# via rich
|
|
|
|
|
markupsafe==2.1.2
|
2021-02-04 08:31:48 +00:00
|
|
|
# via
|
|
|
|
|
# -r requirements/base.txt
|
|
|
|
|
# jinja2
|
feat: strongly typed hooks
Now that the mypy bugs have been resolved, we are able to define more precisely
and cleanly the types of Actions and Filters.
Moreover, can now strongly type named actions and hooks (in consts.py). With
such a strong typing, we get early alerts of hooks called with incorrect
arguments, which is nothing short of awesome :)
This change breaks the hooks API by removing the `context=...` argument. The
reason for that is that we cannot insert arbitrary arguments between `P.args,
P.kwargs`: https://peps.python.org/pep-0612/#the-components-of-a-paramspec
> A function declared as def inner(a: A, b: B, *args: P.args, **kwargs:
> P.kwargs) -> R has type Callable[Concatenate[A, B, P], R]. Placing
> keyword-only parameters between the *args and **kwargs is forbidden.
Getting the documentation to build in nitpicky mode is quite difficult... We
need to add `nitpick_ignore` to the docs conf.py, otherwise sphinx complains
about many missing class references. This, despite upgrading almost all doc
requirements (except docutils).
2022-10-06 10:05:01 +00:00
|
|
|
mccabe==0.7.0
|
2021-02-04 08:31:48 +00:00
|
|
|
# via pylint
|
2023-02-09 10:57:26 +00:00
|
|
|
mdurl==0.1.2
|
|
|
|
|
# via markdown-it-py
|
feat: strongly typed hooks
Now that the mypy bugs have been resolved, we are able to define more precisely
and cleanly the types of Actions and Filters.
Moreover, can now strongly type named actions and hooks (in consts.py). With
such a strong typing, we get early alerts of hooks called with incorrect
arguments, which is nothing short of awesome :)
This change breaks the hooks API by removing the `context=...` argument. The
reason for that is that we cannot insert arbitrary arguments between `P.args,
P.kwargs`: https://peps.python.org/pep-0612/#the-components-of-a-paramspec
> A function declared as def inner(a: A, b: B, *args: P.args, **kwargs:
> P.kwargs) -> R has type Callable[Concatenate[A, B, P], R]. Placing
> keyword-only parameters between the *args and **kwargs is forbidden.
Getting the documentation to build in nitpicky mode is quite difficult... We
need to add `nitpick_ignore` to the docs conf.py, otherwise sphinx complains
about many missing class references. This, despite upgrading almost all doc
requirements (except docutils).
2022-10-06 10:05:01 +00:00
|
|
|
more-itertools==9.0.0
|
|
|
|
|
# via jaraco-classes
|
2023-02-27 07:41:02 +00:00
|
|
|
mypy==1.0.1
|
2021-07-01 19:35:26 +00:00
|
|
|
# via -r requirements/base.txt
|
2023-02-09 10:57:26 +00:00
|
|
|
mypy-extensions==1.0.0
|
2021-02-25 08:09:14 +00:00
|
|
|
# via
|
|
|
|
|
# -r requirements/base.txt
|
|
|
|
|
# black
|
|
|
|
|
# mypy
|
feat: strongly typed hooks
Now that the mypy bugs have been resolved, we are able to define more precisely
and cleanly the types of Actions and Filters.
Moreover, can now strongly type named actions and hooks (in consts.py). With
such a strong typing, we get early alerts of hooks called with incorrect
arguments, which is nothing short of awesome :)
This change breaks the hooks API by removing the `context=...` argument. The
reason for that is that we cannot insert arbitrary arguments between `P.args,
P.kwargs`: https://peps.python.org/pep-0612/#the-components-of-a-paramspec
> A function declared as def inner(a: A, b: B, *args: P.args, **kwargs:
> P.kwargs) -> R has type Callable[Concatenate[A, B, P], R]. Placing
> keyword-only parameters between the *args and **kwargs is forbidden.
Getting the documentation to build in nitpicky mode is quite difficult... We
need to add `nitpick_ignore` to the docs conf.py, otherwise sphinx complains
about many missing class references. This, despite upgrading almost all doc
requirements (except docutils).
2022-10-06 10:05:01 +00:00
|
|
|
oauthlib==3.2.2
|
2021-02-04 08:31:48 +00:00
|
|
|
# via
|
|
|
|
|
# -r requirements/base.txt
|
|
|
|
|
# requests-oauthlib
|
2023-02-09 10:57:26 +00:00
|
|
|
packaging==23.0
|
|
|
|
|
# via
|
|
|
|
|
# black
|
|
|
|
|
# build
|
|
|
|
|
pathspec==0.11.0
|
2021-02-04 08:31:48 +00:00
|
|
|
# via black
|
2023-02-09 10:57:26 +00:00
|
|
|
pip-tools==6.12.2
|
2021-02-04 08:31:48 +00:00
|
|
|
# via -r requirements/dev.in
|
2023-02-09 10:57:26 +00:00
|
|
|
pkginfo==1.9.6
|
2021-02-04 08:31:48 +00:00
|
|
|
# via twine
|
2023-02-09 10:57:26 +00:00
|
|
|
platformdirs==3.0.0
|
2021-09-23 04:10:05 +00:00
|
|
|
# via
|
|
|
|
|
# black
|
|
|
|
|
# pylint
|
2021-02-04 08:31:48 +00:00
|
|
|
pyasn1==0.4.8
|
|
|
|
|
# via
|
|
|
|
|
# -r requirements/base.txt
|
|
|
|
|
# pyasn1-modules
|
|
|
|
|
# rsa
|
2021-07-01 19:35:26 +00:00
|
|
|
pyasn1-modules==0.2.8
|
|
|
|
|
# via
|
|
|
|
|
# -r requirements/base.txt
|
|
|
|
|
# google-auth
|
feat: strongly typed hooks
Now that the mypy bugs have been resolved, we are able to define more precisely
and cleanly the types of Actions and Filters.
Moreover, can now strongly type named actions and hooks (in consts.py). With
such a strong typing, we get early alerts of hooks called with incorrect
arguments, which is nothing short of awesome :)
This change breaks the hooks API by removing the `context=...` argument. The
reason for that is that we cannot insert arbitrary arguments between `P.args,
P.kwargs`: https://peps.python.org/pep-0612/#the-components-of-a-paramspec
> A function declared as def inner(a: A, b: B, *args: P.args, **kwargs:
> P.kwargs) -> R has type Callable[Concatenate[A, B, P], R]. Placing
> keyword-only parameters between the *args and **kwargs is forbidden.
Getting the documentation to build in nitpicky mode is quite difficult... We
need to add `nitpick_ignore` to the docs conf.py, otherwise sphinx complains
about many missing class references. This, despite upgrading almost all doc
requirements (except docutils).
2022-10-06 10:05:01 +00:00
|
|
|
pycparser==2.21
|
2021-02-04 08:31:48 +00:00
|
|
|
# via cffi
|
2023-02-09 10:57:26 +00:00
|
|
|
pycryptodome==3.17
|
2021-02-04 08:31:48 +00:00
|
|
|
# via -r requirements/base.txt
|
2023-02-09 10:57:26 +00:00
|
|
|
pygments==2.14.0
|
feat: strongly typed hooks
Now that the mypy bugs have been resolved, we are able to define more precisely
and cleanly the types of Actions and Filters.
Moreover, can now strongly type named actions and hooks (in consts.py). With
such a strong typing, we get early alerts of hooks called with incorrect
arguments, which is nothing short of awesome :)
This change breaks the hooks API by removing the `context=...` argument. The
reason for that is that we cannot insert arbitrary arguments between `P.args,
P.kwargs`: https://peps.python.org/pep-0612/#the-components-of-a-paramspec
> A function declared as def inner(a: A, b: B, *args: P.args, **kwargs:
> P.kwargs) -> R has type Callable[Concatenate[A, B, P], R]. Placing
> keyword-only parameters between the *args and **kwargs is forbidden.
Getting the documentation to build in nitpicky mode is quite difficult... We
need to add `nitpick_ignore` to the docs conf.py, otherwise sphinx complains
about many missing class references. This, despite upgrading almost all doc
requirements (except docutils).
2022-10-06 10:05:01 +00:00
|
|
|
# via
|
|
|
|
|
# readme-renderer
|
|
|
|
|
# rich
|
2023-02-27 07:41:02 +00:00
|
|
|
pyinstaller==5.8.0
|
2021-02-04 08:31:48 +00:00
|
|
|
# via -r requirements/dev.in
|
2023-02-27 07:41:02 +00:00
|
|
|
pyinstaller-hooks-contrib==2023.0
|
2021-07-01 19:35:26 +00:00
|
|
|
# via pyinstaller
|
2023-02-27 07:41:02 +00:00
|
|
|
pylint==2.16.2
|
2021-02-04 08:31:48 +00:00
|
|
|
# via -r requirements/dev.in
|
2023-02-09 10:57:26 +00:00
|
|
|
pyproject-hooks==1.0.0
|
|
|
|
|
# via build
|
2021-09-23 04:10:05 +00:00
|
|
|
python-dateutil==2.8.2
|
2021-02-04 08:31:48 +00:00
|
|
|
# via
|
|
|
|
|
# -r requirements/base.txt
|
|
|
|
|
# kubernetes
|
2021-10-25 18:18:07 +00:00
|
|
|
pyyaml==6.0
|
2021-02-04 08:31:48 +00:00
|
|
|
# via
|
|
|
|
|
# -r requirements/base.txt
|
|
|
|
|
# kubernetes
|
feat: strongly typed hooks
Now that the mypy bugs have been resolved, we are able to define more precisely
and cleanly the types of Actions and Filters.
Moreover, can now strongly type named actions and hooks (in consts.py). With
such a strong typing, we get early alerts of hooks called with incorrect
arguments, which is nothing short of awesome :)
This change breaks the hooks API by removing the `context=...` argument. The
reason for that is that we cannot insert arbitrary arguments between `P.args,
P.kwargs`: https://peps.python.org/pep-0612/#the-components-of-a-paramspec
> A function declared as def inner(a: A, b: B, *args: P.args, **kwargs:
> P.kwargs) -> R has type Callable[Concatenate[A, B, P], R]. Placing
> keyword-only parameters between the *args and **kwargs is forbidden.
Getting the documentation to build in nitpicky mode is quite difficult... We
need to add `nitpick_ignore` to the docs conf.py, otherwise sphinx complains
about many missing class references. This, despite upgrading almost all doc
requirements (except docutils).
2022-10-06 10:05:01 +00:00
|
|
|
readme-renderer==37.3
|
2021-02-04 08:31:48 +00:00
|
|
|
# via twine
|
2023-02-09 10:57:26 +00:00
|
|
|
requests==2.28.2
|
2021-02-04 08:31:48 +00:00
|
|
|
# via
|
|
|
|
|
# -r requirements/base.txt
|
|
|
|
|
# kubernetes
|
|
|
|
|
# requests-oauthlib
|
|
|
|
|
# requests-toolbelt
|
2022-11-21 15:35:14 +00:00
|
|
|
# scriv
|
2021-02-04 08:31:48 +00:00
|
|
|
# twine
|
feat: strongly typed hooks
Now that the mypy bugs have been resolved, we are able to define more precisely
and cleanly the types of Actions and Filters.
Moreover, can now strongly type named actions and hooks (in consts.py). With
such a strong typing, we get early alerts of hooks called with incorrect
arguments, which is nothing short of awesome :)
This change breaks the hooks API by removing the `context=...` argument. The
reason for that is that we cannot insert arbitrary arguments between `P.args,
P.kwargs`: https://peps.python.org/pep-0612/#the-components-of-a-paramspec
> A function declared as def inner(a: A, b: B, *args: P.args, **kwargs:
> P.kwargs) -> R has type Callable[Concatenate[A, B, P], R]. Placing
> keyword-only parameters between the *args and **kwargs is forbidden.
Getting the documentation to build in nitpicky mode is quite difficult... We
need to add `nitpick_ignore` to the docs conf.py, otherwise sphinx complains
about many missing class references. This, despite upgrading almost all doc
requirements (except docutils).
2022-10-06 10:05:01 +00:00
|
|
|
requests-oauthlib==1.3.1
|
2021-07-01 19:35:26 +00:00
|
|
|
# via
|
|
|
|
|
# -r requirements/base.txt
|
|
|
|
|
# kubernetes
|
feat: strongly typed hooks
Now that the mypy bugs have been resolved, we are able to define more precisely
and cleanly the types of Actions and Filters.
Moreover, can now strongly type named actions and hooks (in consts.py). With
such a strong typing, we get early alerts of hooks called with incorrect
arguments, which is nothing short of awesome :)
This change breaks the hooks API by removing the `context=...` argument. The
reason for that is that we cannot insert arbitrary arguments between `P.args,
P.kwargs`: https://peps.python.org/pep-0612/#the-components-of-a-paramspec
> A function declared as def inner(a: A, b: B, *args: P.args, **kwargs:
> P.kwargs) -> R has type Callable[Concatenate[A, B, P], R]. Placing
> keyword-only parameters between the *args and **kwargs is forbidden.
Getting the documentation to build in nitpicky mode is quite difficult... We
need to add `nitpick_ignore` to the docs conf.py, otherwise sphinx complains
about many missing class references. This, despite upgrading almost all doc
requirements (except docutils).
2022-10-06 10:05:01 +00:00
|
|
|
requests-toolbelt==0.10.1
|
2021-07-01 19:35:26 +00:00
|
|
|
# via twine
|
feat: strongly typed hooks
Now that the mypy bugs have been resolved, we are able to define more precisely
and cleanly the types of Actions and Filters.
Moreover, can now strongly type named actions and hooks (in consts.py). With
such a strong typing, we get early alerts of hooks called with incorrect
arguments, which is nothing short of awesome :)
This change breaks the hooks API by removing the `context=...` argument. The
reason for that is that we cannot insert arbitrary arguments between `P.args,
P.kwargs`: https://peps.python.org/pep-0612/#the-components-of-a-paramspec
> A function declared as def inner(a: A, b: B, *args: P.args, **kwargs:
> P.kwargs) -> R has type Callable[Concatenate[A, B, P], R]. Placing
> keyword-only parameters between the *args and **kwargs is forbidden.
Getting the documentation to build in nitpicky mode is quite difficult... We
need to add `nitpick_ignore` to the docs conf.py, otherwise sphinx complains
about many missing class references. This, despite upgrading almost all doc
requirements (except docutils).
2022-10-06 10:05:01 +00:00
|
|
|
rfc3986==2.0.0
|
2021-02-04 08:31:48 +00:00
|
|
|
# via twine
|
2023-02-09 10:57:26 +00:00
|
|
|
rich==13.3.1
|
feat: strongly typed hooks
Now that the mypy bugs have been resolved, we are able to define more precisely
and cleanly the types of Actions and Filters.
Moreover, can now strongly type named actions and hooks (in consts.py). With
such a strong typing, we get early alerts of hooks called with incorrect
arguments, which is nothing short of awesome :)
This change breaks the hooks API by removing the `context=...` argument. The
reason for that is that we cannot insert arbitrary arguments between `P.args,
P.kwargs`: https://peps.python.org/pep-0612/#the-components-of-a-paramspec
> A function declared as def inner(a: A, b: B, *args: P.args, **kwargs:
> P.kwargs) -> R has type Callable[Concatenate[A, B, P], R]. Placing
> keyword-only parameters between the *args and **kwargs is forbidden.
Getting the documentation to build in nitpicky mode is quite difficult... We
need to add `nitpick_ignore` to the docs conf.py, otherwise sphinx complains
about many missing class references. This, despite upgrading almost all doc
requirements (except docutils).
2022-10-06 10:05:01 +00:00
|
|
|
# via twine
|
|
|
|
|
rsa==4.9
|
2021-02-04 08:31:48 +00:00
|
|
|
# via
|
|
|
|
|
# -r requirements/base.txt
|
|
|
|
|
# google-auth
|
2023-02-27 07:41:02 +00:00
|
|
|
scriv==1.2.1
|
2022-11-21 15:35:14 +00:00
|
|
|
# via -r requirements/dev.in
|
feat: strongly typed hooks
Now that the mypy bugs have been resolved, we are able to define more precisely
and cleanly the types of Actions and Filters.
Moreover, can now strongly type named actions and hooks (in consts.py). With
such a strong typing, we get early alerts of hooks called with incorrect
arguments, which is nothing short of awesome :)
This change breaks the hooks API by removing the `context=...` argument. The
reason for that is that we cannot insert arbitrary arguments between `P.args,
P.kwargs`: https://peps.python.org/pep-0612/#the-components-of-a-paramspec
> A function declared as def inner(a: A, b: B, *args: P.args, **kwargs:
> P.kwargs) -> R has type Callable[Concatenate[A, B, P], R]. Placing
> keyword-only parameters between the *args and **kwargs is forbidden.
Getting the documentation to build in nitpicky mode is quite difficult... We
need to add `nitpick_ignore` to the docs conf.py, otherwise sphinx complains
about many missing class references. This, despite upgrading almost all doc
requirements (except docutils).
2022-10-06 10:05:01 +00:00
|
|
|
secretstorage==3.3.3
|
2021-02-04 08:31:48 +00:00
|
|
|
# via keyring
|
2021-05-12 08:01:50 +00:00
|
|
|
six==1.16.0
|
2021-02-04 08:31:48 +00:00
|
|
|
# via
|
|
|
|
|
# -r requirements/base.txt
|
|
|
|
|
# bleach
|
2021-10-25 18:18:07 +00:00
|
|
|
# google-auth
|
2021-02-04 08:31:48 +00:00
|
|
|
# kubernetes
|
|
|
|
|
# python-dateutil
|
2022-02-07 17:11:43 +00:00
|
|
|
tomli==2.0.1
|
2021-02-04 08:31:48 +00:00
|
|
|
# via
|
2021-07-01 19:35:26 +00:00
|
|
|
# -r requirements/base.txt
|
2021-09-23 04:10:05 +00:00
|
|
|
# black
|
2022-09-29 11:53:19 +00:00
|
|
|
# build
|
2022-02-07 17:11:43 +00:00
|
|
|
# mypy
|
feat: strongly typed hooks
Now that the mypy bugs have been resolved, we are able to define more precisely
and cleanly the types of Actions and Filters.
Moreover, can now strongly type named actions and hooks (in consts.py). With
such a strong typing, we get early alerts of hooks called with incorrect
arguments, which is nothing short of awesome :)
This change breaks the hooks API by removing the `context=...` argument. The
reason for that is that we cannot insert arbitrary arguments between `P.args,
P.kwargs`: https://peps.python.org/pep-0612/#the-components-of-a-paramspec
> A function declared as def inner(a: A, b: B, *args: P.args, **kwargs:
> P.kwargs) -> R has type Callable[Concatenate[A, B, P], R]. Placing
> keyword-only parameters between the *args and **kwargs is forbidden.
Getting the documentation to build in nitpicky mode is quite difficult... We
need to add `nitpick_ignore` to the docs conf.py, otherwise sphinx complains
about many missing class references. This, despite upgrading almost all doc
requirements (except docutils).
2022-10-06 10:05:01 +00:00
|
|
|
# pylint
|
2023-02-09 10:57:26 +00:00
|
|
|
# pyproject-hooks
|
feat: strongly typed hooks
Now that the mypy bugs have been resolved, we are able to define more precisely
and cleanly the types of Actions and Filters.
Moreover, can now strongly type named actions and hooks (in consts.py). With
such a strong typing, we get early alerts of hooks called with incorrect
arguments, which is nothing short of awesome :)
This change breaks the hooks API by removing the `context=...` argument. The
reason for that is that we cannot insert arbitrary arguments between `P.args,
P.kwargs`: https://peps.python.org/pep-0612/#the-components-of-a-paramspec
> A function declared as def inner(a: A, b: B, *args: P.args, **kwargs:
> P.kwargs) -> R has type Callable[Concatenate[A, B, P], R]. Placing
> keyword-only parameters between the *args and **kwargs is forbidden.
Getting the documentation to build in nitpicky mode is quite difficult... We
need to add `nitpick_ignore` to the docs conf.py, otherwise sphinx complains
about many missing class references. This, despite upgrading almost all doc
requirements (except docutils).
2022-10-06 10:05:01 +00:00
|
|
|
tomlkit==0.11.6
|
|
|
|
|
# via pylint
|
2022-11-22 12:53:29 +00:00
|
|
|
twine==4.0.2
|
2021-02-04 08:31:48 +00:00
|
|
|
# via -r requirements/dev.in
|
2023-02-09 11:13:24 +00:00
|
|
|
typed-ast==1.5.4
|
|
|
|
|
# via
|
|
|
|
|
# -r requirements/base.txt
|
|
|
|
|
# astroid
|
|
|
|
|
# black
|
|
|
|
|
# mypy
|
2023-02-27 07:41:02 +00:00
|
|
|
types-docutils==0.19.1.6
|
|
|
|
|
# via -r requirements/dev.in
|
|
|
|
|
types-pyyaml==6.0.12.8
|
2021-07-01 19:35:26 +00:00
|
|
|
# via -r requirements/dev.in
|
2023-02-27 07:41:02 +00:00
|
|
|
types-setuptools==67.4.0.3
|
2021-07-01 19:35:26 +00:00
|
|
|
# via -r requirements/dev.in
|
2023-02-27 07:41:02 +00:00
|
|
|
typing-extensions==4.5.0
|
2021-02-25 08:09:14 +00:00
|
|
|
# via
|
|
|
|
|
# -r requirements/base.txt
|
2023-02-09 10:57:26 +00:00
|
|
|
# astroid
|
2023-02-09 11:13:24 +00:00
|
|
|
# black
|
|
|
|
|
# importlib-metadata
|
|
|
|
|
# markdown-it-py
|
2021-02-25 08:09:14 +00:00
|
|
|
# mypy
|
2023-02-09 11:13:24 +00:00
|
|
|
# platformdirs
|
|
|
|
|
# pylint
|
|
|
|
|
# rich
|
2023-02-09 10:57:26 +00:00
|
|
|
urllib3==1.26.14
|
2021-02-04 08:31:48 +00:00
|
|
|
# via
|
|
|
|
|
# -r requirements/base.txt
|
|
|
|
|
# kubernetes
|
|
|
|
|
# requests
|
feat: strongly typed hooks
Now that the mypy bugs have been resolved, we are able to define more precisely
and cleanly the types of Actions and Filters.
Moreover, can now strongly type named actions and hooks (in consts.py). With
such a strong typing, we get early alerts of hooks called with incorrect
arguments, which is nothing short of awesome :)
This change breaks the hooks API by removing the `context=...` argument. The
reason for that is that we cannot insert arbitrary arguments between `P.args,
P.kwargs`: https://peps.python.org/pep-0612/#the-components-of-a-paramspec
> A function declared as def inner(a: A, b: B, *args: P.args, **kwargs:
> P.kwargs) -> R has type Callable[Concatenate[A, B, P], R]. Placing
> keyword-only parameters between the *args and **kwargs is forbidden.
Getting the documentation to build in nitpicky mode is quite difficult... We
need to add `nitpick_ignore` to the docs conf.py, otherwise sphinx complains
about many missing class references. This, despite upgrading almost all doc
requirements (except docutils).
2022-10-06 10:05:01 +00:00
|
|
|
# twine
|
2021-02-04 08:31:48 +00:00
|
|
|
webencodings==0.5.1
|
|
|
|
|
# via bleach
|
2023-02-09 10:57:26 +00:00
|
|
|
websocket-client==1.5.1
|
2021-02-04 08:31:48 +00:00
|
|
|
# via
|
|
|
|
|
# -r requirements/base.txt
|
|
|
|
|
# kubernetes
|
feat: strongly typed hooks
Now that the mypy bugs have been resolved, we are able to define more precisely
and cleanly the types of Actions and Filters.
Moreover, can now strongly type named actions and hooks (in consts.py). With
such a strong typing, we get early alerts of hooks called with incorrect
arguments, which is nothing short of awesome :)
This change breaks the hooks API by removing the `context=...` argument. The
reason for that is that we cannot insert arbitrary arguments between `P.args,
P.kwargs`: https://peps.python.org/pep-0612/#the-components-of-a-paramspec
> A function declared as def inner(a: A, b: B, *args: P.args, **kwargs:
> P.kwargs) -> R has type Callable[Concatenate[A, B, P], R]. Placing
> keyword-only parameters between the *args and **kwargs is forbidden.
Getting the documentation to build in nitpicky mode is quite difficult... We
need to add `nitpick_ignore` to the docs conf.py, otherwise sphinx complains
about many missing class references. This, despite upgrading almost all doc
requirements (except docutils).
2022-10-06 10:05:01 +00:00
|
|
|
wheel==0.38.4
|
2021-07-01 19:35:26 +00:00
|
|
|
# via pip-tools
|
2023-02-27 07:41:02 +00:00
|
|
|
wrapt==1.15.0
|
2021-02-04 08:31:48 +00:00
|
|
|
# via astroid
|
2023-02-27 07:41:02 +00:00
|
|
|
zipp==3.15.0
|
2023-02-09 11:13:24 +00:00
|
|
|
# via
|
|
|
|
|
# -r requirements/base.txt
|
|
|
|
|
# importlib-metadata
|
|
|
|
|
# importlib-resources
|
2020-01-13 21:33:12 +00:00
|
|
|
|
|
|
|
|
# The following packages are considered to be unsafe in a requirements file:
|
2019-12-24 16:22:12 +00:00
|
|
|
# pip
|
2020-01-13 21:33:12 +00:00
|
|
|
# setuptools
|
