Skip to content

Conversation

@VeckoTheGecko
Copy link
Contributor

@VeckoTheGecko VeckoTheGecko commented Aug 15, 2024

Implement SPEC 0 (fixes #1657).

  • Drop support for Python 3.8 and 3.9
  • Adapt workflows to accept python-version param, and update matrix
  • Update installation instructions mentioning min Python version
  • Update zips (flagged by Bugbear B905)
  • Update conda feedstock recipe
  • Set min versions for packages
    • Xarray has CI tooling to flag whether the recorded min version is outdated according to SPEC 0, not sure if we want to go that far though. Thoughts @erikvansebille? Should just be a matter of copying a script across and setting it to run twice a year. Why not I guess, just a matter of deciding what core packages count as (xarray, zarr, pandas, numpy?). Wouldn't mind leaving this for a future PR. Getting the current changes into master allows me to work with python 3.10 features (re. typing) next week

- Drop support for Python 3.8 and 3.9
- Adapt workflows to accept python-version param, and update matrix
- Update installation.rst with min Python version
Prior behaviour didn't require x and y to be same length. PEP618 in Python 3.10 introduced strict flag. True raises ValueError if x and y aren't same length.

Setting values here based on intuition. This was flagged by Bugbear in Ruff checks (B905)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Python and code package version support (SPEC 0)

3 participants