Skip to content

More core features#7

Merged
pattertj merged 10 commits intomainfrom
more-features
Nov 12, 2025
Merged

More core features#7
pattertj merged 10 commits intomainfrom
more-features

Conversation

@pattertj
Copy link
Copy Markdown
Owner

No description provided.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment thread quantalytics/__init__.py
Comment on lines 3 to +9
# 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"]
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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 👍 / 👎.

@pattertj pattertj merged commit e64815a into main Nov 12, 2025
8 checks passed
@pattertj pattertj deleted the more-features branch November 12, 2025 19:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant