Skip to content

feat(packaging): publish optax with py.typed marker - #1750

Closed
erensh27 wants to merge 1 commit into
google-deepmind:mainfrom
erensh27:feature/publish-py-typed
Closed

feat(packaging): publish optax with py.typed marker#1750
erensh27 wants to merge 1 commit into
google-deepmind:mainfrom
erensh27:feature/publish-py-typed

Conversation

@erensh27

@erensh27 erensh27 commented Aug 9, 2026

Copy link
Copy Markdown

Implements #1388: publish optax with a py.typed marker so PEP 561-compliant type checkers (mypy default, pyright, etc.) treat import optax as typed instead of falling back to Any.

  • Adds optax/py.typed (empty marker; the flit backend ships all files inside the module directory, so no package-data config change is needed).
  • Adds the Typing :: Typed trove classifier that packaging ecosystems show in metadata.

No behavior change; builds reproduce the same sdist/wheel plus the marker.

optax is almost fully annotated, so tools like mypy benefit from
declaring the package as typed. Adds the empty py.typed marker (flit
ships all files in the package dir) and the 'Typing :: Typed' classifier
so PEP 561 consumers do not treat every optax import as untyped.
@google-cla

google-cla Bot commented Aug 9, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@erensh27 erensh27 closed this Aug 10, 2026
@erensh27
erensh27 deleted the feature/publish-py-typed branch August 10, 2026 03:15
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