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
- have all dependencies in pyproject.toml only
- remove requirements.txt files and tox.ini
- adapt contributing guide for documentation creation
- fix some dockerfile warnings
We welcome any contributions that help to improve pyfakefs for the community.
4
+
We welcome any contributions that help to improve `pyfakefs` for the community.
5
5
Contributions may include bug reports, bug fixes, new features, infrastructure enhancements, or
6
6
documentation updates.
7
7
8
8
## How to contribute
9
9
10
10
### Reporting Bugs
11
11
12
-
If you think you found a bug in pyfakefs, you can [create an issue](https://help.github.com/articles/creating-an-issue/).
12
+
If you think you found a bug in `pyfakefs`, you can [create an issue](https://help.github.com/articles/creating-an-issue/).
13
13
Before filing the bug, please check, if it still exists in the [main branch](https://github.com/pytest-dev/pyfakefs).
14
14
If you can reproduce the problem, please provide enough information so that it can be reproduced by other developers.
15
15
This includes:
@@ -21,9 +21,9 @@ For better readability, you may use [markdown code formatting](https://help.gith
21
21
22
22
### Proposing Enhancements
23
23
24
-
If you need a specific feature that is not implemented, or have an idea for the next
25
-
exciting gimmick in pyfakefs, you can also create a respective issue.
26
-
Of course - implementing it yourself is the best chance to get it done!
24
+
If you need a specific feature that is not implemented, or have an idea for a useful addition,
25
+
you may also create a respective issue.
26
+
As usually, implementing it yourself is the best chance to get it done!
27
27
The next item has some information on doing this.
28
28
29
29
### Contributing Code
@@ -34,25 +34,33 @@ develop on a feature branch, and [create a pull request](https://help.github.com
34
34
There are a few things to consider for contributing code:
35
35
* We ensure the [PEP-8 coding style](https://www.python.org/dev/peps/pep-0008/)
36
36
by using [black](https://pypi.org/project/black/) auto-format in a
37
-
pre-commit hook; you can locally install
38
-
[pre-commit](https://pypi.org/project/pre-commit/) to run the linter
39
-
tests on check-in or on demand (`pre-commit run --all-files`)
40
-
* Use the [Google documentation style](https://google.github.io/styleguide/pyguide.html) to document new public classes or methods
41
-
* Provide unit tests for bug fixes or new functionality - check the existing tests for examples
42
-
* Provide meaningful commit messages - it is ok to amend the commits to improve the comments
43
-
* Check that the automatic GitHub Action CI tests all pass for your pull request
44
-
* Be ready to adapt your changes after a code review
37
+
pre-commit hook. We recommend to locally install
38
+
[pre-commit](https://pypi.org/project/pre-commit/)(`pre-commit install`) to run the linter
39
+
tests on check-in, or run the tests on demand (`pre-commit run --all-files`).
40
+
* Use the [Google documentation style](https://google.github.io/styleguide/pyguide.html) to document new public classes or methods.
41
+
* Provide unit tests for bug fixes or new functionality - check the existing tests for examples.
42
+
* Provide meaningful commit messages - it is ok to amend the commits to improve the comments.
43
+
* Check that the automatic GitHub Action CI tests all pass for your pull request.
44
+
* Be ready to adapt your changes after a code review.
45
45
46
46
### Contributing Documentation
47
47
48
48
If you want to improve the existing documentation, you can do this also using a pull request.
49
49
You can contribute to:
50
50
* the source code documentation using [Google documentation style](https://google.github.io/styleguide/pyguide.html)
51
51
* the [README](https://github.com/pytest-dev/pyfakefs/blob/main/README.md) using [markdown syntax](https://help.github.com/articles/basic-writing-and-formatting-syntax/)
52
-
* the documentation published on [Read the Docs](https://pytest-pyfakefs.readthedocs.io/en/latest/),
53
-
located in the `docs` directory (call `make html` from that directory).
54
-
For building the documentation, you will need [sphinx](http://sphinx.pocoo.org/).
0 commit comments