Possible bug in Internal Python API

[Miguel Araujo]

> Well, I wouldn't say they are poor in the sense that they're
> incorrect, but I would agree that they're not really extensive.
>
> Be aware that our API is also always in flux. If you want a stable
> API, your best bet is scripting the command line (or maybe calling
> functions in the commands module, which map directly to commands).
>
>
When I said poor, I meant scarce, not incorrect. Yes, many functions related
to code, but internal API organization is not obvious to me. I don't
understand why I should parse commands outputs to get the info and have an
stable script. You should think about versioning the API. APIs are for this.
Many people use bash scripting because you don't promote the API use, which
I think is not a good idea.



> I'm not seeing any screenshot. :)
>

Sorry, I sent an email after that one, with the screenshot.


> Right, there aren't many docs. Still, if you start looking at commands
> code to see what they do, the patterns should become obvious. It would
> probably also help if you studied documentation not just on the API,
> but also the underlying data model (and usage of the tool).


I have been using Mercurial for a while, though I wouldn't call myself an
expert. My script is actually trying to promote the use of it in another
open source project.

Thanks Vishakh, I will answer you next mail right now,
Miguel Araujo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20100813/49de7818/attachment.htm>