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 ralph.corderoy
Recipients ralph.corderoy
Date 2008-09-02.13:34:08
SpamBayes Score 6.809499e-07
Marked as misclassified No
Message-id <1220362449.51.0.882466438238.issue3758@psf.upfronthosting.co.za>
In-reply-to
Content
A new target, "check", has been added to Makefile for 2.6.  It runs some
tests on the source code that are intended to check there's nothing
wrong before preparing a patch. 
http://svn.python.org/view/python/trunk/Makefile.pre.in?rev=61528&view=markup

Unfortunately, GNU coding standards have cemented in many people's minds
that "check" is the target for self-tests, e.g. "make clean all check
install".  http://www.gnu.org/prep/standards/standards.html#Standard-Targets

I realise Python doesn't fall under those coding standards, but none the
less it is confusing to people to re-use a standard target name for a
different use.  In the past, Python had no "check" target so people
spotted their mistake, investigated, and found the "test" target.

Please consider renaming this new "check" target, e.g. to "prepatch", to
avoid this confusion when 2.6 is released.  Perhaps a "check" target can
be added as a synonym for "test" at the same time?
History
Date User Action Args
2008-09-02 13:34:09ralph.corderoysetrecipients: + ralph.corderoy
2008-09-02 13:34:09ralph.corderoysetmessageid: <1220362449.51.0.882466438238.issue3758@psf.upfronthosting.co.za>
2008-09-02 13:34:08ralph.corderoylinkissue3758 messages
2008-09-02 13:34:08ralph.corderoycreate