behavior when failing to build an extension?
What's the intended behavior if an extension fails to build? Should it print an error message and continue, or should it stop? (On the Mac distutils currently stops, which is kindof a nuisance, so I'm tempted to "fix" it...) Just
Just van Rossum <just@letterror.com> writes:
What's the intended behavior if an extension fails to build? Should it print an error message and continue, or should it stop? (On the Mac distutils currently stops, which is kindof a nuisance, so I'm tempted to "fix" it...)
I think distutils should print an error and stop by default. That way users trying to build an extension immediately know that something went wrong. A command line option to make distutils try to go on if an error occurs might be useful, though, as long a clear message that an error occurred and the commands weren't completed successfully is printed at the end. Bernhard -- Intevation GmbH http://intevation.de/ Sketch http://sketch.sourceforge.net/ MapIt! http://mapit.de/
Just van Rossum <just@letterror.com> writes:
Bernhard Herzog wrote:
I think distutils should print an error and stop by default. That way users trying to build an extension immediately know that something went wrong.
Is that what happens under Unix?
Yes, distutils stops with a message along the lines of error: command 'gcc' failed with exit status 1 That's also what e.g. make does by default, unless you run it with the -k flag. Bernhard -- Intevation GmbH http://intevation.de/ Sketch http://sketch.sourceforge.net/ MapIt! http://mapit.de/
participants (2)
-
Bernhard Herzog -
Just van Rossum