Contribute¶
Python-guide is under active development, and contributors are welcome.
If you have a feature request, suggestion, or bug report, please open a newissue onGitHub. To submit patches, please send a pull request onGitHub.Once your changes get merged back in, you’ll automatically be added to theContributors List.
Style Guide¶
For all contributions, please follow theThe Guide Style Guide.
Todo List¶
If you’d like to contribute, there’s plenty to do. Here’s a shorttodo list.
- Establish “use this” vs “alternatives are....” recommendations
Todo
Write about Blueprint
(Theoriginal entry is located in /home/docs/checkouts/readthedocs.org/user_builds/python-guide-fil/checkouts/latest/docs/scenarios/admin.rst, line 371.)
Todo
Fill in “Freezing Your Code” stub
(Theoriginal entry is located in /home/docs/checkouts/readthedocs.org/user_builds/python-guide-fil/checkouts/latest/docs/shipping/freezing.rst, line 39.)
Todo
Include code examples of exemplary code from each of the projects listed. Explain why it is excellent code. Use complex examples.
(Theoriginal entry is located in /home/docs/checkouts/readthedocs.org/user_builds/python-guide-fil/checkouts/latest/docs/writing/reading.rst, line 59.)
Todo
Explain techniques to rapidly identify data structures, algorithms and determine what the code is doing.
(Theoriginal entry is located in /home/docs/checkouts/readthedocs.org/user_builds/python-guide-fil/checkouts/latest/docs/writing/reading.rst, line 61.)
