On Wed, Aug 13, 2008 at 17:24 +0200, Ralf Schmitt wrote: > On Wed, Aug 13, 2008 at 8:21 AM, holger krekel <[EMAIL PROTECTED]> wrote: > > > > > sure but in any case i don't want to change this going from 0.9.1 to 0.9.2. > > ack. > > > > > I think i'd like to have a flag that turns automatic > > compilation on or off. A setup.py installed release > > should have this flag off so that no automatic > > installation occurs. > > I've implemented this in http://systemexit.de/repo/py-setup/rev/4e18f70b985d. > The flag used here is the existence of greenlet.c in > py/c-extensions/greenlet/.
ok, i'll check this. another thing with setuptools: the way that py.test is installed as a console script modifies the py lib lookup: py/bin/py.test usually looks for a py lib upwards from where you invokve it (the curdir) with the help of _findpy.py. this is important at least for pypy and when you are using py.test to work on the py lib itself. Do you have an idea how to preserve this logic with setuptools? Specifying a module import path probably does not work because then there is no chance anymore to influence which py lib gets loaded. holger _______________________________________________ py-dev mailing list py-dev@codespeak.net http://codespeak.net/mailman/listinfo/py-dev
