I would like to bring some logical structure to the packaging of our python modules. To be consistent with the architectural goals described in https://sourceforge.net/apps/trac/pytrainer/wiki/Architecture I think our packages should look like:
pytrainer - contains the main module pytrainer.util - contains utility modules (should be very few) pytrainer.core - contains entity, persistence and service modules pytrainer.gui - contains gui frontend modules pytrainer.upgrade - contains data migration modules I will start to use this package structure for the new service layer modules that I am currently adding. - Nathan ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 _______________________________________________ Pytrainer-devel mailing list Pytrainer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytrainer-devel
