Skip to content

Commit

Permalink
Remove again pika/markdown from top level Pipfile
Browse files Browse the repository at this point in the history
The theory:
* 55b31b0 *really* fixes the issue that dependencies from the packages did not end up in the top level Pipfile.lock
* the Pipfile.lock *is* the ground truth currently for our python3-modules
* therefore, we should be able to reliable remove both package dependencies again from the Pipfile, they stay in the Pipfile.lock after locking
* however, we soon need to finish the transition to plain venv from bazel

Change-Id: Ic62034fd6bedd21c93e61d52872a4e6f48bfb046
JIRA-Ref: CMK-19819
  • Loading branch information
TimotheusBachinger committed Oct 25, 2024
1 parent 966ca38 commit 398f934
Show file tree
Hide file tree
Showing 4 changed files with 1,296 additions and 52 deletions.
2 changes: 0 additions & 2 deletions Pipfile
Original file line number Diff line number Diff line change
Expand Up @@ -90,8 +90,6 @@ uvicorn = "*"
webtest = "*" # used by WSGI based tests

[packages]
markdown = "*" # Should be in cmk-werks, see CMK-19819
pika = "*" # Should be in cmk-messaging, see CMK-19819
setuptools = "<=70.3.0" # See https://github.com/pypa/setuptools/issues/4487#issuecomment-2237487845 for context
setuptools-scm = "==4.1.2" # needed by various setup.py
six = "==1.16.0" # direct dependency + needed by python-dateutil, vcrpy, python-active-directory
Expand Down
Loading

0 comments on commit 398f934

Please sign in to comment.