On 4/11/2009 1:15 AM, David Cournapeau wrote:
(sorry for having forgotten to CC the list the first time)
On 2/11/2009 6:34 PM, David Cournapeau wrote:
The way I did was similar to what we do in numpy, that is setup.py is
still using distutils by default, but if you call setupegg.py, you get
the setuptools feature set. The changes to pywin32 sources are minimal
(< 20 lines), and none of the changes should affect current users.
I attached the patch to this email.
The only test I have done is that python setupegg.py and setup.py
install generate the same tree (and that the produced egg is working).
I am not very familiar with pywin32, so if there is a formal test
suite to run, let me know,
Sorry for the delay,
Is it possible to just have 'setup.py bdist_egg' do the right thing
without the new setupegg.py?
Cheers,
Mark
_______________________________________________
python-win32 mailing list
python-win32@python.org
http://mail.python.org/mailman/listinfo/python-win32
