[chimera-dev] Debugging own extension in Mac OS X

[Tom Goddard]

Hi Pablo,

  Our typical Python debugging is run the code, see the traceback reported by Chimera, fix the code in the editor of your choice, quit Chimera and start again.  If you are asking about IDEs (integrated development environments) for Python that help with this cycle, I have not tried any.  Those typically can run Python code for you.  That is suitable for procedural code but I doubt it integrates well with Python apps such as Chimera that use an event driven graphical user interface.

	Tom


> On Feb 20, 2017, at 4:17 AM, Pablo Solar Rodríguez wrote:
> 
>  
> Hello all,
> 
> My name is Pablo Solar and I am newbie in a real BioInformatics work, specifically in Chimera. Due to my new project requirements, I want/need to write a Chimera Extensión which executes an existing tool for fitting maps in an exhaustive way. I started to read the documentation available and the programmers guide, but the fist question that came to my mind is about debugging.
> 
> I would like to know how could I debug my extension python code while I work with Chimera at the same time. Is this possible? I mean, opening my extension in Chimera (Tools -> preferences and so on) and starting to debug the _init_py and the rest of my files. How should I configure my environment? What framework to use? That kind of things
> 
> Thank you in advance. I think I will post questions frequently because, as I said, this is totally new to me. By the way, I suscribed to the mailing list with my personal mail (pablosolar.r at gmail.com)
> 
> I would like to give you all kind regards and hope to learn from you as much as possible. Just need a bit of patience... :)
> 
> Keep in touch and thank you in advance,
> 
> Pablo Solar.
> _______________________________________________
> Chimera-dev mailing list
> Chimera-dev at cgl.ucsf.edu
> http://www.rbvi.ucsf.edu/mailman/listinfo/chimera-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://plato.cgl.ucsf.edu/pipermail/chimera-dev/attachments/20170221/4dda267d/attachment.html>