Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| # Organize the public surface into focused namespaces so consumers | ||
| # access helpers via `quantalytics.metrics`, `quantalytics.stats`, `quantalytics.charts`, and `quantalytics.reports`. | ||
| # access helpers via `quantalytics.analytics`, `quantalytics.charts`, and `quantalytics.reports`. | ||
| from . import analytics as analytics | ||
| from . import charts as charts | ||
| from . import metrics as metrics | ||
| from . import stats as stats | ||
| from . import reporting as reports | ||
|
|
||
| __all__ = ["metrics", "stats", "charts", "reports"] | ||
| __all__ = ["analytics", "charts", "reports"] |
There was a problem hiding this comment.
Removing metrics/stats namespaces without shim breaks public API
The commit deletes the quantalytics.metrics and quantalytics.stats packages and drops their exports from the top-level module, leaving only the new analytics namespace. Any existing user code importing quantalytics.metrics or quantalytics.stats will now raise ModuleNotFoundError even though the project version only advances from 0.1.1 to 0.1.2. Unless the release is intentionally a breaking change, a thin compatibility module (or a deprecation shim) is needed to avoid silently breaking all consumers that rely on the previous import path.
Useful? React with 👍 / 👎.
No description provided.