Possible bug in Internal Python API

[Miguel Araujo]

Hello Greg,


> Mercurial is an open source project.  It's up to *everyone* to make it
> better.
> And you don't need to be able to devour revlogs raw before breakfast to
> make
> it better.  If you find a key API method is undocumented, then write a
> docstring
> and send a patch.  If your docstring is good, the patch will be
> accepted; if not,
> it's quite likely that someone will point out what you missed.  End result:
> Mercurial gets better *and* you learn something.  As does everyone who
> follows
> that thread on the mailing list, or finds it in the archive in 2 years.
>

I totally agree with you. I perfectly understand how the open source
initiative works and I understand the "show me code" lesson. I'm still far
of being confident with the API to improve docstrings correctly.


>
> Also, all you have to do to improve the wiki is create a username for
> yourself and
> get editing.  The MercurialApi page could definitely use some more
> explicit tips,
> suggestions, friendly advice, high-level guidelines, etc.
>
>
I will do this, see if I can promote the use of the API. Although I'm still
convinced that the API should be more stable or use versioning.

Regards,
Miguel Araujo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20100813/b8a6f411/attachment.htm>