diff options
author | Todd Gamblin <tgamblin@llnl.gov> | 2018-05-10 10:01:55 -0700 |
---|---|---|
committer | Todd Gamblin <tgamblin@llnl.gov> | 2018-05-18 16:06:21 -0700 |
commit | 6b2c49648a7ad53022a0d83dcb043399d7041027 (patch) | |
tree | cec7714aff83866db6822b02799fc5e54d8b90b6 /README.md | |
parent | f2eb71ca2086a77a2ebd8d08afb564991ef00b43 (diff) | |
download | spack-6b2c49648a7ad53022a0d83dcb043399d7041027.tar.gz spack-6b2c49648a7ad53022a0d83dcb043399d7041027.tar.bz2 spack-6b2c49648a7ad53022a0d83dcb043399d7041027.tar.xz spack-6b2c49648a7ad53022a0d83dcb043399d7041027.zip |
init: move symbols in `spack` to `spack.pkgkit`
- Spack packages were originally expected to call `from spack import *`
themselves, but it has become difficult to manage imports in the
Spack core.
- the top-level namespace polluted by package symbols, and it's not
possible to avoid circular dependencies and unnecessary module loads in
the core, given all the stuff the packages need.
- This makes the top-level `spack` package essentially empty, save for a
version tuple and a version string, and `from spack import *` is now
essentially a no-op.
- The common routines and directives that packages need are now in
`spack.pkgkit`, and the import system forces packages to automatically
include this so that old packages that call `from spack import *`
will continue to work without modification.
- Since `from spack import *` is no longer required, we could consider
removing ``from spack import *`` from packages in the future and
shifting to ``from spack.pkgkit import *``, but we can wait a while to
do this.
Diffstat (limited to 'README.md')
0 files changed, 0 insertions, 0 deletions