René's URL Explorer Experiment

Title: Consider an architectural distinction between aspects inherent to a tool versus aspects varying by repo · Issue #1315 · usethis-python/usethis-python · GitHub

Open Graph Title: Consider an architectural distinction between aspects inherent to a tool versus aspects varying by repo · Issue #1315 · usethis-python/usethis-python

X Title: Consider an architectural distinction between aspects inherent to a tool versus aspects varying by repo · Issue #1315 · usethis-python/usethis-python

Description: There's an import cycle thing going on between coveragepy and pytest. Both use the presence of each other to modify their behaviour as tools when adding their config etc. But trying to break import cycles (#1311) will require a cleaner d...

Open Graph Description: There's an import cycle thing going on between coveragepy and pytest. Both use the presence of each other to modify their behaviour as tools when adding their config etc. But trying to break import...

X Description: There's an import cycle thing going on between coveragepy and pytest. Both use the presence of each other to modify their behaviour as tools when adding their config etc. But trying to break im...

Opengraph URL: https://github.com/usethis-python/usethis-python/issues/1315

X: @github

direct link

Domain: github.com

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Consider an architectural distinction between aspects inherent to a tool versus aspects varying by repo","articleBody":"There's an import cycle thing going on between coveragepy and pytest. Both use the presence of each other to modify their behaviour as tools when adding their config etc.\n\nBut trying to break import cycles (#1311) will require a cleaner dependency relationship. I've thought about the options but one to consider is to try and be more deliberate about keeping separate book-keeping for which class attributes of tools are allowed to read files/config etc. versus others which should never change (e.g. the name of the tool).\n\nPerhaps ToolMeta is needed, since it gives us the metadata about the tool. This would be an attribute of the tool itself.","author":{"url":"https://github.com/nathanjmcdougall","@type":"Person","name":"nathanjmcdougall"},"datePublished":"2026-02-25T08:12:34.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/1315/usethis-python/issues/1315"}

Links:

Viewport: width=device-width