Dan Nicholson added the comment:
Right, that's what makes this difficult. If the stub exe of the target python
was used, then it wouldn't need to care about compatibility. However, what
you're running is the stub of the build python. So, when I distribute a
bdist_wininst exe, i
Dan Nicholson added the comment:
Like the previous users, I've only got VS Express, so I can't tell exactly what
happens when you have VS Pro and it generates the install.rc file. However, I
might as well post this fuller patch, which I think would do the right thing
since it also
Changes by Dan Nicholson :
Added file: http://bugs.python.org/file31717/wininst-9.0-compat-2.7.exe
___
Python tracker
<http://bugs.python.org/issue4636>
___
___
Python-bug
Changes by Dan Nicholson :
Added file: http://bugs.python.org/file31715/wininst-compat-2.7.patch
___
Python tracker
<http://bugs.python.org/issue4636>
___
___
Python-bug
Changes by Dan Nicholson :
Added file: http://bugs.python.org/file31716/wininst-10.0-compat.exe
___
Python tracker
<http://bugs.python.org/issue4636>
___
___
Python-bug
Dan Nicholson added the comment:
It turns out this is pretty easy to fix by just changing the stub to import
builtins or __builtin__ depending on the python install version. Attached are
patches that fix this for both the default and 2.7 branches.
My test case is a pure python module with an
