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

alisonken1 alisonken1 at gmail.com
Thu Apr 20 20:35:50 EDT 2006

Previous message (by thread): 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
Next message (by thread): 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
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Not sure about "vcs" - but "cvs" can be more fun if the hard disk dies
{g}.

Previous message (by thread): 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
Next message (by thread): 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
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Python-list mailing list