Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to 3.11 #100

Merged
merged 61 commits into from
Sep 30, 2024
Merged

Upgrade to 3.11 #100

merged 61 commits into from
Sep 30, 2024

Conversation

eculler
Copy link
Collaborator

@eculler eculler commented Jun 21, 2024

Earth Lab -- Pull Request Template

Welcome to the earth analytics python environment repo!

Before submitting a Pull Request please be sure to submit an issue that describes what the contents of the PR addresses.

IMPORTANT: Please do not use this repository as a practice activity to learn how to use GitHub! Only submit a PR after:

  1. Submitting an issue with a valid item that you wish to address in earthpy
  2. Getting approval from one of the maintainers to submit a formal PR.

Description

Please include a summary of the change and which issue is fixed. Be sure to reference the ISSUE that this PR addresses which should have been approved by an earthpy maintainer.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Test A
  • Test B

Checklist:

  • I have already submitted an issue and i was invited to submit a pr by an earthdatascience.org maintainer
  • 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
  • I have checked my code and corrected any misspellings

@eculler eculler changed the title Upgrade to 3.9 Upgrade to 3.11 Jun 21, 2024
@eculler eculler merged commit d414461 into main Sep 30, 2024
@eculler eculler deleted the upgrade-to-3.9 branch September 30, 2024 19:25
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.

3 participants