How should multiple (related) projects be arranged (structured) and configured so that they can share code, have a related package structure and enable proper unittesting, and ensuring no namespace collisions

[bruno at modulix]

alisonken1 wrote:
> As to the question "fail to see how version control relates to
> code/test separation", the original poster asked several questions, one
> of which was production/testing code separation.
> 
> Along with the separation (so while you're testing new functionality,
> you don't break production files), a properly setup CVS allows you to
> do this by importing files from a production branch into your testing
> branch 

Ok, get it - you're talking about branching,  when the OP talked about
unit testing, which is something totally different.


-- 
bruno desthuilliers
python -c "print '@'.join(['.'.join([w[::-1] for w in p.split('.')]) for
p in 'onurb at xiludom.gro'.split('@')])"