Martin v. Löwis wrote:
> I propose the following PEP for inclusion to Python 3.1.
> Please comment.
Would this support the following case:
I have a package called mortar, which defines useful stuff:
from mortar import content, ...
I now want to distribute large optional chunks separately, but ideally
so that the following will will work:
from mortar.rbd import ...
from mortar.zodb import ...
from mortar.wsgi import ...
Does the PEP support this? The only way I can currently think to do this
would result in:
from mortar import content,..
from mortar_rbd import ...
from mortar_zodb import ...
from mortar_wsgi import ...
...which looks a bit unsightly to me.
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4