RE: [PyCrust] Thoughts...

[Patrick K. O'B. <po...@or...>]

I made the names verbose in order to avoid name clashes when PythonCard was
talking about including the PyCrust files in their directory. I'm not
opposed to shortening the names now.

I'd rather not make assumptions about which classes to import through the
packages' __init__.py file, because of the number of ways PyCrust components
can be used. Some users will use it for just its interpreter, others for the
editor, others will use all the shell defaults but will provide their own
editor, etc. I'll work on more sample apps that illustrate this, but for now
there is PyCrustAlaCarte.py.

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

-----Original Message-----
From: pyc...@li...
[mailto:pyc...@li...]On Behalf Of Robin Dunn
Sent: Friday, August 10, 2001 6:55 PM
To: pyc...@li...
Subject: [PyCrust] Thoughts...

2. Since PyCrust is a Python package, do we really need filenames like
PyCrustShell.py and PyCrustEditor.py?  When importing it just looks
redundant:  "from PyCrust.PyCrustShell import Shell"  Or maybe
PyCrust.__init__.py could just import the major classes into it's namespace
so we just have to use "import PyCrust" and then use "PyCrust.Shell"