Re: [StGIT PATCH 3/5] Create a git.Branch class as ancestor of stack.Stack

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Jun 8, 2008 at 3:16 PM, Catalin Marinas<catalin.marinas@xxxxxxxxx> wrote:> On 07/06/2008, Karl Hasselström <kha@xxxxxxxxxxx> wrote:>> On 2008-06-06 09:44:37 +0100, Catalin Marinas wrote:>>  > 2008/6/5 Karl Hasselström <kha@xxxxxxxxxxx>:>> > > We'll have to be watchful against attempts to create objects other>> > > than via the officially designated factories, though. Python>> > > doesn't really have any mechanisms that help us here.>> >>> > If you really want enforcing this, it can probably be done by>> > hacking __new__ and __init__.>>>> No, I reckon you're right -- it's overkill. StGit is small enough that>>  we can probably enforce the relevant restrictions by hand.>> Hidden plan - once the new stgit.lib.git module is complete, we can> advertise it as a stand-alone object-oriented Git wrapper for Python> :-). At that point, we can think about enforcing the factory> mechanism.>> --> Catalin
Surely you don't want people to have to install stgit just to "import git"?(or perhaps you do, since that'd give people incentive to install stgit ;))
Back to the point...
A few folks are working towards an OO git interface for python.Perhaps joining forces would be a big win for everyone?
http://gitorious.org/projects/git-python
It would be really cool if we could wrangle in all interested partiestowards a common goal for python.  You guys (the stgit team) have alot of experience in this domain so your ideas and opinions would begreatly appreciated.
--  David��.n��������+%������w��{.n��������n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�m


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux