Greg Roodt

@Faqa Thanks for your input. Agree that in an ideal world, the full transitive dependency graph for all python runtimes of the user's monorepo would be materialised ahead of time...

@Faqa Can you please create a repro for the situation you describe? If you're generating platform specific lockfiles, then the situation you describe sounds like a bug. I'm not sure...

This comes up from time to time. Isn't python packaging "fun". 😂 Setuptools "scripts" have been replaced by entry_points in setuptools and it's generally only legacy or old packages that...

Which version of ansible are you using? It seems they migrated to entry_points in October 2021 https://github.com/ansible/ansible/pull/76021 Maybe they've just missed that entry_point and a small upstream PR could be...

@f0rmiga for early review before opening up to other maintainers.

Any further comments @f0rmiga ?

> Will users run into a problem with passing uncompiled requirements to pip_parse? Do you get an error if your requirements.txt just contains "pep8" or something? Yes, folks will get...

> So its almost certain a requirements.txt that was used with pip_install won't work with pip_parse, if pip_install is an alias of pip_parse. Can you explain what you mean? This...

> a fully-pinned requirements.txt that only has top level distributions Got it. Do you expect those to be common? It's quite unlikely those individuals will have a good bazel experience...

Is the suggestion you are making @hrfuller to rather NOT try to reuse the existing requirements.txt (even though many will be transitively locked)? I can get behind that. I don't...