On Tue, Oct 13, 2009 at 5:30 PM, P.J. Eby email@example.com wrote:
One identical to test_build_ext_path_with_os_sep, but that explicitly uses a '/' (rather than os.sep) will identify the problem I'm referring to, when run on Windows.
It's common practice to use /-separated paths in setup scripts, regardless of platform. So, your current fix (converting os.sep to '.') will work on Linux, Mac, etc., but fail on Windows when run with the same setup.py, since os.sep is a backslash there.
Ok I will have a look at this tonite. Thanks. Notice that this changed I made to fix another bug opened a can of worms because Extension is not enough/clearly documented in this regards.
The goal for 2.7/3.2 is to come up with one single way to define extensions, and I will probably just add deprecation warnings for the other forms.
(Just as a side note, if when you split off issue 7115 you'd said what the new issue number was in 7064, or copied me to the nosy-list on the new issue, I'd have been able to review this change and comment on it yesterday instead of today, and I'd have done it in the bug tracker rather than via Python-Dev.)
Sorry about that, I'll add a note on #7064.