On Sun, Dec 5, 2010 at 9:47 PM, Stefan Behnel <[email protected]> wrote: > Ondrej Certik, 06.12.2010 02:42: >> Maybe we should create a StopOnFirstError >> exception, and then catch it and print "exiting the compilation due to >> --fatal-errors command line switch"? > > +1, although I'd name it AbortCompilation or something like that, maybe > SilentlyAbortCompilation.
We should trigger the exact same kind of abort that happens between (some) pipeline phases if there are any errors. This will trigger the necessary cleanup (e.g. a castrated C file), etc. I thought that's what I did, but I guess I only tested running cython manually (which didn't give a nasty traceback). While I'm thinking about this, I'd rather the flag be named --fast-fail, as errors are always fatal, it's just a question of timing. - Robert _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
