tutor/requirements/dev.txt

209 lines
4.0 KiB
Plaintext
Raw Normal View History

#
# This file is autogenerated by pip-compile with python 3.8
# To update, run:
#
2020-01-13 21:33:12 +00:00
# pip-compile requirements/dev.in
#
altgraph==0.17.2
# via pyinstaller
appdirs==1.4.4
# via -r requirements/base.txt
astroid==2.8.3
# via pylint
feat: migrate to plugins.v1 with filters & actions This is a very large refactoring which aims at making Tutor both more extendable and more generic. Historically, the Tutor plugin system was designed as an ad-hoc solution to allow developers to modify their own Open edX platforms without having to fork Tutor. The plugin API was simple, but limited, because of its ad-hoc nature. As a consequence, there were many things that plugin developers could not do, such as extending different parts of the CLI or adding custom template filters. Here, we refactor the whole codebase to make use of a generic plugin system. This system was inspired by the Wordpress plugin API and the Open edX "hooks and filters" API. The various components are added to a small core thanks to a set of actions and filters. Actions are callback functions that can be triggered at different points of the application lifecycle. Filters are functions that modify some data. Both actions and filters are collectively named as "hooks". Hooks can optionally be created within a certain context, which makes it easier to keep track of which application created which callback. This new hooks system allows us to provide a Python API that developers can use to extend their applications. The API reference is added to the documentation, along with a new plugin development tutorial. The plugin v0 API remains supported for backward compatibility of existing plugins. Done: - Do not load commands from plugins which are not enabled. - Load enabled plugins once on start. - Implement contexts for actions and filters, which allow us to keep track of the source of every hook. - Migrate patches - Migrate commands - Migrate plugin detection - Migrate templates_root - Migrate config - Migrate template environment globals and filters - Migrate hooks to tasks - Generate hook documentation - Generate patch reference documentation - Add the concept of action priority Close #499.
2022-02-07 17:11:43 +00:00
black==22.1.0
# via -r requirements/dev.in
bleach==4.1.0
# via readme-renderer
cachetools==4.2.4
# via
# -r requirements/base.txt
# google-auth
certifi==2021.10.8
# via
# -r requirements/base.txt
# kubernetes
# requests
cffi==1.15.0
# via cryptography
charset-normalizer==2.0.7
# via
# -r requirements/base.txt
# requests
click==8.0.3
# via
# -r requirements/base.txt
# black
# pip-tools
colorama==0.4.4
# via twine
coverage==6.2
# via -r requirements/dev.in
cryptography==35.0.0
# via secretstorage
docutils==0.17.1
# via readme-renderer
google-auth==2.3.1
# via
# -r requirements/base.txt
# kubernetes
idna==3.3
# via
# -r requirements/base.txt
# requests
importlib-metadata==4.8.1
# via
# keyring
# twine
isort==5.9.3
# via pylint
jeepney==0.7.1
# via
# keyring
# secretstorage
jinja2==3.0.2
# via -r requirements/base.txt
keyring==23.2.1
# via twine
kubernetes==18.20.0
# via -r requirements/base.txt
lazy-object-proxy==1.6.0
# via astroid
markupsafe==2.0.1
# via
# -r requirements/base.txt
# jinja2
mccabe==0.6.1
# via pylint
feat: migrate to plugins.v1 with filters & actions This is a very large refactoring which aims at making Tutor both more extendable and more generic. Historically, the Tutor plugin system was designed as an ad-hoc solution to allow developers to modify their own Open edX platforms without having to fork Tutor. The plugin API was simple, but limited, because of its ad-hoc nature. As a consequence, there were many things that plugin developers could not do, such as extending different parts of the CLI or adding custom template filters. Here, we refactor the whole codebase to make use of a generic plugin system. This system was inspired by the Wordpress plugin API and the Open edX "hooks and filters" API. The various components are added to a small core thanks to a set of actions and filters. Actions are callback functions that can be triggered at different points of the application lifecycle. Filters are functions that modify some data. Both actions and filters are collectively named as "hooks". Hooks can optionally be created within a certain context, which makes it easier to keep track of which application created which callback. This new hooks system allows us to provide a Python API that developers can use to extend their applications. The API reference is added to the documentation, along with a new plugin development tutorial. The plugin v0 API remains supported for backward compatibility of existing plugins. Done: - Do not load commands from plugins which are not enabled. - Load enabled plugins once on start. - Implement contexts for actions and filters, which allow us to keep track of the source of every hook. - Migrate patches - Migrate commands - Migrate plugin detection - Migrate templates_root - Migrate config - Migrate template environment globals and filters - Migrate hooks to tasks - Generate hook documentation - Generate patch reference documentation - Add the concept of action priority Close #499.
2022-02-07 17:11:43 +00:00
mypy==0.942
# via -r requirements/base.txt
mypy-extensions==0.4.3
# via
# -r requirements/base.txt
# black
# mypy
oauthlib==3.1.1
# via
# -r requirements/base.txt
# requests-oauthlib
packaging==21.0
# via bleach
pathspec==0.9.0
# via black
pep517==0.12.0
# via pip-tools
pip-tools==6.4.0
# via -r requirements/dev.in
pkginfo==1.7.1
# via twine
platformdirs==2.4.0
# via
# black
# pylint
pyasn1==0.4.8
# via
# -r requirements/base.txt
# pyasn1-modules
# rsa
pyasn1-modules==0.2.8
# via
# -r requirements/base.txt
# google-auth
pycparser==2.20
# via cffi
pycryptodome==3.11.0
# via -r requirements/base.txt
pygments==2.10.0
# via readme-renderer
pyinstaller==4.5.1
# via -r requirements/dev.in
pyinstaller-hooks-contrib==2021.3
# via pyinstaller
pylint==2.11.1
# via -r requirements/dev.in
pyparsing==3.0.1
# via packaging
python-dateutil==2.8.2
# via
# -r requirements/base.txt
# kubernetes
pyyaml==6.0
# via
# -r requirements/base.txt
# kubernetes
readme-renderer==30.0
# via twine
requests==2.26.0
# via
# -r requirements/base.txt
# kubernetes
# requests-oauthlib
# requests-toolbelt
# twine
requests-oauthlib==1.3.0
# via
# -r requirements/base.txt
# kubernetes
requests-toolbelt==0.9.1
# via twine
rfc3986==1.5.0
# via twine
rsa==4.7.2
# via
# -r requirements/base.txt
# google-auth
secretstorage==3.3.1
# via keyring
six==1.16.0
# via
# -r requirements/base.txt
# bleach
# google-auth
# kubernetes
# python-dateutil
toml==0.10.2
feat: migrate to plugins.v1 with filters & actions This is a very large refactoring which aims at making Tutor both more extendable and more generic. Historically, the Tutor plugin system was designed as an ad-hoc solution to allow developers to modify their own Open edX platforms without having to fork Tutor. The plugin API was simple, but limited, because of its ad-hoc nature. As a consequence, there were many things that plugin developers could not do, such as extending different parts of the CLI or adding custom template filters. Here, we refactor the whole codebase to make use of a generic plugin system. This system was inspired by the Wordpress plugin API and the Open edX "hooks and filters" API. The various components are added to a small core thanks to a set of actions and filters. Actions are callback functions that can be triggered at different points of the application lifecycle. Filters are functions that modify some data. Both actions and filters are collectively named as "hooks". Hooks can optionally be created within a certain context, which makes it easier to keep track of which application created which callback. This new hooks system allows us to provide a Python API that developers can use to extend their applications. The API reference is added to the documentation, along with a new plugin development tutorial. The plugin v0 API remains supported for backward compatibility of existing plugins. Done: - Do not load commands from plugins which are not enabled. - Load enabled plugins once on start. - Implement contexts for actions and filters, which allow us to keep track of the source of every hook. - Migrate patches - Migrate commands - Migrate plugin detection - Migrate templates_root - Migrate config - Migrate template environment globals and filters - Migrate hooks to tasks - Generate hook documentation - Generate patch reference documentation - Add the concept of action priority Close #499.
2022-02-07 17:11:43 +00:00
# via pylint
tomli==2.0.1
# via
# -r requirements/base.txt
# black
feat: migrate to plugins.v1 with filters & actions This is a very large refactoring which aims at making Tutor both more extendable and more generic. Historically, the Tutor plugin system was designed as an ad-hoc solution to allow developers to modify their own Open edX platforms without having to fork Tutor. The plugin API was simple, but limited, because of its ad-hoc nature. As a consequence, there were many things that plugin developers could not do, such as extending different parts of the CLI or adding custom template filters. Here, we refactor the whole codebase to make use of a generic plugin system. This system was inspired by the Wordpress plugin API and the Open edX "hooks and filters" API. The various components are added to a small core thanks to a set of actions and filters. Actions are callback functions that can be triggered at different points of the application lifecycle. Filters are functions that modify some data. Both actions and filters are collectively named as "hooks". Hooks can optionally be created within a certain context, which makes it easier to keep track of which application created which callback. This new hooks system allows us to provide a Python API that developers can use to extend their applications. The API reference is added to the documentation, along with a new plugin development tutorial. The plugin v0 API remains supported for backward compatibility of existing plugins. Done: - Do not load commands from plugins which are not enabled. - Load enabled plugins once on start. - Implement contexts for actions and filters, which allow us to keep track of the source of every hook. - Migrate patches - Migrate commands - Migrate plugin detection - Migrate templates_root - Migrate config - Migrate template environment globals and filters - Migrate hooks to tasks - Generate hook documentation - Generate patch reference documentation - Add the concept of action priority Close #499.
2022-02-07 17:11:43 +00:00
# mypy
# pep517
tqdm==4.62.3
# via twine
twine==3.4.2
# via -r requirements/dev.in
feat: migrate to plugins.v1 with filters & actions This is a very large refactoring which aims at making Tutor both more extendable and more generic. Historically, the Tutor plugin system was designed as an ad-hoc solution to allow developers to modify their own Open edX platforms without having to fork Tutor. The plugin API was simple, but limited, because of its ad-hoc nature. As a consequence, there were many things that plugin developers could not do, such as extending different parts of the CLI or adding custom template filters. Here, we refactor the whole codebase to make use of a generic plugin system. This system was inspired by the Wordpress plugin API and the Open edX "hooks and filters" API. The various components are added to a small core thanks to a set of actions and filters. Actions are callback functions that can be triggered at different points of the application lifecycle. Filters are functions that modify some data. Both actions and filters are collectively named as "hooks". Hooks can optionally be created within a certain context, which makes it easier to keep track of which application created which callback. This new hooks system allows us to provide a Python API that developers can use to extend their applications. The API reference is added to the documentation, along with a new plugin development tutorial. The plugin v0 API remains supported for backward compatibility of existing plugins. Done: - Do not load commands from plugins which are not enabled. - Load enabled plugins once on start. - Implement contexts for actions and filters, which allow us to keep track of the source of every hook. - Migrate patches - Migrate commands - Migrate plugin detection - Migrate templates_root - Migrate config - Migrate template environment globals and filters - Migrate hooks to tasks - Generate hook documentation - Generate patch reference documentation - Add the concept of action priority Close #499.
2022-02-07 17:11:43 +00:00
types-docutils==0.18.0
# via -r requirements/dev.in
types-pyyaml==6.0.0
# via -r requirements/dev.in
types-setuptools==57.4.2
# via -r requirements/dev.in
typing-extensions==3.10.0.2
# via
# -r requirements/base.txt
# astroid
# black
# mypy
# pylint
urllib3==1.26.7
# via
# -r requirements/base.txt
# kubernetes
# requests
webencodings==0.5.1
# via bleach
websocket-client==1.2.1
# via
# -r requirements/base.txt
# kubernetes
wheel==0.37.0
# via pip-tools
wrapt==1.13.2
# via astroid
zipp==3.6.0
# via importlib-metadata
2020-01-13 21:33:12 +00:00
# The following packages are considered to be unsafe in a requirements file:
# pip
2020-01-13 21:33:12 +00:00
# setuptools