tutor/requirements/base.in

appdirs
click>=8.0
mypy
pycryptodome
jinja2>=2.10
kubernetes
pyyaml>=6.0
Tutor v3 complete rewrite Replace all make commands by a single "tutor" binary. Environment and data are all moved to ~/.tutor/local/share/tutor. We take the opportunity to add a web UI and revamp the documentation. This is a complete rewrite. Close #121. Close #147. 2019-01-22 20:25:04 +00:00			`appdirs`
fix: minimum click version is 8.0 An issue was reported here: https://app.slack.com/client/T02SNA1T6/CGE253B7V CompletionItem was introduced in 8.0, so click needs to be upgraded when we `pip install tutor`. 2022-11-23 17:19:27 +00:00			`click>=8.0`
refactor: add type annotations Annotations were generated with pyannotate: https://github.com/dropbox/pyannotate We are running in strict mode, which is awesome! This affects a large part of the code base, which might be an issue for people running a fork of Tutor. Nonetheless, the behavior should not be affected. If anything, this process has helped find and resolve a few type-related bugs. Thus, this is not considered as a breaking change. 2021-02-25 08:09:14 +00:00			`mypy`
v10.0.0 Upgrade to Juniper (2020-06-15) Here, we upgrade the Open edX platform from Ironwood to Juniper. This upgrade does not come with many feature changes, but there are many technical improvements under the hood: - Upgrade from Python 2.7 to 3.5 - Upgrade from Mongodb v3.2 to v3.6 - Upgrade Ruby to 2.5.7 We took the opportunity to completely rething the way locally running platforms should be accessed for testing purposes. It is no longer possible to access a running platform from http://localhost and http://studio.localhost. Instead, users should access http://local.overhang.io and https://studio.local.overhang.io. This drastically simplifies internal communication between Docker containers. To upgrade, users should simply run: tutor local quickstart For Kubernetes platform, the upgrade process is outlined when running: tutor k8s upgrade --from=ironwood 2019-12-24 16:22:12 +00:00			`pycryptodome`
fix: TemplateSyntaxError with old jinja2 The following syntax is only supported in jinja2>=2.10: {% set jwt_rsa_key \| rsa_import_key %}{{ JWT_RSA_PRIVATE_KEY }}{% endset %} Thus, we bump the minimal working version of jinja2 in the base requirements. See discussion: https://discuss.openedx.org/t/error-while-tutor-local-quickstart/8796 2022-11-28 08:20:28 +00:00			`jinja2>=2.10`
Improve job running in local and k8s Running jobs was previously done with "exec". This was because it allowed us to avoid copying too much container specification information from the docker-compose/deployments files to the jobs files. However, this was limiting: - In order to run a job, the corresponding container had to be running. This was particularly painful in Kubernetes, where containers are crashing as long as migrations are not correctly run. - Containers in which we need to run jobs needed to be present in the docker-compose/deployments files. This is unnecessary, for example when mysql is disabled, or in the case of the certbot container. Now, we create dedicated jobs files, both for local and k8s deployment. This introduces a little redundancy, but not too much. Note that dependent containers are not listed in the docker-compose.jobs.yml file, so an actual platform is still supposed to be running when we launch the jobs. This also introduces a subtle change: now, jobs go through the container entrypoint prior to running. This is probably a good thing, as it will avoid forgetting about incorrect environment variables. In k8s, we find ourselves interacting way too much with the kubectl utility. Parsing output from the CLI is a pain. So we need to switch to the native kubernetes client library. 2020-03-25 17:47:36 +00:00			`kubernetes`
feat: upgrade to olive 2022-11-22 12:53:29 +00:00			`pyyaml>=6.0`