> Thus, I'm hereby proposing that we change this in Py3k so that Python's > debug mode does not mandate any ABI change anymore.
It seems people still debate what it is that you *actually* want. This sentence suggests Christian's interpretation, i.e. you might be unaware that the debug mode not only adds debug symbols, but also changes the layout of objects. That is *very* useful, and should not be dropped. > This means that a > programmer will be able to mixmatch release-mode extensions and compile- > mode extensions, thus getting debuggability only of those extensions he > really cares. Whereas this suggests Phillip's interpretation, i.e. you merely want debug symbols on a single DLL. You can get that today - just enable debug information for your extension module, and the compiler will emit the PDB files you need for debugging. > If people agree on this goal, I'm willing to actually implement it in the > Python core (there must be a change in the logic through which "_d" > extensions are picked up since they would become optional rather than > required) and everywhere else it might be needed (eg: distutils). See above. Don't drop what Python calls the debug mode. Instead, just learn to build your extension with debugging, for Python's release mode. Regards, Martin _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
