Matt Wilson writes:
> Hmm... I'm thinking of putting all the python code into a
> python1.5/site-packages/anaconda directory. I need to find the 'proper'
> way to package large python apps...
I haven't looked at Anaconda yet.
Does it make sense to import any of the code in Anaconda? If so,
this would make sense, and make sure there's an __init__.py in there;
the main script can take the form:
#! /usr/bin/env python
from anaconda.main import main
main()
If not, then don't; put the code someplace like
${prefix}/lib/anaconda/ and use a symlink from ${prefix}/bin to point
to the main script(s).
The site-packages directory is for Python packages, not modules that
belong to applications. Module sources and .pyc/.pyo files should be
considered platform-independent support files for the application.
-Fred
--
Fred L. Drake, Jr. <[EMAIL PROTECTED]>
Corporation for National Research Initiatives
To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
