You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In addition to the options to publish the graph based on module paths and including third-party deps
mentioned in #13431, publishing a --detailed graph would be great! It would allow people to build or
conceive of several other tools on top of ruff, and also allow ruff to swallow them up.
This could include information like:
whether this is from a string or not
if it could go so deep as to being able to detect whether it's being mocked, dynamically imported,
opened as a pkg resource, etc, that would be absolutely nuts
whether this is a top-level import or not
whether private members are imported (I guess this starts pushing the graph towards being not
just for modules but for module members)
whether it's a relative import
any attached annotations (particularly pylint, also semgrep)
I understand there would be some non-trivial restructure or reconsideration, since there could be multiple
dependencies on the same module with differing characteristics
The text was updated successfully, but these errors were encountered:
In addition to the options to publish the graph based on module paths and including third-party deps
mentioned in #13431, publishing a
--detailed
graph would be great! It would allow people to build orconceive of several other tools on top of ruff, and also allow ruff to swallow them up.
This could include information like:
opened as a pkg resource, etc, that would be absolutely nuts
just for modules but for module members)
I understand there would be some non-trivial restructure or reconsideration, since there could be multiple
dependencies on the same module with differing characteristics
The text was updated successfully, but these errors were encountered: