2009/3/22 Steve Borho <[email protected]>
> On Sun, Mar 22, 2009 at 12:12 PM, Stefano Mioli <[email protected]> wrote:
> > Hi all,
> > I cloned THg's crew repo a couple of hours ago.
> > While skimming through the sources, I was wondering what's the easiest
> > way to debug.
> >
> > I mean, what steps do you guys follow to test a change to, say, the
> > commit dialog (which, if I understand correctly, is located in
> > \hggtk\commit.py)?
>
> Yes, all of the dialog code is in hggtk. Commit is in commit.py, but
> it uses a lot of code from status.py and gdialog.py
>
> > And, just out of curiosity, do you use a particular IDE or something?
>
> I do most of my debugging just by running the dialog via hgtk.
> Debugging python GUI apps is usually no more difficult than sprinkling
> print statements in appropriate places.
>
> Perhaps others have more interesting debug environments?
>
I have flirted with Eclipse and Code::Blocks, but reverted to a command line
+ a plain text editor (SciTe/Notepad++)
I use a number of small .bat files to set up environment, launch programs,
etc.
During major upgrades of Mercurial I have found it helpful to have isolated
Python environments, using http://pypi.python.org/pypi/virtualenv
Regards,
Peer
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Tortoisehg-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
