> so if you are hacking around inside analysis and changeing bits of code
> (adding debug statements etc) each time you make a change you have to
> reload analysis for any changes in the code of the class to be loaded on
> current instance objects (only new objects will pickup the changes). Now
> there are fancy ways around this using metclasses etc but i just wanted
> to know if the analysis people had a way round this 'change code - quit
> analysis - restart analysis with new code' cycle which can be quite
> consuming if you load a large project or each startup
Hi Gary,
I use macros for prototyping most things, as they can be reloaded without
having to restart Analysis. Sure, you have to copy the bits you're playing
with into the macro file, but development is quick and you can still call
the original unaltered functions.
Alternatively, look in .../python/ccpnmr/analysis/Command.py to see how
the macro reloading is done.
T.
-------------------------------------------------------------------------------
Dr Tim Stevens Email: [log in to unmask]
Department of Biochemistry [log in to unmask]
University of Cambridge Phone: +44 1223 766018 (office)
80 Tennis Court Road +44 7816 338275 (mobile)
Old Addenbrooke's Site +44 1223 364613 (home)
Cambridge CB2 1GA WWWeb: http://www.bio.cam.ac.uk/~tjs23
United Kingdom http://www.pantonia.co.uk
-------------------------------------------------------------------------------
------ +NH3CH(CH(CH3)OH)C(O)NHCH(CH(CH3)CH2CH3)C(O)NHCH(CH2CH2SCH3)CO2- -------
-------------------------------------------------------------------------------
|