F py37

Summary

For https://gitlab.indiscale.com/caosdb/internal/all/-/issues/1439. Re-introduce Python 3.7.

Focus

Point the reviewer to the core of the code change. Where should they start reading? What should they focus on (e.g. security, performance, maintainability, user-friendliness, compliance with the specs, finding more corner cases, concrete questions)?

Test Environment

How to set up a test environment for manual testing?

Check List for the Author

Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines

• All automated tests pass
• Reference related issues
• Up-to-date CHANGELOG.md (or not necessary)
• Annotations in code (Gitlab comments)
  • Intent of new code
  • Problems with old code
  • Why this implementation?

Check List for the Reviewer

• I understand the intent of this MR
• All automated tests pass
• Up-to-date CHANGELOG.md (or not necessary)
• The test environment setup works and the intended behavior is reproducible in the test environment
• In-code documentation and comments are up-to-date.
• Check: Are there specifications? Are they satisfied?

For further good practices have a look at our review guidelines.

.gitlab-ci.yml

@@ -54,18 +54,25 @@ pylint:
   allow_failure: true
 
 # run unit tests
-unittest_py3.8:
+unittest_py3.7:
   tags: [ docker ]
   stage: test
   needs: [ ]
-  image: python:3.8
+  image: python:3.7
   script: &python_test_script
     # Python docker has problems with tox and pip so use plain pytest here
     - touch ~/.pycaosdb.ini
-    - pip install nose pytest pytest-cov python-dateutil jsonschema==4.0.1
+    - pip install nose pytest pytest-cov python-dateutil jsonschema>=4.4.0
     - pip install .
     - python -m pytest unittests
 
+unittest_py3.8:
+  tags: [ docker ]
+  stage: test
+  needs: [ ]
+  image: python:3.8
+  script: *python_test_script
+
 # This needs to be changed once Python 3.9 isn't the standard Python in Debian
 # anymore.
 unittest_py3.9: