[Python-Dev] deprecating .pyo and -O (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Thu Jun 14 15:23:34 CEST 2012
- Previous message: [Python-Dev] deprecating .pyo and -O
- Next message: [Python-Dev] deprecating .pyo and -O
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, 14 Jun 2012 09:14:59 -0400 "R. David Murray" <rdmurray at bitdance.com> wrote:
What does matter though is the memory savings. I'm working with an application where the difference between normal and -OO is around a 10% savings (about 2MB) in program DATA size at startup, and that makes a difference for an ap running in a memory constrained environment. A docstring stripper would enable the bulk of that savings,
Probably indeed.
but it is still nice to be able to omit code (such as debug logging statements) as well.
But does that justify all the additional complication in the core interpreter, as well as potential user confusion?
Regards
Antoine.
- Previous message: [Python-Dev] deprecating .pyo and -O
- Next message: [Python-Dev] deprecating .pyo and -O
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]