[TIP] Are extensions needed for coverage required?
Chris Withers
chris at simplistix.co.uk
Sun Jul 1 08:40:10 PDT 2012
Hi Ned,
Thanks for the quick response!
(CC'ing Enthought support in case it's something to do with EPD 7.2-2)
On 01/07/2012 16:34, Ned Batchelder wrote:
> Chris: coverage.py works by setting a trace function with
> sys.settrace(). That function is invoked for every line of your
> program. To reduce the burden, coverage.py has a trace function written
> in C. If for whatever reason you can't compile that C extension,
> coverage.py will fall back to a Python implementation, which is what
> happened here to you. Everything will continue to work, but it will be
> slower.
Okay, so sounds like I'd like the C extension, but the problem is more
general, I've had the same error trying to compile some other C
extensions on Mac OS X:
>> /Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/unicodeobject.h:4,
>>
>> from
>> /Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/Python.h:85,
>>
>> from coverage/tracer.c:3:
>> /Developer/SDKs/MacOSX10.6.sdk/usr/include/stdarg.h:4:25: error:
>> stdarg.h: No such file or directory
Anyone seen this and/or know how to fix it?
cheers,
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
More information about the testing-in-python
mailing list