[py-dev] py.test and editors (Re: [issue57] Emacs and py.test tracebacks)

Ralf Schmitt schmir at gmail.com
Mon Aug 4 11:01:40 CEST 2008


On Mon, Aug 4, 2008 at 10:41 AM, holger krekel <holger at merlinux.eu> 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?

Regards,
- Ralf



More information about the Pytest-dev mailing list