[Zope] Allow import of whole filesystem class hierarchy?

[Kirk Strauser]

My company has a Zope server that has no editing rights for external 
persons - only employees have management permissions.  We also have a 
company-specific hierarchy of several hundred Python modules that I'd like 
to access from Zope.  Rather than modifying each and every module as per 
the instructions in the "Security" chapter of the ZDG, is there a way to 
say "allow the import of any module inside this part of $PYTHONPATH"?

Oh, for those curious: part of the reason for moving code from Zope Python 
scripts and into filesystem code is that my company has officially adopted 
Python as our new development platform for new projects.  I'm cranking out 
thousands of lines of code, and the Windows guys are tweaking it to run 
under IronPython.  The end goal is to have a library of code that runs 
under Unix, Windows, Mac, or wherever else we might want to explore, and 
then to write frontends to that library in whatever seems appropriate to 
the task.  For example, new web apps will be written with Zope calling 
those modules.  New GUI apps will be written with Visual Studio calling 
those modules.  Yay Zope and Python!  You're what broke us away from vendor 
lock-in!
-- 
Kirk Strauser
Daycos