devguide
devguide copied to clipboard
The Python developer's guide
In python-dev mailing list, it was asked what to do when a PR will address multiple issues. https://mail.python.org/archives/list/[email protected]/thread/74FS2DW2L4MDJXRREAABXYRWNI6INMBA/ From few answers from the core devs, seems like we prefer keeping...
Update this page, https://devguide.python.org/langchanges/, to add mention of a sponsor for a PEP. - [ ] Refer to PEP 1 [discussion of sponsor](https://github.com/python/peps/blob/master/pep-0001.txt#L160) - [ ] The intent is to...
Hello everyboy! I am not sure if here is the appropriate place to this issue. Sorry if not. On gitbootcamp.rst there is a recommendation to made easy the creation of...
Hi, Sometimes, I can read `python` or `python3` in the documentation and in the devguide. Maybe we could take a decision and indicate which term we should use for the...
I think the Devguide is due for some reorganization after the migration. In particular: * [x] [The version control setup section](https://devguide.python.org/getting-started/setup-building/#version-control-setup) should link to a separate "git" page (either the...
The workflow for merging PRs in the Github interface and triggering backports, is very straightforward, but it would be useful to document it for core developers unfamiliar with it (as...
In /coverage/ section 5.2.1.1 When installing coverage on Windows, the second command step can not be used: `source ../cpython-venv/bin/activate` Instead, there should probably be some mention of the proper step:...
I'm not sure how we'd structure this, but I realised that the principle of "Escalate tracker disagreements to python-ideas and python-dev discussions, and potentially all the way to the PEP...
Moved from http://bugs.python.org/issue18041