Hi Ralf, On Mon, Aug 04, 2008 at 11:01 +0200, Ralf Schmitt wrote: > On Mon, Aug 4, 2008 at 10:41 AM, holger krekel <[EMAIL PROTECTED]> wrote: > > > > > ok, but this requires a C-compiler on the client side. > > The thing i don't know much about is how to best provide eggs > > with pre-compiled c-extensions. > > > > ahh. ok. But you really shouldn't remove the c code... > python setup.py bdist_wininst will create a binary installer suitable > for windows. > In case you use setuptools python setup.py bdist_egg would build an egg. > But I guess then the problem is that your setup.py does not even > compile the c-extensions when it's run? > What about removing some magic and using a standard setup.py?
that's a good idea, i think. Actually i'd like to have a (generated or manually written for now) setup.py that plays along nicely with setuptools. Maybe it'S good if it also works without setuptools? What do you think about starting a branch (based on release/0.9.x) to get it towards such a state? cheers, holger -- collaborative expert contracting: http://merlinux.eu PyPy Python/Compiler tool chain: http://codespeak.net/pypy pylib py.test/greenlets/svn APIs: http://pylib.org _______________________________________________ py-dev mailing list py-dev@codespeak.net http://codespeak.net/mailman/listinfo/py-dev
