-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #78 from pysat/rc0.0.5
RC v0.0.5
- Loading branch information
Showing
31 changed files
with
1,472 additions
and
829 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,6 +5,11 @@ Bug reports, feature suggestions and other contributions are greatly | |
appreciated! pysat and pysatSpaceWeather are community-driven projects and | ||
welcomes both feedback and contributions. | ||
|
||
Come join us on Slack! An invitation to the pysat workspace is available | ||
in the 'About' section of the | ||
[pysat GitHub Repository.](https://github.com/pysat/pysat) | ||
Development meetings are generally held fortnightly. | ||
|
||
Short version | ||
------------- | ||
|
||
|
@@ -40,17 +45,26 @@ Development | |
|
||
To set up `pysatSpaceWeather` for local development: | ||
|
||
1. `Fork pysatSpaceWeather on GitHub <https://github.com/pysat/pysatSpaceWeather/fork>`_. | ||
2. Clone your fork locally:: | ||
1. [Fork pysatSpaceWeather on GitHub](https://github.com/pysat/pysatSpaceWeather/fork>). | ||
|
||
2. Clone your fork locally: | ||
|
||
``` | ||
git clone [email protected]:your_name_here/pysatSpaceWeather.git | ||
``` | ||
|
||
3. Create a branch for local development:: | ||
3. Create a branch for local development: | ||
|
||
``` | ||
git checkout -b name-of-your-bugfix-or-feature | ||
``` | ||
|
||
Now you can make your changes locally. Tests for new instruments are | ||
performed automatically. Tests for custom functions should be added to the | ||
performed automatically. See discussion | ||
[here](https://pysat.readthedocs.io/en/main/new_instrument.html#testing-support) | ||
for more information on triggering these standard tests. | ||
|
||
Tests for custom functions should be added to the | ||
appropriately named file in ``pysatSpaceWeather/tests``. For example, | ||
space weather methods should be named | ||
``pysatSpaceWeather/tests/test_methods_sw.py``. If no test file exists, | ||
|
@@ -59,20 +73,28 @@ To set up `pysatSpaceWeather` for local development: | |
must begin with ``Test``, and test methods must also begin with ``test``. | ||
|
||
4. When you're done making changes, run all the checks to ensure that nothing | ||
is broken on your local system:: | ||
is broken on your local system: | ||
|
||
``` | ||
pytest -vs pysatSpaceWeather | ||
``` | ||
|
||
5. Update/add documentation (in ``docs``). Even if you don't think it's | ||
relevant, check to see if any existing examples have changed. | ||
|
||
6. Add your name to the .zenodo.json file as an author | ||
|
||
7. Commit your changes and push your branch to GitHub:: | ||
7. Commit your changes and push your branch to GitHub: | ||
|
||
``` | ||
git add . | ||
git commit -m "Brief description of your changes" | ||
git commit -m "CODE: Brief description of your changes" | ||
git push origin name-of-your-bugfix-or-feature | ||
``` | ||
|
||
Where CODE is a standard shorthand for the type of change (eg, BUG or DOC). | ||
`pysat` follows the [numpy development workflow](https://numpy.org/doc/stable/dev/development_workflow.html), | ||
see the discussion there for a full list of this shorthand notation. | ||
|
||
8. Submit a pull request through the GitHub website. Pull requests should be | ||
made to the ``develop`` branch. | ||
|
@@ -87,8 +109,8 @@ For merging, you should: | |
|
||
1. Include an example for use | ||
2. Add a note to ``CHANGELOG.md`` about the changes | ||
3. Ensure that all checks passed (current checks include Travis-CI | ||
and Coveralls) [1]_ | ||
3. Ensure that all checks passed (current checks include GitHub Actions, | ||
Coveralls, and ReadTheDocs) [1]_ | ||
|
||
.. [1] If you don't have all the necessary Python versions available locally or | ||
have trouble building all the testing environments, you can rely on | ||
|
@@ -118,6 +140,8 @@ These include: | |
* `import numpy as np` | ||
* `import pandas as pds` | ||
* `import xarray as xr` | ||
* When incrementing a timestamp, use `dt.timedelta` instead of `pds.DateOffset` | ||
when possible to reduce program runtime | ||
* All classes should have `__repr__` and `__str__` functions | ||
* Docstrings use `Note` instead of `Notes` | ||
* Try to avoid creating a try/except statement where except passes | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.