At 8:28 AM -1000 2006-06-30, Francesco Pierfederici wrote:
OK, even though my heart is bleeding, I can definitely see the idea
behind dropping the .py extension for command line tools (even
though it will make it a royal pain to edit those files in Eclipse).
One nasty-ish possibility would be to keep the extension and then
have the installer remove it...
I'll think about that. It does make the installer harder. (Are you
sure Eclipse will not look at the #! line to figure out what language
is in use -- if there is no suffix?). Anyway, I'm not wedded to
ditching the suffix.
Directory structure. What about something like this (I understand
that you guys thought about this a lot, please bear with me):
lsst
apps
someApp
src
python
bla.py
c
bla.c
...
doc
bla.txt
test
...
data
...
someOtherApp
...
mw
someMW
[same structure]
The main point of my proposal is to keep code for a python package
together. That makes installation easier because the directory
hierarchy of python code directly reflects the name space (used to
import code). A typical pure python package that has source code
organized the way it will appear in the final installed package is
trivial to write -- just point the installer to the root of the
source tree and you're done.
That is why I don't want to just keep the python code in the existing
svn hierarchy -- it distributes modules for a give package too
widely, making the installer much more difficult to write.
-- Russell
_______________________________________________
LSST-data mailing list
[email protected]
http://www.lsstmail.org/mailman/listinfo/lsst-data
