[SciPy-dev] Package organization

[Robert Kern]

Travis Oliphant wrote:
> I really like the discussion that is occurring.  Part of the problem 
> with the current system is that there was no discussion and so it just 
> evolved.   I'm not against major surgery on the organization as long as 
> there is some mechanism for helping old users move forward.   That's why 
> scipy has not reached 1.0 yet -- because of code organization issues.
> 
> First.   I like what Fernando is trying to do with the scipy.kits 
> concept.   The most valuable thing scipy could provide is a mechanism 
> for auto-indexing your scipy-related packages for a help browser.  I 
> don't think packages would need to live under scipy to accomplish this 
> (but it would make it easier).   There are other mechanism like the 
> environment variable concept that could also collect package 
> information.  In fact, I wonder if scipy could detect that some module 
> imported it and add that to some internal index (or only add it if the 
> module defined some __scipy__  name or something...

I'm pretty sure we can implement these mechanisms using pkg_resources
and eggs.

  http://peak.telecommunity.com/DevCenter/PkgResources

Specifically, look at the section on "Entry Points".

-- 
Robert Kern
rkern at ucsd.edu

"In the fields of hell where the grass grows high
 Are the graves of dreams allowed to die."
  -- Richard Harter