[ python-Bugs-1093173 ] distutils/tests not installed

SourceForge.net noreply at sourceforge.net
Thu Dec 30 15:11:55 CET 2004


Bugs item #1093173, was opened at 2004-12-30 10:43
Message generated for change (Comment added) made by loewis
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1093173&group_id=5470

Category: Python Library
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Submitted By: Armin Rigo (arigo)
Assigned to: Nobody/Anonymous (nobody)
Summary: distutils/tests not installed

Initial Comment:
The new subdirectory distutils/tests is not copied to
the installation location by a 'make install'.  This
causes test_distutils to crash when run from an
installed path (as opposed to from a CVS check-out).

I could propose a patch (Makefile.pre.in) given some
bash syntax learning efforts  -- for example,
distutils/tests shouldn't be installed if we want a
no-test installation.

This raises the question about why distutils/tests
isn't actually called test/distutils...

----------------------------------------------------------------------

>Comment By: Martin v. Löwis (loewis)
Date: 2004-12-30 15:11

Message:
Logged In: YES 
user_id=21627

Please do try to come up with a patch.

I'm not sure I understand the no-test business - there is no
no-test installation AFAICT; adding it to LIBSUBDIRS might
be sufficient. The Windows installer
has the notion of no-test installs; it did always package
distutils/tests, but now also conditionalizes installation
on the selection of the testsuite.

As for choice of location of the tests: both bsddb and email
have their own test directories, both because they contain a
large number of tests, and because they are both packaged
independently of Python. The same could be said about distutils.

As for the choice of name: it is called "test" in all other
cases, only "tests" for distutils. This is unfortunate, but
changing directories in CVS does more harm than good.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1093173&group_id=5470


More information about the Python-bugs-list mailing list