Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2011-February/107859.html below:

[Python-Dev] devguide: Generate patches without code checkout (Was: devguide: Write a guide to committing a patch.)

• Previous message: [Python-Dev] devguide: Generate patches without code checkout (Was: devguide: Write a guide to committing a patch.)
• Next message: [Python-Dev] [Python-checkins] devguide: Add a document discussing the development cycle typically followed for
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Wed, Feb 2, 2011 at 10:33 AM, anatoly techtonik <techtonik at gmail.com> wrote:
> How about patches sent by users who track and fix bugs directly in
> codebase of their Python installation?

While I don't personally endorse the above approach, if you're going
to develop inside your installed site-packages folder it seems like a
good idea to at least version control that code by running "hg init"
or similar in the site-packages folder. Then you can create diffs
against older versions using "hg diff".

If one is going to do something crazy one might as well go the whole
hog I guess. :)

Schiavo
Simon

• Previous message: [Python-Dev] devguide: Generate patches without code checkout (Was: devguide: Write a guide to committing a patch.)
• Next message: [Python-Dev] [Python-checkins] devguide: Add a document discussing the development cycle typically followed for
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4