> > The cost I'm concerned about is the runtime cost of worse code, because > > the compiler can't perform some optimizations due the constraints of > > providing the extended debug information.
Python does have an Optimized mode (-O). Granted, it’s not used very often, but this would be a good use case for it. -CHB > Aah thanks for clarifying, I see what you mean now. In cases like this > where the compiler is making optimizations, I think it is perfectly > fine to just elide the column information. While it would be nice to > maintain accurate columns wherever possible, you shouldn't constrain > improvements and optimizations based on it. The traceback machinery > will simply not print out the carets in that case and everything > should just work smoothly. > _______________________________________________ > Python-Dev mailing list -- python-dev@python.org > To unsubscribe send an email to python-dev-le...@python.org > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/python-dev@python.org/message/EB24LA7L5C35QHQTFLB6QZX26E77O6QM/ > Code of Conduct: http://python.org/psf/codeofconduct/ > -- Christopher Barker, PhD (Chris) Python Language Consulting - Teaching - Scientific Software Development - Desktop GUI and Web Development - wxPython, numpy, scipy, Cython
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/GBAJSME7P7D6FS4NDCFCJRSJXN6LIYZK/ Code of Conduct: http://python.org/psf/codeofconduct/
