NOTICE: This library is no longer being developed. Use Ensaio instead (https://www.fatiando.org/ensaio). -- Download geophysical models/datasets and load them in Python
BSD 3-Clause "New" or "Revised" License
34
stars
15
forks
source link
Use only first year of publication in the copyright notice #97
[ ] 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.
[ ] If adding new example, please build the docs with make -C doc gallery and push the changes made on doc/gallery. Continuous Integration services build and deploy the docs, but they won't run the examples.
[ ] 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.
Reminders for Maintainers:
[ ] Maintainers must run all tests locally before the PR is merged. CIs run only minimal tests and styling checks.
Inspired on fatiando/verde#296
Related to fatiando/maintenance#9
Reminders:
make formatandmake checkto make sure the code follows the style guide.doc/api/index.rstand the base__init__.pyfile for the package.make -C doc galleryand push the changes made ondoc/gallery. Continuous Integration services build and deploy the docs, but they won't run the examples.AUTHORS.mdfile (if you haven't already) in case you'd like to be listed as an author on the Zenodo archive of the next release.Reminders for Maintainers: