[tahoe-lafs-trac-stream] [tahoe-lafs] #1443: use exocet instead of the builtin Python module loader

[tahoe-lafs]

#1443: use exocet instead of the builtin Python module loader
-----------------------------------------+---------------------------
 Reporter:  zooko                        |          Owner:  somebody
     Type:  enhancement                  |         Status:  new
 Priority:  minor                        |      Milestone:  undecided
Component:  packaging                    |        Version:  1.8.2
 Keywords:  setuptools packaging exocet  |  Launchpad Bug:
-----------------------------------------+---------------------------
 [https://launchpad.net/exocet exocet] is a replacement for the builtin
 Python module loader. It makes the module system no longer be a global
 (mutable) namespace, but instead each module has a separate namespace for
 the modules that it loads. This facilitates dependency injection e.g. for
 unit testing. It may be useful for various things. In general, the notion
 of eliminating a single global mutable namespace in favor of separate,
 narrowly-scoped namespaces sounds great!

 * [http://washort.twistedmatrix.com/2011/01/modules-in-python-good-bad-
 and-ugly.html Modules in Python: the Good, the Bad, and the Ugly]
 * [http://washort.twistedmatrix.com/2011/01/introducing-exocet.html
 Introducing Exocet]
 * [http://washort.twistedmatrix.com/2011/03/exocet-second-look.html
 Exocet: A Second Look]
 * exocet's
 [http://bazaar.launchpad.net/~washort/exocet/katamari/view/head:/README
 README]

 Over on ticket #1334, I pointed out in comment:15:ticket:1334 that exocet
 could facilitate blacklisting a module to test our dependencies, and
 davidsarah pointed out in comment:16:ticket:1334 that exocet itself
 requires pywin32 (oops).

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1443>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage