Paul Topley
Paul Topley
This is nothing short of a poor design choice. I have been working around this on the resolver side for a sizable graphql api, now hit by the same issue...
I have also noticed the same behaviour with option `--use-default-kwarg`
I have a fix for this, but I am struggling to get tests to pass locally. tests/test_main.py::test_enable_version_header always fails, with the following error `importlib.metadata.PackageNotFoundError: No package metadata was found for...
> Thank for found bug! I will check your problem in tests soon Did you happen to get anywhere with this?
I think what nfx is after (and I also) is to be able to get the full dependency tree for all packages defined in a given requirements.txt file.