Skip to content

Conversation

@jagerber48
Copy link
Contributor

  • Closes # (insert issue number)
  • Executed pre-commit run --all-files with no errors
  • The change is fully covered by automated unit tests
  • Documented in docs/ as appropriate
  • Added an entry to the CHANGES file

I created this PR so that the CI will run for the main branch. Our plan is to release version 4.0.0 from the main branch so there is actually not a technical need to merge main into master. I would be happy with not doing so.

jagerber48 added 11 commits May 20, 2025 21:36
- [ ] Closes # (insert issue number)
- [ ] Executed `pre-commit run --all-files` with no errors
- [ ] The change is fully covered by automated unit tests
- [ ] Documented in docs/ as appropriate
- [ ] Added an entry to the CHANGES file
- [ ] Closes # (insert issue number)
- [ ] Executed `pre-commit run --all-files` with no errors
- [ ] The change is fully covered by automated unit tests
- [ ] Documented in docs/ as appropriate
- [ ] Added an entry to the CHANGES file

NOTE!!!! This PR targets `main`, not `master`. This PR will be released
in version `4.x` (likely `4.0.0`).

This PR eliminates functions, methods, and their corresponding tests
that were deprecated in version 3.2.3:
https://github.com/lmfit/uncertainties/releases/tag/3.2.3.
- [ ] Closes # (insert issue number)
- [ ] Executed `pre-commit run --all-files` with no errors
- [ ] The change is fully covered by automated unit tests
- [ ] Documented in docs/ as appropriate
- [ ] Added an entry to the CHANGES file

This PR targets `main`, not `master`.
- [ ] Closes # (insert issue number)
- [ ] Executed `pre-commit run --all-files` with no errors
- [ ] The change is fully covered by automated unit tests
- [ ] Documented in docs/ as appropriate
- [ ] Added an entry to the CHANGES file
- [ ] Closes # (insert issue number)
- [ ] Executed `pre-commit run --all-files` with no errors
- [ ] The change is fully covered by automated unit tests
- [ ] Documented in docs/ as appropriate
- [ ] Added an entry to the CHANGES file
- [ ] Closes # (insert issue number)
- [ ] Executed `pre-commit run --all-files` with no errors
- [ ] The change is fully covered by automated unit tests
- [ ] Documented in docs/ as appropriate
- [x] Added an entry to the CHANGES file

Get rid of the custom `NegativeStdDev` exception. This exception case is
covered by `ValueError`. i.e., the caller is passing in an invalid value
for the `std_dev` input.
@codecov
Copy link

codecov bot commented Jun 16, 2025

Codecov Report

❌ Patch coverage is 62.71186% with 22 lines in your changes missing coverage. Please review.
✅ Project coverage is 86.75%. Comparing base (f1b7e4f) to head (2c30134).
⚠️ Report is 9 commits behind head on master.

Files with missing lines Patch % Lines
tests/test_unumpy.py 0.00% 20 Missing ⚠️
tests/test_ulinalg.py 0.00% 2 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #333      +/-   ##
==========================================
- Coverage   86.81%   86.75%   -0.07%     
==========================================
  Files          18       18              
  Lines        1919     1706     -213     
==========================================
- Hits         1666     1480     -186     
+ Misses        253      226      -27     
Flag Coverage Δ
macos-latest-3.10 94.05% <100.00%> (-1.58%) ⬇️
macos-latest-3.11 94.05% <100.00%> (-1.58%) ⬇️
macos-latest-3.12 94.05% <100.00%> (-1.58%) ⬇️
macos-latest-3.8 94.05% <100.00%> (-1.58%) ⬇️
macos-latest-3.9 94.05% <100.00%> (-1.58%) ⬇️
no-numpy 82.64% <47.45%> (+0.73%) ⬆️
ubuntu-latest-3.10 94.05% <100.00%> (-1.58%) ⬇️
ubuntu-latest-3.11 94.05% <100.00%> (-1.58%) ⬇️
ubuntu-latest-3.12 94.05% <100.00%> (-1.58%) ⬇️
ubuntu-latest-3.8 94.05% <100.00%> (-1.58%) ⬇️
ubuntu-latest-3.9 94.05% <100.00%> (-1.58%) ⬇️
windows-latest-3.10 94.05% <100.00%> (-1.58%) ⬇️
windows-latest-3.11 94.05% <100.00%> (-1.58%) ⬇️
windows-latest-3.12 94.05% <100.00%> (-1.58%) ⬇️
windows-latest-3.8 94.05% <100.00%> (-1.58%) ⬇️
windows-latest-3.9 94.05% <100.00%> (-1.58%) ⬇️

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.

@codspeed-hq
Copy link

codspeed-hq bot commented Jun 16, 2025

CodSpeed Performance Report

Merging #333 will not alter performance

Comparing main (2c30134) with main (53ac376)

🎉 Hooray! pytest-codspeed just leveled up to 4.0.0!

A heads-up, this is a breaking change and it might affect your current performance baseline a bit. But here's the exciting part - it's packed with new, cool features and promises improved result stability 🥳!
Curious about what's new? Visit our releases page to delve into all the awesome details about this new version.

Summary

✅ 5 untouched benchmarks

- [ ] Closes # (insert issue number)
- [ ] Executed `pre-commit run --all-files` with no errors
- [ ] The change is fully covered by automated unit tests
- [ ] Documented in docs/ as appropriate
- [ ] Added an entry to the CHANGES file

This PR removes all usages of `np.matrix` from the source code and
tests.
- [ ] Closes # (insert issue number)
- [ ] Executed `pre-commit run --all-files` with no errors
- [ ] The change is fully covered by automated unit tests
- [ ] Documented in docs/ as appropriate
- [ ] Added an entry to the CHANGES file

Right now the tests raise many warnings about `std_dev=0` not being
supported. I am eliminating the tests that raise those warnings.
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.

2 participants