At 05-01-2004 15:11, Michael Chermside wrote:
So I guess I am forced to put up with (2), and the (hopefully minor) headaches of copying Mark's code UNLESS we can somehow ensure that win32all is available on all sane windows installs. If, for instance, it were released with the python.org releases for the Windows platform, (other packagers already include it), then I think we could dispense with the annoying need to duplicate code.
A number of people seem to under the impression that win32all contains a lots of useful value added code. It does not. It is a very thin SWIG wrapper over the windows API that it exposes. There is nothing that you will need to copy from it to implement popen5 in C. Just as you would not copy code from the python posix module to implement popen5 in C on Unix. The value of using win32all would be that you could implement popen5 in python rather then C. This might be a good way to develop and test the win32 popen5 algorithms before conversion to C. Developing the algorithm is going to be the hard part. The issue is a packaging one not a code cloning one. 1) include win32all in the standard windows python and implement popen5 in python 2) implement popen5 in C on windows. As I understand it (2) is the suggested way forwards. Barry