Re: File extension for the copy of python2.5.exe

2010-05-03 Thread Jason Tishler
Yaakov, On Sun, May 02, 2010 at 08:16:43PM -0500, Yaakov (Cygwin/X) wrote: > On 2010-05-02 16:48, Jason Tishler wrote: > >Unfortunately when I converted to using cygport, I forgot about the > >functionality in my build script to workaround the above issue. > > > >I will try to figure out how to co

Re: File extension for the copy of python2.5.exe

2010-05-02 Thread Yaakov (Cygwin/X)
On 2010-05-02 16:48, Jason Tishler wrote: Unfortunately when I converted to using cygport, I forgot about the functionality in my build script to workaround the above issue. I will try to figure out how to convince cygport to pass "LN=cp" during the "make install" phase. Yaakov, Do you have an

Re: File extension for the copy of python2.5.exe

2010-05-02 Thread Jason Tishler
Jim, On Sat, May 01, 2010 at 09:37:22AM -0700, Jim Eberle wrote: > Part of the latest python rollout involved converting the "python" > symlink into a full file copy. I was wondering if this could be > renamed to "python.exe". > > Without the ".exe" extension, doing a CreateProcess() on "python"

File extension for the copy of python2.5.exe

2010-05-01 Thread Jim Eberle
Part of the latest python rollout involved converting the "python" symlink into a full file copy. I was wondering if this could be renamed to "python.exe". Without the ".exe" extension, doing a CreateProcess() on "python" fails even if the python file exists and is in the calling process' %PAT