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).<br>
<br>Phillip<br><br><div class="gmail_quote">On Mon, Dec 20, 2010 at 11:20 AM, Éric Araujo <span dir="ltr">&lt;<a href="mailto:report@bugs.python.org">report@bugs.python.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Changes by Éric Araujo &lt;<a href="mailto:merwok@netwok.org">merwok@netwok.org</a>&gt;:<br>
<br>
<br>
----------<br>
components: +IO<br>
nosy: +eric.araujo<br>
versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6<br>
<div><div></div><div class="h5"><br>
_______________________________________<br>
Python tracker &lt;<a href="mailto:report@bugs.python.org">report@bugs.python.org</a>&gt;<br>
&lt;<a href="http://bugs.python.org/issue10715" target="_blank">http://bugs.python.org/issue10715</a>&gt;<br>
_______________________________________<br>
</div></div></blockquote></div><br>