On Tue, Jan 06, 2009 at 03:02:36PM -0800, Christopher Lee wrote: -> You may also want to look at issue 51 in the tracker as another minor -> problem related to the test framework. -> http://code.google.com/p/pygr/issues/detail?id=51
(Issue #51 refers to a problem with the sys.path munging that ensures that the in-development version of pygr is run, rather than whatever version is installed.) It looks like Istvan's patch drops the whole sys.path munging issue. The problem with this is that if you *don't* add the pygr development directory (pygr/, if build_ext -i is used, or build/lib.*, if not) then you might be running the tests against a different pygr -- basically whatever comes first in sys.path or PYTHONPATH. This causes two kinds of problems: - the common problem is that people forget to set PYTHONPATH to their dev version & run the tests against the system-installed version; - a less common problem is that people using easy_install and eggs *cannot* always override the default sys.path settings with PYTHONPATH. This happened to me several times; I think it has to do with the way import is changed by setuptools. The second problem cannot easily be fixed without adding code into the tests. The first problem is likely to be a big stumbling block for new hackers and an infrequent but annoying problem for the rest of us. That's why I added it into the test framework. cheers, --titus -- C. Titus Brown, [email protected] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
