You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,7 +68,7 @@ For developers interested in expanding `pymatgen` for their own purposes, we rec
68
68
69
69
Given that `pymatgen` is intended to be a long-term code base, we adopt very strict quality control and coding guidelines for all contributions to `pymatgen`. The following must be satisfied for your contributions to be accepted into `pymatgen`.
70
70
71
-
1. **Unit tests** are required for all new modules and methods. The only way to minimize code regression is to ensure that all code is welltested. Untested contributions will not be accepted.
71
+
1. **Unit tests** are required for all new modules and methods. The only way to minimize code regression is to ensure that all code is well-tested. Untested contributions will not be accepted.
72
72
1. **Python PEP 8** [code style](https://python.org/dev/peps/pep-0008). We allow a few exceptions when they are well-justified (e.g., Element's atomic number is given a variable name of capital Z, in line with accepted scientific convention), but generally, PEP 8 must be observed. Code style will be automatically checked for all PRs and must pass before any PR is merged. To aid you, you can install and run the same set of formatters and linters that will run in CI using
73
73
74
74
```sh
@@ -78,7 +78,7 @@ Given that `pymatgen` is intended to be a long-term code base, we adopt very str
78
78
pre-commit run --all-files # ensure your entire codebase passes linters
79
79
```
80
80
81
-
1. **Python 3**. We only support Python 3.8+.
81
+
1. **Python 3**. We only support Python 3.9+.
82
82
1. **Documentation** is required forall modules, classes and methods. In particular, the method doc strings should make clear the arguments expected and the return values. For complex algorithms (e.g., an Ewald summation), a summary of the algorithm should be provided and preferably with a link to a publication outlining the methodin detail.
83
83
84
84
For the above, ifin doubt, please refer to the core classes in`pymatgen`for examples of what is expected.
0 commit comments