July 20, 2011
11:41 p.m.
On 21/07/2011 7:43 AM, Glenn Linderman wrote: ...
I still get the same behavior. Is there any debugging output produced by py.exe that would tell what py.ini it looks in, and what the content is? What diagnostic steps might I take to produce additional information that would help you (or me, along the way) analyze the issue? I do not presently have a C compiler installed on this machine, however, unless it came along for a ride with something else.
It doesn't do exactly what you ask, but setting an environment variable PYLAUNCH_DEBUG to any value will cause some debug output to be generated to stdout. Mark