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

Run CIs only on the two ends of supported Python versions #256

Merged
merged 1 commit into from
Oct 19, 2021

Conversation

santisoler
Copy link
Member

Instead of running the test suite on CIs over each supported Python version,
limit it only to the two ends. Currently, they are Python 3.6 and Python 3.9.

Suggested by @leouieda on #240

Reminders:

  • Run make format and make check to make sure the code follows the style guide.
  • Add tests for new features or tests that would have caught the bug that you're fixing.
  • Add new public functions/methods/classes to doc/api/index.rst and the base __init__.py file for the package.
  • Write detailed docstrings for all functions/classes/methods. It often helps to design better code if you write the docstrings first.
  • If adding new functionality, add an example to the docstring, gallery, and/or tutorials.
  • Add your full name, affiliation, and ORCID (optional) to the AUTHORS.md file (if you haven't already) in case you'd like to be listed as an author on the Zenodo archive of the next release.

@santisoler santisoler merged commit 7bf4e2a into master Oct 19, 2021
@santisoler santisoler deleted the ci-python-versions branch October 19, 2021 17:03
@santisoler santisoler added the maintenance A maintenance task to improve development label Oct 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance A maintenance task to improve development
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant