Andreas Maier
Andreas Maier
I think this PR only fails due to the current failures on Python 3.5 and 3.6 (issue #374).
I have the same error. In a virtualenv with Python 3.10, and pipdeptree 2.13.0 installed in the virtualenv: ``` $ pip list | grep -E "pip|python-jsonschema" pip 23.2.1 pipdeptree 2.13.0...
This old and unresolved problem caused me some extra hours of work today, because I simply did not remember it. I finally provided a fix for it in PR #2028.
Does anyone know whether any of the 20 forks of this repo released anything?
@pradyunsg Sure, if it helps. I was not aware that it causes all these entries here in the PR.
Fixed in PR #375
> could 3.5/3.6 dropped from supported? Not as far as our projects are concerned, because we still need to support Python 3.5 and 3.6, and we urgently need a solution...
I created issue #376 for the tox failure on Python 3.6, but think that this PR successfully addresses the issue it intended to fix, namely to run Python 3.5 and...
> could 3.5/3.6 dropped from supported? Not as far as our projects are concerned, because we still need to support Python 3.5 and 3.6, and we urgently need a solution...
@adamtheturtle We are NOT having indirect dependencies in the requirements.txt file and thus also not in the package on Pypi. Where we have indirect dependencies is in a minimum-constraints.txt file...