Phillip J. Eby wrote:
At 04:47 PM 5/15/2007 -0500, Robert Kern wrote:
Phillip J. Eby wrote:
Reading that page, I'm not sure whether you want a scikits namespace package in the first place. A namespace package is used to group several projects under a single "owner", ala the various zope.* and peak.* and plone.* packages. However, nobody but Zope Corp. should be releasing a zope.* package, and nobody but me releasing a peak.* one. The whole point is to "claim" a namespace for packages being released by a single owner - either an organization or umbrella project. This corresponds to things like the 'org.apache' and 'com.sun' package namespaces in Java - it's just a namespace to allow authors free rein to put whatever modules and packages they like under that namespace. This is exactly what we are aiming for. While different people will be responsbile for each subpackage, they are all operating under the aegis of the scikits infrastructure.
But who adds things to the namespace? Is there a single organization that decides what packages or modules will exist in scikits?
Yes, the scipy developer team. mlabwrap is just the first scikits project. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco