Robyn Allsman and I talked about the code arrangement this morning
and came up with some refinements which I have implemented.
Installed package hierarchy:
- I had some general application-support code that I was installing
in lsst.apps. This is now installed in lsst.fw (framework) a new
package.
- lsst.apps will be used for support code for individual
applications. This is code which is primarily or only of interest to
the one application (reusable code belongs in lsst.fw or lsst.mw).
Thus for example dbingest puts some support files in
lsst.apps.dbingest.
Source code hierarchy:
- I combined the code in pyapps and pymw into pylsst. Thus pylsst now
contains all framework code. It is installed with one installer and
has one parent html document that links to the other documents.
- I moved dbingest into applications.
I am very happy with the new arrangement and I hope you are, as well.
See DocuShare document 2022 "Python Code Organization for DC1" for a
full description of the layout.
-- Russell
_______________________________________________
LSST-data mailing list
[email protected]
http://www.lsstmail.org/mailman/listinfo/lsst-data
