Once Python 2.1.1 is released, and I've updated the OS/2+EMX port, I plan to submit the diffs for the port to the Python patch manager. I'd appreciate advice on whether to include the DistUtils patches as part of a complete Python port patch, or submit them separately. If the latter, pointers on submission also appreciated. For info: The only significant change to the DistUtils involves adding emxccompiler.py, which is derived from cygwinccompiler.py (IIRC - I'm not close to the sources right now). It is possible the EMX changes could be merged back into the original, as the changes aren't too drastic. There are other changes to various files of course, to add platform specifics - ccompiler.py, spawn.py, sysconfig.py, util.py, command/bdist_dumb.py and command/build_ext.py come to mind. ----------------------------------------------------------------------- Andrew MacIntyre \ E-mail: andrew.macintyre@aba.gov.au Planning & Licensing Branch \ Tel: +61 2 6256 2812 Australian Broadcasting Authority \ Fax: +61 2 6253 3277 -> "These thoughts are mine alone!" <----------------------------------
Andrew MacIntyre writes:
Once Python 2.1.1 is released, and I've updated the OS/2+EMX port, I plan to submit the diffs for the port to the Python patch manager.
Why wait?
I'd appreciate advice on whether to include the DistUtils patches as part of a complete Python port patch, or submit them separately. If the latter, pointers on submission also appreciated.
It's probably best to submit this as a separate patch. Distutils has a separate patch category on the SourceForge patch manager, and it will probably be reviewed by a different person. Keeping each individual patch small actually makes it easier to review and incorporate patches. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Digital Creations
participants (2)
-
Andrew MacIntyre
-
Fred L. Drake, Jr.