Hi Dom, I'm sorry I haven't had time to look at this yet. Some comments ...
On Oct 28, 2009, at 4:35 PM, Dominic Lowe wrote: > All (especially Sean & Tom), > > As discussed I've just rejigged all the OWSLib code into separate > eggs under a > single namespace package as you can see here: > > http://trac.gispython.org/lab/browser/OWSLib/branches/ > namespacePkgsTest > > And checkout from here: > svn co http://svn.gispython.org/svn/gispy/OWSLib/branches/namespacePkgsTest/ > mytestdir > > When you have a moment could you please take a look at all this and > see if it > makes sense and works for you? There are eggs for each service, > which will > need building separately as far as I can tell - unless anyone has a > better > way. > > The OWSLib egg itself, depends on all the other services except > owslib.sos, > which Tom says isn't mature enough to go into the final distribution > - so > (when released) "easy install OWSLib" should get you all the service > eggs > except SOS. Alternatively you will be able to do "easy install > OWSLib.wfs" > for example. > > I've also added an owslib.common package, which contains OGC OWSCommon > modules, and other 'common' modules such as etree. Each service egg > depends > on owslib.common. > > Anyway - I'd really like someone else to take a look at this and > check I > haven't scrambled/fried/overcooked the eggs. > > Some questions: > 1) What's the best way to install all these eggs for development? I > ended up > doing "python setup.py develop" on each egg individually. Maybe > that's okay > though as you won't normally be working on all the eggs at once. > Yes, develop for each. A build framework can make this easier. I use zc.buildout for some things, but I'd bet you could do it with Paver. Or a bash script? > 2) What about tests - currently they are in the main owslib package > but it > would be nice to distribute them. But then we'd have to strap them > back > together again to run them as a batch. Any ideas? > How about the nose test runner? From the directory containing all the checkouts, you could do something like (which I haven't actually tried) $ PYTHONPATH=LIST_OF_DEVELOP_EGGS nose owslib/tests owslib.common/ tests ... Zope's test runner can test multiple packages too. > 3) Multiple service versions.. eg the WCS egg contains clients for > wcs 1.0 and > 1.1 - ideally these should be distributed separately... I don't > think it's a > showstopper though at the moment. Agreed. I wish I had more time to try out these suggestions, but I'm a bit submerged in a different project. > > Cheers, > > Dom > > _______________________________________________ > Community mailing list > [email protected] > http://lists.gispython.org/mailman/listinfo/community -- Sean _______________________________________________ Community mailing list [email protected] http://lists.gispython.org/mailman/listinfo/community
