Include Python 3.11 in test suite

[namurphy]

This PR makes two changes to tox.ini in preparation for a v0.1.0 release:

• Add a test for Python 3.11 to the test suite
• Change the Python 3.9 test to windows-latest

Because PlasmaPy depends on Numba (at least for now), and fiasco depends on PlasmaPy, it'll be necessary to wait until Numba works on Python 3.11.

[codecov-commenter]

Codecov Report

Base: 86.90% // Head: 86.90% // No change to project coverage 👍

Coverage data is based on head (45f0612) compared to base (7c118eb).
Patch has no changes to coverable lines.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #176   +/-   ##
=======================================
  Coverage   86.90%   86.90%           
=======================================
  Files          22       22           
  Lines        1802     1802           
=======================================
  Hits         1566     1566           
  Misses        236      236           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[wtbarnes]

Hmm it seems there are issues with both the Windows and 3.11 tests:

• Windows test failure is because when reading the fiasco rc file, it is expected that the $HOME environment variable exists which is probably bad practice in general. Perhaps we could take a more general approach to reading this configuration file?
• The 3.11 failure is because numba is being picked up as a dependency but numba is not yet compatible with 3.11. However, I'm not sure why numba is getting picked up as a dependency at all. It is not an explicit dependency of fiasco.

[namurphy]

Windows test failure is because when reading the fiasco rc file, it is expected that the $HOME environment variable exists which is probably bad practice in general. Perhaps we could take a more general approach to reading this configuration file?

Agreed! I'll raise an issue on this.

The 3.11 failure is because numba is being picked up as a dependency but numba is not yet compatible with 3.11. However, I'm not sure why numba is getting picked up as a dependency at all. It is not an explicit dependency of fiasco.

That's PlasmaPy's fault here, since we have Numba as a requirement. I've been dreaming of dropping it because of how long it takes for Numba to get released after a few Python version. Hopefully before next year!

[wtbarnes]

Ah gotcha. I didn't realize it had been picked up as a dependency in plasmapy. Is there room to make it an optional dependency?

[namurphy]

Ah gotcha. I didn't realize it had been picked up as a dependency in plasmapy. Is there room to make it an optional dependency?

We use it within some of our formulary functions, so we'd have to do some rewriting to make it optional. My own preference would be to cythonize the numba out of everything so that we drop it as a dependency entirely.

[namurphy]

Just downscoped this to remove the tests for Windows, which are going to be covered in a separate PR (see also #179).

And still waiting for Numba to work on Python 3.11...

downscope ← my new favorite word

[wtbarnes]

This is superseded by #245