I eventually determined that a call to `subprocess.Popen` was responsible for the message, but could have determined this much more quickly if the message had included the name of the file that could not be opened (executed).
Phillip
Changes by Éric Araujo <merwok@netwok.org>:
----------
components: +IO
nosy: +eric.araujo
versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6
_______________________________________
Python tracker <report@bugs.python.org>
<http://bugs.python.org/issue10715>
_______________________________________