In message
, Dun
Peal wrote:
> On Oct 4, 7:23 pm, Lawrence D'Oliveiro
> wrote:
>
>> You can already check the exit status from the subprocess. What more do
>> you need?
>
> A robust mechanism to deal with said issues...
You haven’t explained what “issues” will not be reported via a failure exi
Dun Peal writes:
> Of course I can write it myself, but it would save much time and
> effort if I could use something that's already written.
You don't mention which ones you've already evaluated or are aware of,
so I'll point out that Bazaar and Mercurial both use the Dulwich library
http://pyp
On Oct 4, 7:23 pm, Lawrence D'Oliveiro wrote:
> You can already check the exit status from the subprocess. What more do you
> need?
A robust mechanism to deal with said issues...
Of course I can write it myself, but it would save much time and
effort if I could use something that's already writt
In message
, Dun
Peal wrote:
> That's what I'm doing right now, but since this is a mission-critical
> process, it would be nice to have a more reliable exception detection
> and handling mechanism.
You can already check the exit status from the subprocess. What more do you
need?
> For instanc
On Oct 4, 4:04 pm, Lawrence D'Oliveiro wrote:
> Why not just call Git itself?
That's what I'm doing right now, but since this is a mission-critical
process, it would be nice to have a more reliable exception detection
and handling mechanism. With my straight calling-out-to-git
implementation, the
Hi folks,
I'm writing a Python program to operate on Git repositories.
The program works at the user level of abstraction: i.e. it needs to
do everything that an end user can do with Git.
I'm talking about the high-level commands like git-clone, git-branch,
git-fetch, git-merge, git-rebase, git-
