Add explicit support of Python 3.14

[eduardo-rodrigues]

No description provided.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (f5c8190) to head (f9407a4).

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #282   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            7         7           
  Lines          339       339           
=========================================
  Hits           339       339           

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

[eduardo-rodrigues]

Hi @nsmith-, it's "interesting" that I simply updated Mypy to run on Python 3.10 and I get the following complaint in the Pint module:

mypy.....................................................................Failed
- hook id: mypy
- exit code: 1

src/hepunits/pint.py:41: error: Incompatible return value type (got "PlainUnit", expected "Unit")  [return-value]
src/hepunits/pint.py:95: error: Returning Any from function declared to return "Quantity"  [no-any-return]
Found 2 errors in 1 file (checked 8 source files)

I can make Mypy ignore it but wonder why this is, especially that I see the types involved being fine if I type the commands involved on the prompt, checking things out. Any idea?

[nsmith-]

Yeah, my IDE's linter also flagged that and as far as I could tell its a false positive. Probably a typing bug on pint's side.

[eduardo-rodrigues]

That makes sense. Indeed I could not reproduce it line-by-line, which is odd. Thanks a lot for the quick reply. I will proceed, then.