Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

erroneous warnings with development versions of packages installed #393

Closed
tacaswell opened this issue Jul 11, 2024 · 1 comment · Fixed by #394
Closed

erroneous warnings with development versions of packages installed #393

tacaswell opened this issue Jul 11, 2024 · 1 comment · Fixed by #394
Labels

Comments

@tacaswell
Copy link

What pipdeptree version are you using?

2.23.0 or 2.23.1.dev6+g02f4f26

Are you running pipdeptree in a virtual environment?

Yes

Describe the problem

Development versions are not being correctly parsed. In a (probably ill advised) venv where most things are installed from the development branches I am seeing many warnings like:

@ pipdeptree --reverse -p six
Warning!!! Possibly conflicting dependencies found:
* aiohttp==4.0.0a2.dev0
 - frozenlist [required: >=1.1.1, installed: 1.4.2.dev0]
 - multidict [required: >=4.5,<7.0, installed: 6.0.6.dev0]
 - yarl [required: >=1.0,<2.0, installed: 1.9.5.dev0]
* aiohttp-jinja2==1.6
 - aiohttp [required: >=3.9.0, installed: 4.0.0a2.dev0]
* aiosignal==1.3.1
 - frozenlist [required: >=1.1.0, installed: 1.4.2.dev0]
* area-detector-handlers==0.0.10.post2.dev0+gf58ca85
 - pandas [required: Any, installed: 3.0.0.dev0+1025.gb4d40a2bf6]
* argon2-cffi-bindings==21.2.0
 - cffi [required: >=1.0.1, installed: 1.17.0.dev0]
* arrow==1.3.0
 - python-dateutil [required: >=2.7.0, installed: 2.9.0.post1.dev1+g0353b78]
* awkward==2.6.6
 - numpy [required: >=1.18.0, installed: 2.1.0.dev0]
* awkward-cpp==35
 - numpy [required: >=1.18.0, installed: 2.1.0.dev0]
* blosc2==3.0.0b1
 - numpy [required: >=1.23.0, installed: 2.1.0.dev0]
 - msgpack [required: Any, installed: 1.1.0rc1]
 - numexpr [required: Any, installed: 2.10.2.dev0]
[...it goes on for a couple of screens...]
@tacaswell tacaswell added bug tobeconfirmed To be confirmed after more investigation labels Jul 11, 2024
@kemzeb
Copy link
Collaborator

kemzeb commented Jul 11, 2024

Yep, I can confirm this. I'll make a fix as soon as possible.

@kemzeb kemzeb removed the tobeconfirmed To be confirmed after more investigation label Jul 11, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants