python hglib missing features

Barry Scott barry at barrys-emacs.org
Thu Oct 6 09:48:01 UTC 2016


On Thursday, 6 October 2016 02:42:21 BST Gregory Szorc wrote:
> On Thu, Oct 6, 2016 at 1:56 AM, Barry Scott <barry at barrys-emacs.org> wrote:
> > I wish to know if Mercurial project is willing to take patches to add
> > missing
> > features to hglib for Python?
> > 
> > I am writing a GUI interface to hg that needs support in hglib that is
> > missing.
> > 
> > 1. Provided 'o'utput and 'e'rror data to the call of hglib as it arrives.
> > 
> > 2. Handle the 'L'ine protocol element to call back into the user of hglib
> > to
> > provided the required input.
> > 
> > (1) will allow for the GUI to present the user with info from hg commands.
> > It will also allow detecting that prompts that caused 'L'ine request, for
> > example user/pass prompts.
> > 
> > As hglib is structured at the moment there is not a simple way for a
> > caller
> > to get hold of 'o'utput and 'e'rror data or be notified of an 'L'ine
> > requires.
> > 
> > I you are will to take patches what is the process you need me to follow
> > for hglib?
> 
> These both sound like great features to add to hglib! I think having hglib
> support fully-featured custom GUIs is a worthy end goal. That being said,
> I'm not sure how we'll support both a synchronous request-response API
> (like we have) and a streaming one or one that handles user input. You may
> want to send a more concrete proposal to the mercurial-devel list before
> you code too much. This could be a long email describing things in detail,
> a link to a design doc (such as a *Plan page on the wiki - like
> https://www.mercurial-scm.org/wiki/TopicPlan), or a link to a repository,
> gist, etc showing a proof-of-concept. You could even publish patches marked
> as "RFC" if you have code already.
> 
> As for submitting patches, send them using the same instructions as
> Mercurial itself: https://www.mercurial-scm.org/wiki/ContributingChanges.
> You'll want to use `--flag hglib` or `--flag python-hglib` so the email
> subject calls out the patch as belonging to hglib.

I think I can have this as an RFC with modest amount of work. I'll post to
mercurial devel as you suggest as an RFC once I have something working.

Barry




More information about the Mercurial mailing list