On Wed, Aug 13, 2008 at 00:13 +0200, Ralf Schmitt wrote: > On Tue, Aug 12, 2008 at 9:16 PM, holger krekel <[EMAIL PROTECTED]> wrote: > > Hi Ralf, > > > > On Mon, Aug 04, 2008 at 16:11 +0200, Ralf Schmitt wrote: > >> On Mon, Aug 4, 2008 at 3:48 PM, holger krekel <[EMAIL PROTECTED]> wrote: > >> > I don't have a strong opinion on this. But for python 2.3 and > >> > 2.4 i guess it's somewhat nice to be able to type "python setup.py > >> > install" > >> > and have it work indepedently from the question if > >> > setuptools is installed. > >> > > >> > >> setuptools enabled packages come with a short bootstrap module which > >> does install setuptools in case it is not installed. This should also > >> work with python 2.3. > >> (I think you will also need vs 6.0 instead of vs 2003 to build > >> extensions for python 2.3 on windows) > > > > ok. if we want to ship with a pre-compiled greenlet module > > we would need to distribute per-python versions, right? > > yes. > > > If we can't manage this ourselves then i hope we can > > find people to prepare binary eggs. > > yes, for mac and windows only I guess. This would be another good > reason to split the greenlet module from the other code. You wouldn't > have to build new binary packages as long as only some python code got > changed..
sure but in any case i don't want to change this going from 0.9.1 to 0.9.2. > >> > originally the greenlet lib was moved into the py lib > >> > to ease maintenance and because it was used in PyPy and > >> > we didn't want to add dependencies there. > >> > > >> > Today, I'd be fine both ways - for 0.9.2 i guess > >> > greenlets should still be part of the py lib, though. > >> > > >> > >> ok. I'll try to implement a setuptools based setup.py then. > > > > any chances you'll get to that this week? I think i'd > > like to get the 0.9.2 release out the coming weekend. > > > > http://systemexit.de/repo/py-setup/ contains a mercurial repository > with a setup.py using setuptools. > The setup.py itself currently can be viewed here: > http://systemexit.de/repo/py-setup/file/tip/setup.py > > It currently only installs a py.test as a script (everything else from > py/bin/ is missing). > It installs the greenlet module under the name greenlet. > py.magic.greenlet should be adapted accordingly. > (You still want to compile it on the fly???). Something like 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. > try: > import greenlet > except ImportError: > try_compile() > > should work.. > > You can build a source distribution with > python setup.py build sdist > and a binary egg with > python setup.py build bdist_egg is it usual to do binary eggs for linux/osx? > When doing development you can run python setup.py develop in order to > use the source files in place. > > ez_setup.py has been downloaded from > http://peak.telecommunity.com/dist/ez_setup.py > The MANIFEST.in file should not be needed as setuptools would handle > that automatically for a subversion repository. ah, it looks at all the files that are versioned? thanks for the work, btw! holger _______________________________________________ py-dev mailing list py-dev@codespeak.net http://codespeak.net/mailman/listinfo/py-dev
