The same way you are. i.e. just recompile everything. If you are building in place, I *think* you can get away with just running the setup.py script in the directory that has changed files. But don&#39;t quote me on that. <br>
<br><div class="gmail_quote">On Sun, Oct 31, 2010 at 2:54 PM, Maël Primet <span dir="ltr">&lt;<a href="mailto:mael.primet@gmail.com">mael.primet@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Sure, this was the idea, however since it was easier <div> for me to develop the viewer as a side program, I haven&#39;t done it yet</div><div><br></div><div>btw I find it hard to develop directly inside scikits.image, because each time I compile the library, it recompiles everything, rather than the things that changed. How do you </div>


<div> handle developpment of new modules.?</div>
</blockquote></div><br>