This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author techtonik
Recipients techtonik
Date 2012-06-05.14:40:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1338907211.87.0.323271147876.issue15005@psf.upfronthosting.co.za>
In-reply-to
Content
This code dumps a lot of internal source code info when executed with trace as:

python -m trace --trace file2.py


---[file2.py]
import subprocess

def ret():
  output = subprocess.check_output(['hg', 'id', '-nib'])
  print( output )
  print( output )
  print( output.strip() )
  print( output.strip().split() )

ret()
---

Normally, the last line of the output is:
['e67793ec2995+', '2162+', 'default']

But during trace call it is:
['subprocess.py(1180):', '_dup2(errwrite,', '2)', '---', 'modulename:', 'subprocess,', 'funcname:', '_dup2', 'subprocess.py(1174):', 'if', 'a', '==', 'b:', 'subprocess.py(1176):', 'elif', 'a', 'is', 'not', 'None:', 'subprocess.py(1184):', 'closed', '=', '{', 'None', '}',
...
etc.
History
Date User Action Args
2012-06-05 14:40:12techtoniksetrecipients: + techtonik
2012-06-05 14:40:11techtoniksetmessageid: <1338907211.87.0.323271147876.issue15005@psf.upfronthosting.co.za>
2012-06-05 14:40:11techtoniklinkissue15005 messages
2012-06-05 14:40:10techtonikcreate