[Numpy-discussion] Package structure

Janko Hauser jhauser at ifm.uni-kiel.de
Fri Jun 2 16:38:36 CDT 2000

An important thing to keep in mind is the possibility that part of
Numeric.py can become a standard part of Python, this would mean that
it has the same status as the string module. This would speak against
a package structure for Numeric itself.

So if packages are used, the structure should not be a subtree of

Second thought: Should every module be it's own package? Or should
there be a structure so that third party modules can be sorted into
this structure (for example sorted by problem domains, math, data, IO,
physics/natural science, image processing etc.) One problem is, if some
libraries with a broader spectrum are wrapped, like GSL, the sorting
becomes obsolete. This would suggest to have a package for every

I would also say, that it is not easy to aim at complete environment
if there is not a refactoring by a maintainer. As long as the modules
are only (not meant in a bad way) provided by different authors there
will be no kitchen sink application. This would also suggest a package
for every module.


More information about the Numpy-discussion mailing list