Contribute

https://farm3.staticflickr.com/2858/33573769116_49c1ef51e7_k_d.jpg

Python-guide is under active development, and contributors are welcome.

If you have a feature request, suggestion, or bug report, please open a new issue on GitHub. To submit patches, please send a pull request on GitHub. Once your changes get merged back in, you’ll automatically be added to the Contributors List.

Style Guide

For all contributions, please follow the The Guide Style Guide.

Todo List

If you’d like to contribute, there’s plenty to do. Here’s a short todo list.

  • Establish “use this” vs “alternatives are....” recommendations

Por hacer

Write about Blueprint

(El entrada original se encuentra en /home/docs/checkouts/readthedocs.org/user_builds/python-guide-es/checkouts/latest/docs/scenarios/admin.rst, en la línea 371.)

Por hacer

Fill in “Freezing Your Code” stub

(El entrada original se encuentra en /home/docs/checkouts/readthedocs.org/user_builds/python-guide-es/checkouts/latest/docs/shipping/freezing.rst, en la línea 39.)

Por hacer

Include code examples of exemplary code from each of the projects listed. Explain why it is excellent code. Use complex examples.

(El entrada original se encuentra en /home/docs/checkouts/readthedocs.org/user_builds/python-guide-es/checkouts/latest/docs/writing/reading.rst, en la línea 59.)

Por hacer

Explain techniques to rapidly identify data structures, algorithms and determine what the code is doing.

(El entrada original se encuentra en /home/docs/checkouts/readthedocs.org/user_builds/python-guide-es/checkouts/latest/docs/writing/reading.rst, en la línea 61.)