On Tue, 19 May 2009 20:21:10 -0700 "C. Titus Brown" <c...@msu.edu> wrote:
> There's another issue, which is that we don't want a top-level > directory called 'tests' made available. If I understand you > correctly, the end result of either situation is that > > import tests > > would import the pygr tests, on a system-wide level. This doesn't feel like too big an issue to me... Istvan's comment on the lack of __init__ in tests/ aside, that would only happened if someone imported Pygr from the source package AND had built in in-place mode (i.e. with sys.path pointing at the top-level directory of the source package). Feels like a lot of conditions to meet, perhaps we could simply assume that if someone tries to use Pygr in such an advanced way he knows what he's doing. > I think we should consider moving the tests under the pygr directory, > then include them in the installation, [...] While in principle a sound idea, haven't we decided we wanted the tests to be confined to source packages to avoid possible issues with cross-version testing? > > 1. I do not know yet how to have setuptools query Pyrex for its > version > You can use pkg_resources, which comes with setuptools; see my commit, Nice! I've merged your commit into my branch, then extended it a bit so that if Pyrex is not found, setup tries to use pre-built C files. -- MS --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to pygr-dev@googlegroups.com To unsubscribe from this group, send email to pygr-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
