A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/1999-September/000928.html below:

[Python-Dev] Relative Package Imports

[Python-Dev] Relative Package Imports [Python-Dev] Relative Package ImportsBarry A. Warsaw bwarsaw@cnri.reston.va.us (Barry A. Warsaw)
Wed, 15 Sep 1999 14:46:44 -0400 (EDT)
    JF> Zope products are python packages installed as sub-packages of
    JF> the Zope 'Products' packages.  Products are generally
    JF> self-contained.  If they need anything that's not part of
    JF> standard Python or standard Zope, they need to include it or
    JF> install what they need in a sub-package of another Zope
    JF> package, 'Shared'.

Jim, from your description, it sounds like Zope should be putting both
the `Shared' and possibly `Products' directories on sys.path.  Maybe
it does and I'm still missing your point.

However if they are not, then wouldn't this solve your problem?  A
user would drop the kjParsing directory into Shared, and then all the
import kjParsing.kjParser statements would Just Work.

-Barry



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