This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author francismb
Recipients eric.smith, francismb, ncoghlan, terry.reedy
Date 2012-02-18.12:10:54
SpamBayes Score 1.0443912e-10
Marked as misclassified No
Message-id <1329567057.92.0.757840371062.issue13579@psf.upfronthosting.co.za>
In-reply-to
Content
Updated. The NEWS line is now at the top of the section.

>As near as I can tell, the two change block beginning with 
>+In less formal terms,
>[...]
>are strictly re-wrapping and no text changes. Correct?

Yes. Just a pydev question here: I now this re-wrapping
adds noise to the patch, but can/should be done?

Please correct me if I'm wrong: one should try to
limit the line width to 80. If one word starts before
and ends behind is not bad but new words should start
in a new line.

Now in the devguide states “To perform a quick sanity check on your path, you can run make patchcheck”

I did that (I'm using the mq approach here) but I get no useful information (AFAIN):
-----------------------------------------------
Modules/Setup.dist is newer than Modules/Setup;
check to make sure you have all the updates you
need in your Modules/Setup file.
Usually, copying Modules/Setup.dist to Modules/Setup will work.
-----------------------------------------------
./python ./Tools/scripts/patchcheck.py
Getting the list of files that have been added/changed ... 0 files
Fixing whitespace ... 0 files
Fixing C file whitespace ... 0 files
Fixing docs whitespace ... 0 files
Docs modified ... NO
Misc/ACKS updated ... NO
Misc/NEWS updated ... NO


Thanks in advance !
History
Date User Action Args
2012-02-18 12:10:58francismbsetrecipients: + francismb, terry.reedy, ncoghlan, eric.smith
2012-02-18 12:10:57francismbsetmessageid: <1329567057.92.0.757840371062.issue13579@psf.upfronthosting.co.za>
2012-02-18 12:10:57francismblinkissue13579 messages
2012-02-18 12:10:56francismbcreate