[issue9583] PYTHONOPTIMIZE = 0 is not honored

2010-09-20 Thread Terry J. Reedy
Terry J. Reedy added the comment: I am following the suggestion in the last sentence of the original post and turning this into a doc issue. I believe it is standard that command-line switches override environmental variables when there is a conflict, but 'Using Python', section 1.2. 'Environ

[issue9583] PYTHONOPTIMIZE = 0 is not honored

2010-09-20 Thread Buck Golemon
Buck Golemon added the comment: Minimal demo: $ setenv PYTHONOPTIMIZE 0 $ python3.1 -OO -c "print(__debug__)" False I've used this code to get the desired functionality: if [[ $TESTING == 1 || ${PYTHONOPTIMIZE-2} =~ '^(0*|)$' ]]; then #someone is requesting no optimization export -n

[issue9583] PYTHONOPTIMIZE = 0 is not honored

2010-09-20 Thread Éric Araujo
Changes by Éric Araujo : -- versions: +Python 3.1 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue9583] PYTHONOPTIMIZE = 0 is not honored

2010-08-15 Thread Terry J. Reedy
Terry J. Reedy added the comment: How did you conclude that PYTHONOPTIMIZE = 0 is not honored? Can you provide a minimal example or demonstration. In any case, 2.6.6 is nearly out so bad behavior needs to be demonstrated with 2.7/3.x. -- nosy: +terry.reedy versions: +Python 2.7, Pyth

[issue9583] PYTHONOPTIMIZE = 0 is not honored

2010-08-12 Thread Buck Golemon
New submission from Buck Golemon : In our environment, we have a wrapper which enables optimization by default (-OO). Most commandline tools which have a mode-changing flag such as this, also have a flag to do the opposite ( see: ls -t -U, wget -nv -v, ). I'd like to implement one or both of: