Open oheger-bosch opened 1 year ago
@oheger-bosch Excellent catch! we should also use simpler way to state a version (e.g. using the actual fully dotted version)
Hi @pombredanne, have you already thought about this, maybe even worked on an implementation/solution? FYI: @oheger-bosch
@kerstin-bosch I have looked into the details but no fix yet. This is a couple days of work.
Hi @pombredanne Do you have any updates for us? Is the fix already implemented?
We have a
requirements.txt
file that cannot be analyzed by Python Inspector due to conflicting dependencies. It boils down to the following two dependencies:When running the command
python-inspector -r requirements.txt --json-pdt - -o linux -p 36
it reportsWhen choosing a different Python version, e.g.
37
the problem is caused by thedataclasses
library (see full stack trace below).From what I found out, there seem to be only specific Python versions for which this constellation can work: dataclasses requires Python >=3.6, <3.7; anyio requires Python >=3.6.2. It is, however, not possible to define the Python version for Python Inspector on that level of detail. I assume that the
36
option will select a 3.6.0 version? So, should the corresponding option be extended to support an exact version number? Or is there another way how to solve this issue?Here is the full stack trace: