qct 0.4 released

Steve Borho steve at borho.org
Mon Dec 18 21:10:58 UTC 2006


On Monday 18 December 2006 2:45 pm, Satish Balay wrote:
> On Mon, 18 Dec 2006, Steve Borho wrote:
> > The mercurial extension should have been installed for you by
> > setup.py. You just need to enable it in your ~/.hgrc
> >
> > [extensions]
> > hgext.qct =
> >
> > If all is well, you'll get useful output from `hg help qct`
>
> Ah.. I realized my mistake.. I need to update my PYTHONPATH to enable
> mercurial to find this extension [I install each extension in its own
> separate location]. Its curious that I didn't have to do this for
> other extensions [hct,hgk]
>
> Is there an equivalent for PYTHONPATH that I can add in my ~/.hgrc -
> for this to work?? [I hate to use PYTHONPATH]

Sorry, my previous response was bogus.

The reason qct is different from hgct and hgk is that the GUI app is not 
just a standalone binary.  'qct' needs the GUI implementation python 
files in order to run, and those files needed to be separate from the 
standalone app in order for that functionality to be shared between the 
various  VCS back-ends and plugins.

I've got a total of 1 week of python experience.  If someone knows of a 
better way to bundle this all together, I'm all ears.

-- 
Steve Borho (steve at borho.org)
http://www.borho.org/~steve/steve.asc
Key fingerprint = 2D08 E7CF B624 624C DE1F  E2E4 B0C2 5292 F2C6 2C8C



More information about the Mercurial mailing list