Skip to content

Conversation

@atztogo
Copy link
Collaborator

@atztogo atztogo commented Dec 22, 2025

How about this?

Fix #624

@atztogo atztogo requested a review from LecrisUT December 22, 2025 06:45
@codecov
Copy link

codecov bot commented Dec 22, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.05%. Comparing base (e02be02) to head (717cf5e).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #627   +/-   ##
========================================
  Coverage    74.05%   74.05%           
========================================
  Files           27       27           
  Lines         8018     8018           
  Branches      1646     1643    -3     
========================================
  Hits          5938     5938           
  Misses        1603     1603           
  Partials       477      477           
Flag Coverage Δ
c_api 69.45% <ø> (ø)
fortran_api 52.96% <ø> (ø)
python_api 67.18% <ø> (ø)
unit_tests 11.68% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ 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.

# Python API exceptions

This feature is available starting in v2.7. To enable it, add the following
snippet to your code:
Copy link
Collaborator

@LecrisUT LecrisUT Dec 22, 2025

Choose a reason for hiding this comment

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

The wording of the "to enable it" makes it sound like it will be a more permanent feature, which I hope it will not, that's why I put a note about it in the docstring instead as "currently it's an opt-in"

How about the part below this in the docstring inside that note?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I could not grasp the nuance of that English since I am not good at English.

How about the part below this in the docstring inside that note?

I don't see what you mean.

Could you change as you think the best?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Ok, updated the documentation with some of the hints you suggested. Also proposing to release 2.8.0 where we switch the default relatively quick so the users would not have to wait to opt-in the exception feature. They could just lock the dependency at 2.7 if they cannot update quickly. But for now having it a bit noisy should help with the visibility that they need to update these, and we can make 2.7.1 release silencing the warning if needed.

Wdyt?

@LecrisUT LecrisUT requested a review from lan496 December 23, 2025 14:15
Signed-off-by: Cristian Le <git@lecris.dev>
@LecrisUT LecrisUT force-pushed the pyspglib-exception-doc branch from 474a264 to bfa1c89 Compare December 23, 2025 14:26
Signed-off-by: Cristian Le <git@lecris.dev>
Signed-off-by: Cristian Le <git@lecris.dev>
Signed-off-by: Cristian Le <git@lecris.dev>
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.

Documentation for OLD_ERROR_HANDLING

2 participants