[issue2057] difflib: add patch capability

Terry J. Reedy added the comment: I am going to agree with starting on PyPI if indeed there is not something there now. -- resolution: -> rejected stage: needs patch -> resolved status: open -> closed ___ Python tracker

[issue2057] difflib: add patch capability

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 exampl

[issue2057] difflib: add patch capability

Terry J. Reedy added the comment: I would like a simple patcher for three reasons. 1. hg, at least as I see it exposed through tortoisehg workbenck, will not apply a patch if there is already an uncommitted change. (But perhaps someone will tell me that there is a 'do it anyway' option.) Some

[issue2057] difflib: add patch capability

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue2057] difflib: add patch capability

Éric Araujo added the comment: Hi Marco, thanks for your interest in improving Python. Do you want to propose a patch for this request? If so, guidelines and help are found in the devguide. (For the other bug, please read the discussion there to see why 2.7 is not possible.) -- __

[issue2057] difflib: add patch capability

Marco Scataglini added the comment: I agree with Anatoly that it should be an easy way to create and apply Unified Diff Patches within Python. Also issue 2142 should get fixed, as proposed, but also include the fix at least on 2.7 not only on 3.x -- nosy: +marco _

[issue2057] difflib: add patch capability

Éric Araujo added the comment: A productive thing to do would be to ask feedback on python-ideas for this new feature. -- ___ Python tracker ___

[issue2057] difflib: add patch capability

anatoly techtonik added the comment: It is not sarcasm, but prerequisite. I do not sign papers I don't understand or papers that doesn't make any sense (and thus are free to any interpretation). I could sign current CLA right away, but I prefer not to do this until everybody is aware of the i

[issue2057] difflib: add patch capability

Amaury Forgeot d'Arc added the comment: Anatoly, Even if I remove all sarcasm from your previous answer, I don't see what it brings to the current issue. -- nosy: +amaury.forgeotdarc ___ Python tracker ___

[issue2057] difflib: add patch capability

anatoly techtonik added the comment: For this to move forward, PSF should accelerate work on new sane Contributor's Agreements or join Harmony (http://www.harmonyagreements.org/) -- ___ Python tracker

[issue2057] difflib: add patch capability

Éric Araujo added the comment: For this to move forward, a patch or link to Mercurial repo would be required. -- nosy: +eric.araujo stage: test needed -> needs patch versions: +Python 3.3 -Python 3.2 ___ Python tracker

[issue2057] difflib: add patch capability

anatoly techtonik added the comment: On Mon, Sep 20, 2010 at 11:58 PM, Terry J. Reedy wrote: > Given that difflib produces unified diffs (among 3 others) and that diff.py > is a thin command-line wrapper that provides access to all 4 formats (with no > default), I consider those two files 're

[issue2057] difflib: add patch capability

Terry J. Reedy added the comment: Given that difflib produces unified diffs (among 3 others) and that diff.py is a thin command-line wrapper that provides access to all 4 formats (with no default), I consider those two files 'ready'. So I presume you are referring to your patch.py, which is s

[issue2057] difflib: add patch capability

anatoly techtonik added the comment: Unified diffs is the preferred type on this tracker as http://www.python.org/dev/patches/ describes. I also sure that they constitute more than 90% of patches attached here. If you have access to tracker attachments - you can test this. Unfortunately, dif

[issue2057] difflib: add patch capability

Mark Lawrence added the comment: Is this really needed? TortoiseSVN is a cracking bit of kit, and I'm hoping that in the future TortoiseHG is as good if not better. -- nosy: +BreamoreBoy ___ Python tracker __

[issue2057] difflib: add patch capability

Terry J. Reedy added the comment: I would like to see this more easily available, perhaps in /Scripts. Are unified diffs the type usually posted to the tracker? I am not sure what you meant by ' diff/patch lib is not.' -- nosy: +terry.reedy stage: -> unit test needed versions: +Python

[issue2057] difflib: add patch capability

Changes by Alexander Stanley : -- nosy: +swixel ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue2057] difflib: add patch capability

Changes by Todd Whiteman : -- nosy: +twhitema ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue2057] difflib: add patch capability

Changes by Stefan van der Walt : -- nosy: +stefanv ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue2057] difflib: add patch capability

anatoly techtonik added the comment: Tool is ready. diff/patch lib is not. http://code.google.com/p/python-patch/ -- ___ Python tracker ___ __

[issue2057] difflib: add patch capability

Changes by Christian Heimes: -- priority: -> low __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue2057] difflib: add patch capability

New submission from anatoly techtonik: difflib alone and bundled Tools\Scripts\diff.py utility are both very useful, esp. on windows platforms where standard unix diffutils are absent. However, python difflib still doesn't have a patch counterpart to apply at least unified diff format. -