Skip to content

Conversation

@hmgaudecker
Copy link
Member

No description provided.

hmgaudecker and others added 13 commits January 11, 2026 11:16
Type-promoting aggregators (e.g., summing bools returns int) may give
incorrect results with same-type target inference.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Verify that:
- aggregator_return_type is ignored when set_annotations=False
- No inference or warnings occur when set_annotations=False

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@codecov
Copy link

codecov bot commented Jan 16, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.57%. Comparing base (f56a4a8) to head (b933f86).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #65   +/-   ##
=======================================
  Coverage   95.57%   95.57%           
=======================================
  Files          23       23           
  Lines        1174     1174           
=======================================
  Hits         1122     1122           
  Misses         52       52           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@review-notebook-app
Copy link

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

@hmgaudecker hmgaudecker requested review from janosg and timmens January 17, 2026 07:01
@hmgaudecker
Copy link
Member Author

@timmens @janosg

I much prefer the JB-based version over the Sphinx-based one. Differences:

  • I improved the usage patterns page a bit in the JB version
  • No API docs in JB. My view: Nobody looks at them online anymore, all introspection in the editor / asking AI)

But no big deal if we went back to #63

@janosg
Copy link
Member

janosg commented Jan 17, 2026

Switching to Jupyterbook is ok and the new page does look better. However, I would keep the API docs in. It's almost zero cost to have it and I do use online API docs sometimes.

Does Jupyterbook have a good way of producing an llms.txt? If we touch the docs this would be the right time to add it.

@hmgaudecker
Copy link
Member Author

Is it okay to postpone API docs until this one is there? jupyter-book/mystmd#1259

Would much prefer that over using Sphinx for now and then porting. Writing native MyST is so much nicer!

Copy link
Member

@timmens timmens left a comment

Choose a reason for hiding this comment

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

I don't have the capacity to give you a detailed review right now (still sick), but I think switching to JB is nice. I do share Janos view that having the API docs online is nice, but as long as this is an "open issue" that will be tackled in the future I would be okay with this PR as is. In optimagic we build the llms.txt file automatically using sphinx-llms. I am not sure how yours was build but automating this could be an improvement.

@hmgaudecker hmgaudecker changed the base branch from buid-docs-using-pixi to main January 22, 2026 13:59
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.

4 participants