Raymond Hettinger added the comment: I don't think this should be done. Python is primarily a language with a standard library, not a command-line development toolkit. We should avoid "mission creep".
There are plenty of mature, robust, full-featured solutions already available. For example, when I was developing Python on Windows, I used the GNU Win32 toolkit. If anything, this ought to be an offering on PyPI. There is could live freely outside our rather slow release cycle which is too lethargic to respond the challenges that would inevitably arise with a new command-line tool (i.e. it won't handle input from some diff utility, or isn't robust against minor spacing issues or encoding issues, or it can't handle slightly offset hunks etc). ---------- nosy: +rhettinger _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue2057> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
