Skip to content

Add python3.14 and update other dependencies - #162

Open
aburrell wants to merge 24 commits into
developfrom
maint_add_python3.14
Open

aburrell wants to merge 24 commits into
developfrom
maint_add_python3.14

Conversation

@aburrell

@aburrell aburrell commented Apr 3, 2026 •

Copy link
Copy Markdown
Contributor

Description

Addresses PyHC PHEP 3 needs, as well as updates to GitHub Actions and other dependency deprectations.

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • This change requires a documentation update

How Has This Been Tested?

Unit tests

Test Configuration

  • Operating system: OS X Tahoe
  • Version number: Python 3.10
  • Any details about your local setup that are relevant

Checklist:

  • Make sure you are merging into the develop (not main) branch
  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • Add a note to CHANGELOG.md, summarizing the changes

If this is a release PR, replace the first item of the above checklist with the
release checklist on the pysat wiki:
https://github.com/pysat/pysat/wiki/Checklist-for-Release

aburrell added 17 commits April 3, 2026 11:25
Updated the old pysat requirement to the current standard.
Switched from the vaporwear `m2r2` package to `myst_parser` for including markdown files in the docs.
Updated links and labels to avoid duplicates.
Cycled python support to 3.10-3.14.
Raised the minimum supported version to 3.10.
No longer need the version number in the setup.cfg file.
Updated the checkout and python GitHub Actions versions, and added testing for 3.14.
Added a summary of changes to the changelog.
Updated GFZ links to their new locations.
Updated the contributor covenant links.
The fork link no longer works, so linked to the GitHub fork instructions instead.
Updated an outstanding GFZ link.
Added Zenodo to the lists of sites to ignore when link testing.
SWPC changed the filename of the 45 day Ap and F10.7 forecast again.
Updated the GFZ links in the data access.
Renamed the SWPC 45-day forecast file to match the remote repository.
Added more changes to the changelog.
@aburrell

aburrell commented Apr 3, 2026

Copy link
Copy Markdown
Contributor Author

Requires an update to pysat for 3.11+ tests to pass.

@aburrell aburrell added this to the 0.2.3 milestone Apr 3, 2026
@rstoneback

Copy link
Copy Markdown
Collaborator

Hmmm.... code tests aren't being run for some reason. There were a whole bunch of tests here.

@rstoneback

Copy link
Copy Markdown
Collaborator

Made some progress. Tests are running again. The filename issue has been fixed. There is a data access issue that popped up and may be related to actual changes in pysat's data access stuff as part of the latest release.

@rstoneback

rstoneback commented Oct 3, 2026 •

Copy link
Copy Markdown
Collaborator

So the problem was a change in pandas 3.0. Anyway, I have a potential fix for the remaining error. I'm not exactly certain what the test really wants. However, pandas no longer likes:

        assert len(kp_inst['Kp'][kp_inst['Kp']]
                   == self.combine['fill_val']) > 0

And forcing that to a integer lookup and the test passes.

        assert len(kp_inst['Kp'].iloc[kp_inst['Kp']]
                   == self.combine['fill_val']) > 0

The issue is, so we are accessing data, and doing a comparison, but everything is wrapped in a length check. So the data check isn't very specific.

Looking at the outputs from the check, inside the length check, we get:

2019-03-20 21:00:00    False
2019-03-20 21:00:00    False
2019-03-20 21:00:00    False
2019-03-20 21:00:00    False
2019-03-20 21:00:00    False
                       ...  
2019-02-16 06:00:00     True
2019-02-16 06:00:00     True
2019-02-16 09:00:00     True
2019-02-16 06:00:00     True
2019-02-16 06:00:00     True
Name: Kp, Length: 264, dtype: bool

There isn't a single specific value that should result. This output comes from running the tests on pandas < 3.0 . I get the same output when running pandas >= 3.0. Best I can tell so far, the addition of .iloc is a valid change.

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