E. Madison Bray writes: > However, I can see how this could be inconvenient for some Python > builds where you might have something within the setup.py script > (which, when building Python extension modules, is still usually used) > like (in pseudo-code): > > run_build_ext_command() > import just_built_module > # Use just_built_module to generate some files > run_install_command() > > all within the same process. One could work around this by modifying > the setup.py to call `rebase` as a subprocess and that should work, > but it would suck to have to make such extra considerations just for > Cygwin, much less get some upstream project to accept that.
Well, Perl has hooks for platform specific code in ExtUtils and Module::Install, so that takes care of 99% of the module builds out there and they seem to have no trouble accepting it into their code as long as you can demonstrate that it woreks and why it's there. I won't touch Python if I can avoid it, so I have no idea what they do; but again, it would seem a glaring omission to not have _something_ that caters to the runtime platform at least. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
