3 ms·
I would argue that one should never use '-O' it also strips doc strings from running code. Not really an `optimization` but they had do something right? One cou
by sitkack 10y ago
I would argue that one should never use '-O' it also strips doc strings from running code. Not really an `optimization` but they had do something right? One couldn't run __unoptimized__ in production could they?
- HerrMonnezza 10y ago> I would argue that one should never use '-O' it also strips doc strings from running code. Python `-OO` strips docstrings, `-O` basically only disables assertions. See: http://stackoverflow.com/a/4777156/459543 http://stackoverflow.com/a/4777156/459543
- vram22 10y ago>See: http://stackoverflow.com/a/4777156/459543 http://stackoverflow.com/a/4777156/459543 Or just do "python -h": -O : optimize generated bytecode slightly; also PYTHONOPTIMIZE=x -OO : remove doc-strings in addition to the -O optimizations Same on both Py 2 and 3.
- dfox 10y agoI assume that almost nobody uses -O in production.
- sitkack 10y agoProbably the same folks who don't test their code probably also remove their assertions in production.
- Twirrim 10y agoSo far as I've ever read, literally all -O does is strip asserts and docstrings. It doesn't really optimise anything.