On Thu, 29 Jun 2006, Francesco Pierfederici wrote:
> It is not super clear to me the reason to have a duplicate directory
> structure in the repository, one at the top level (applications,
> pymw...) and then the same thing under pylsst. Wouldn't be simpler to
> have code in SVN organized as installed modules (i.e. use only the
> pylsst tree)?
Two items we need to keep in mind:
o not all code will be in python
o some packages may have a combination of code in different languages
(that are not strictly python extension packages). E.g. Java +
python, or Java + C++.
Nevertheless, we know this is not perfect, so your suggestions are
welcome as we expect to evolve this.
> Two aesthetical preferences: I would drop the prefix py and keep the
> extension .py.
The py prefix is just for package names. I personally would not be upset
if you did not follow this one, but it is encouraged so that we can
recognize it as primarily a python package.
Same goes with the .py extension for command-line scripts, but an argument
for not using it is that it may get implemented in another language in the
future.
cheers,
Ray
_______________________________________________
LSST-data mailing list
[email protected]
http://www.lsstmail.org/mailman/listinfo/lsst-data
