> Why not put in it -O instead? Then -O means lose asserts and lose fine-grained tracebacks, while -OO continues to also strip out doc strings.
What if someone wants to keep asserts but do not want the extra data? On Sat, 8 May 2021 at 22:05, Ethan Furman <et...@stoneleaf.us> wrote: > On 5/8/21 1:31 PM, Pablo Galindo Salgado wrote: > >> We can't piggy back on -OO as the only way to disable this, it needs to > >> have an option of its own. -OO is unusable as code that relies on > "doc" > >> strings as application data such as http://www.dabeaz.com/ply/ply.html > >> exists. > > > > -OO is the only sensible way to disable the data. There are two things > to disable: > > > > * The data in pyc files > > * Printing the exception highlighting > > Why not put in it -O instead? Then -O means lose asserts and lose > fine-grained tracebacks, while -OO continues to also > strip out doc strings. > > -- > ~Ethan~ > _______________________________________________ > 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/BEE4BGUZHXBTVDPOW5R4DC3S463XC3EJ/ > Code of Conduct: http://python.org/psf/codeofconduct/ >
_______________________________________________ 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/WK4KXZPOSWYMI3C5AILQCEYVZRCDFL7N/ Code of Conduct: http://python.org/psf/codeofconduct/
