[issue5076] bdist_wininst fails on py3k
report at bugs.python.org
Tue Jan 27 10:57:37 CET 2009
Mark Hammond <mhammond at users.sourceforge.net> added the comment:
> Is it really useful to be have the same stub for 2.x and 3.x?
> I think it would be better if they mutually ignore each
> other, and be different.
Good question! I'm not really aware of the complexities involved in
merging between the various branches, but given the fairly trivial
nature of the patch I figured there were potential advantages in both
identical source and stubs. I'm happy to work the patch into either
#ifdef based (ie, identical source, different stubs), or "unconditional"
(both source and stubs different) if you prefer - and if so, which of
those 2 do you prefer?
On a related note, its obviously true that the same final installer will
not be able to be shared between 2.x and 3.x, as is currently possible
between pure-python installers between the 2.x series. However, this
could be addressed in .py code at a later time while still allowing the
same stub to be shared if that is desirable.
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list