Possible bug in Internal Python API

[Miguel Araujo]

Thanks for the tip Vishakh,

I'm going to start writing on the wiki today as I just finished my project.
If any of you were curious about it, it is a plugin for better integrating
Mercurial VCS with Trac. It solves one of the tickets TracMercurial Plugin
has since a year ago. You can read about it here, in my blog:
http://tumblr.com/x8tg5xbsh

Now, see If I can improve the Mercurial API docs :)


2010/8/13 Vishakh Harikumar <vsh426 at gmail.com>

> On Fri, Aug 13, 2010 at 7:08 PM, Miguel Araujo <muchochini at gmail.com>
> wrote:
> > 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.
>
> The debugshell extension might come in handy for playing with the api,
> http://mercurial.selenic.com/wiki/debugshellExtension
>
> --
> vsh
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20100820/d8624a3f/attachment.htm>