211 Python dependencies

[annette-lutz]

Merge Request - GuideLine Checklist

Guideline to check code before resolve WIP and approval, respectively.
As many checkboxes as possible should be ticked.

Checks by code author:

• There is at least one issue associated with the pull request.
• The branch follows the naming conventions as defined in the git workflow.
• New code adheres with the coding guidelines
• Tests for new functionality has been added
• A local test was succesful
• There is appropriate documentation of your work. (use doxygen style comments)
• If new third party software is used, did you pay attention to its license? Please remember to add it to the wiki after successful merging.
• If new mathematical methods or epidemiological terms are used, has the glossary been updated ? Did you provide further documentation ?
  is present or referenced. Please provide your references.
• The following questions are addressed in the documentation*: Developers (what did you do?, how can it be maintained?), For users (how to use your work?), For admins (how to install and configure your work?)
• For documentation: Please write or update the Readme in the current working directory!

Checks by code reviewer(s):

• Is the code clean of development artifacts e.g., unnecessary comments, prints, ...
• The ticket goals for each associated issue are reached or problems are clearly addressed (i.e., a new issue was introduced).
• There are appropriate unit tests and they pass.
• The git history is clean and linearized for the merge request.
• Coverage report for new code is acceptable.

closes #211

[codecov-commenter]

Codecov Report

Merging #221 (0cbf5e6) into main (089a7e0) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #221   +/-   ##
=======================================
  Coverage   91.23%   91.23%           
=======================================
  Files          77       77           
  Lines        4721     4721           
=======================================
  Hits         4307     4307           
  Misses        414      414           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 089a7e0...0cbf5e6. Read the comment docs.

[xsaschako]

The CI throws an FileNotFoundError Error in the RKI File. I don't think the axis=1 does this. Do you know why it throws that error?

Else, looks good!

[dabele]

The CI throws an FileNotFoundError Error in the RKI File. I don't think the axis=1 does this. Do you know why it throws that error?

May be the same error that is thrown in CI on the main branch?
https://github.com/DLR-SC/memilio/runs/5621535252?check_suite_focus=true

[xsaschako]

The CI throws an FileNotFoundError Error in the RKI File. I don't think the axis=1 does this. Do you know why it throws that error?

May be the same error that is thrown in CI on the main branch? https://github.com/DLR-SC/memilio/runs/5621535252?check_suite_focus=true

Looks like it. I will look into it ( maybe @annette-lutz we can discuss it tomorow morning.)

[annette-lutz]

The FileNotFoundError is thrown because the link to the data from RKI is outdated. That is the case for the main branch and this branch. This is corrected in pull request #216 where the source for the rki data is changed to github and the link failing here is changed to the current link and used as a fallback variant.

[dabele]

Don't forget to properly connect PRs to issues and add a line to the description of the PR that closes the issue, "Closes #" or similar.

[xsaschako]

Looks good!

[xsaschako]

Looks good!