Put public utility items in the top-level namespace
Metadata
Current evaluation
Public helpers such as get_host_architecture should be re-exported from craft_application directly; current code still exposes them only through craft_application.util.
Suggested action: needs triage
Reason: The requested API form is explicit, and util.__all__ provides a concrete candidate set, but the issue has no labels, comments, or maintainer triage. craft_application.__init__ still omits every utility name, so the request is unresolved; implementation should confirm the supported re-export set, preserve util compatibility, and add API tests.
Evaluated by: mr-cal-bot
Impact:
34
Quick Win:
18
Complexity:
31
Confidence:
94
Actionability:
76
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 |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
34
Quick Win:
18
Complexity:
31
Confidence:
94
Actionability:
76
|
needs triage | Public helpers such as get_host_architecture should be re-exported from craft_application directly; current code still exposes them only through craft_application.util. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
19
Complexity:
20
Confidence:
70
Actionability:
80
|
needs triage | Expose utility functions like get_host_architecture at the top-level craft_application namespace for convenience. | |
| qwen/qwen3.8-27b |
Impact:
25
Quick Win:
16
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. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/charmcraft#1757
(confidence 99%)
The issue explicitly cites the review discussion in PR 1757 as the motivation.
Related issues
No related issues found above the similarity threshold.