Today almost nobody runs the debug version -- I suspect mostly because it's slower. On Windows it's awkward to setup cygwin for most users just to do a build. On Mac you also have to install the developer disks, which some people don't want to do. Then you have to wait forever while the build runs -- or fails like it did over the weekend. If we make everyone jump over all these hurdles to run the debug version, even fewer people will run it and we'll miss bugs. Instead, I think we need to make the debug version easier to run (and not too slow), not harder to run.
I hardly ever run the debug version not because it is too hard but because I don't see the need. The only time I do, is when I want python built with --with-pydebug turned on to help me debug C memory bugs I introduce when I use the python C api.
As for running a debug version if Chandler, it is as easy as: - checkout chandler sources - make DEBUG=1 install You do not need to do a full debug build to run a debug build. Andi.. _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
