← Back to issue list

Put public utility items in the top-level namespace

View original Github issue

Metadata

Project
craft-application
Number
#395
Type
issue
State
open
Author
lengau
Labels
—
Created
Updated
Closed
—

Current evaluation

Feature request to re-export public utility functions (e.g. get_host_architecture) in the top-level craft_application namespace. Unlabelled, 0 comments, no activity for ~15 months; not implemented in current code.

Suggested action: needs triage

Reason: The issue is unlabelled, has 0 comments, no assignee, and no maintainer interaction for 465 days, showing no sign of triage or prioritization. It is not a close_stale candidate because the request is still applicable — craft_application/__init__.py still does not re-export util items like get_host_architecture, and the repo remains active. A maintainer needs to decide whether to implement the re-exports or close it as not worth the API surface.

Impact: 25 Quick Win: 16.25 Staleness: 75 Complexity: 35 Confidence: 80 Support Request: 10

Issue body

### What needs to get done Instead of (for example): ```python from craft_application import util util.get_host_architecture() ``` we should be able to do: ```python import craft_application craft_application.get_host_architecture() ``` ### Why it needs to get done https://github.com/canonical/charmcraft/pull/1757#discussion_r1689937899

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 25
Quick Win: 16.25
Staleness: 75
Complexity: 35
Confidence: 80
Support Request: 10
needs triage Feature request to re-export public utility functions (e.g. get_host_architecture) in the top-level craft_application namespace. Unlabelled, 0 comments, no activity for ~15 months; not implemented in current code.
qwen/qwen3.6-35b-a3b
Staleness: 85
Complexity: 15
Confidence: 80
Support Request: 5
needs triage Proposes exposing public utility functions directly in the craft_application top-level namespace instead of requiring imports from the util submodule. Unlabelled and inactive for over two years with no maintainer response.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 10
Confidence: 75
Support Request: 0
close stale Request to expose utility functions directly in the craft_application top-level namespace instead of requiring the util submodule. Unlabelled and inactive for over a year with no maintainer comments.
qwen3.6-35b-a3b-mtp-q6
Staleness: 78
Complexity: 20
Confidence: 65
Support Request: 5
needs triage Moves public utility functions from submodules to the top-level package namespace for direct access. Currently open with no comments or recent activity. Awaiting triage and assignment.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/charmcraft#1757 (confidence 70%)

    Issue body cites a review discussion on this charmcraft PR as the motivation for exposing utils at the top level.

Related issues

No related issues found above the similarity threshold.