Python Devguide

Settings | Report Duplicate

2

I Use This!

Moderate Activity

Commits : Listings

Analyzed about 4 hours ago. based on code collected 1 day ago.

Commit Message	Contributor	Files Modified	Lines Added	Lines Removed	Code Location	Date
Sep 03, 2025 — Sep 03, 2026 Showing page 67 of 77 Search / Filter on:
Mention that the FAQ can be read at any point. This isn't greatly integrated to the preceding paragraph, so improvements welcome!	Antoine Pitrou	More...				over 15 years ago
Move the section about applying patches to the FAQ (it's not really part of the patch creation lifecycle).	Antoine Pitrou	More...				over 15 years ago
Re-add anchor.	Antoine Pitrou	More...				over 15 years ago
Tweak wording and subsections	Antoine Pitrou	More...				over 15 years ago
Comment out the "make patchcheck" advice, since it doesn't work for a non-SVN workflow.	Antoine Pitrou	More...				over 15 years ago
Merge from default	Antoine Pitrou	More...				over 15 years ago
Add some punctuation.	Georg Brandl	More...				over 15 years ago
Merge from default	Brett Cannon	More...				over 15 years ago
Drop the version number; docs are at final and now a living document.	Brett Cannon	More...				over 15 years ago
Fill in some gaps as found at the doc guide at python.org/dev/ (so the latter can simply redirect to here).	Brett Cannon	More...				over 15 years ago
Update the setup instuctions to be more hg-y and less svn-y.	Brett Cannon	More...				over 15 years ago
Mention using 'patch' for svn patches.	Brett Cannon	More...				over 15 years ago
Fix a silly statement.	Brett Cannon	More...				over 15 years ago
clarification	Brett Cannon	More...				over 15 years ago
Note that porting instructions might need to be updated if non-core developers don't go the 'patch' route.	Brett Cannon	More...				over 15 years ago
Mention that using mq is totally optional and a more svn-like approach is feasible.	Brett Cannon	More...				over 15 years ago
Use the term 'core developer' instead of 'committer'.	Brett Cannon	More...				over 15 years ago
Move to using mq for basic usage.	Brett Cannon	More...				over 15 years ago
More clarifications: use the term 'working copy' and mention 'hg update'.	Brett Cannon	More...				over 15 years ago
Fix wording: it is not automation. Also, there's a probably a problem if there's nothing to rebase, since collapsing then won't be done; so using rebase is not a strong suggestion.	Antoine Pitrou	More...				over 15 years ago
Try to present the constraints more clearly	Antoine Pitrou	More...				over 15 years ago
Use Mercurial's full name	Antoine Pitrou	More...				over 15 years ago
Suggest rebasing to compress local commits into a single remote commit.	Brett Cannon	More...				over 15 years ago
grammatical fix	Brett Cannon	More...				over 15 years ago
Try to explain the two most common approaches to hg workflow: feature clones and mq.	Brett Cannon	More...				over 15 years ago
Tweak in patch block/revert.	Brett Cannon	More...				over 15 years ago
Denote the changes in forward-porting changes between feature clones and working in a single clone.	Brett Cannon	More...				over 15 years ago
Try to explain how to port changes.	Brett Cannon	More...				over 15 years ago
Two things: (1) explain how to switch between branches so people don't end up branching off of their own branches constantly, and (2) mention that using named branches for everything is more for non-committers, else we would end up with a ton of named branches in the main repo.	Brett Cannon	More...				over 15 years ago
Merge	Antoine Pitrou	More...				over 15 years ago

←
1
2
…
63
64
65
66
67
68
69
70
71
…
76
77
→