By the way, Do you happen to have a pywin32 buildbot that could run on the python trunk ? (where I can get emails when it's broken) That would be useful because I am doing a lot of work in the trunk. Tarek On Tue, May 19, 2009 at 4:54 PM, Tarek Ziadé <ziade.tarek@gmail.com> wrote:
Hi Tim, thanks for the feedback,
this has been fixed in r72758
http://svn.python.org/view/python/trunk/Lib/distutils/command/build_ext.py?r1=72593&r2=72758
Regards Tarek
On Tue, May 19, 2009 at 4:00 PM, Tim Golden <mail@timgolden.me.uk> wrote:
[coming from a thread on python-win32: http://mail.python.org/pipermail/python-win32/2009-May/009130.html ]
In short: changes to build_ext.py in r72585 caused the pywin32 packages to stop building correctly. The changes in question are those which call get_ext_filename with the short form of the ext.name (without the package prefix). The pywin32 setup.py expects the fully-qualified name in the get_ext_filename in its subclass.
Now I don't know whether this is an incautious change to build_ext or a false -- altho' historically valid -- assumption on the part of the pywin32 developers. You can see their code here at line 1119:
http://pywin32.cvs.sourceforge.net/viewvc/pywin32/pywin32/setup.py?revision=1.107&view=markup
I'm afraid I'm fairly ignorant of the design rationale behind distutils; I'm hoping someone here has a better idea :)
Opinions?
TJG _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
-- Tarek Ziadé | http://ziade.org
-- Tarek Ziadé | http://ziade.org