setup.py deleting files (Was: SSL support in _socket)
I now recall why setup.py deletes modules that cannot be imported: If they would be left there, the test cases would fail with the ImportError. People had been complaining that they get testsuite failures, so we changed setup.py to remove the modules which clearly don't work. Regards, Martin
Martin von Loewis wrote:
I now recall why setup.py deletes modules that cannot be imported: If they would be left there, the test cases would fail with the ImportError. People had been complaining that they get testsuite failures, so we changed setup.py to remove the modules which clearly don't work.
Left aside whether this is a good idea, setup.py should grow an option to make this removal controllable. -- Marc-Andre Lemburg CEO eGenix.com Software GmbH ______________________________________________________________________ Company & Consulting: http://www.egenix.com/ Python Software: http://www.egenix.com/files/python/
"MvL" == Martin von Loewis <loewis@informatik.hu-berlin.de> writes:
MvL> I now recall why setup.py deletes modules that cannot be MvL> imported: If they would be left there, the test cases would MvL> fail with the ImportError. People had been complaining that MvL> they get testsuite failures, so we changed setup.py to remove MvL> the modules which clearly don't work. Can we just rename them? I.e. bsddbmodule-failed.so That would at least leave some artifact around so that the problem has a chance of being debugged. -Barry
Martin> I now recall why setup.py deletes modules that cannot be Martin> imported: ... Regardless of the reason, I continue to think it's a moderately bad idea. No post-mortem on the suspect object or shared object file is possible. Skip
participants (4)
-
barry＠zope.com -
M.-A. Lemburg -
Martin von Loewis -
Skip Montanaro