[Python-Dev] the history of tests being inside Lib/ in Python (original) (raw)
Ned Deily nad at acm.org
Sat Jul 30 05:48:44 CEST 2011
- Previous message: [Python-Dev] the history of tests being inside Lib/ in Python
- Next message: [Python-Dev] the history of tests being inside Lib/ in Python
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
In article <CAF-Rda-M5QL3bhzAcf2d=0U94Qdr_-u_KVPRai9HWZkHTKhUCg at mail.gmail.com>, Eli Bendersky <eliben at gmail.com> wrote:
* The tests usually aren't even installed. The user can run them during installation, but once it goes through, tests are not copied into /usr/whatever...
That's not true across the board. For instance, the python.org Mac OS X installers do install the tests "permanently" and, with the addition of the "-m test" (or "-m test.regrtest" in 2.7) command line options, the tests can be easily run at any time on the end user's system. That's one of the reasons why it is important that additions and changes to the tests need to ensure that auxiliary directories and files are installed by the Makefile install targets and not just resident in the build directory.
-- Ned Deily, nad at acm.org
- Previous message: [Python-Dev] the history of tests being inside Lib/ in Python
- Next message: [Python-Dev] the history of tests being inside Lib/ in Python
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]