Comment 3 for bug 410098

I may have confused the issue originally reported by Shawn Willden with this issue that I experience in Tahoe-LAFS: http://allmydata.org/trac/tahoe/ticket/806 .

Shawn reported that he traced the problem to an empty __init__.py file that is written into /var/lib/python-support/python2.5/twisted/plugins . But Tahoe-LAFS's problem is that an empty __init__.py is written into /var/lib/python-support/python2.5/twisted/__init__.py . I'm not entirely sure that it was the installation of nevow that did it, either. Are these two manifestations of the same problem, or two different problems?

See also http://article.gmane.org/gmane.comp.python.distutils.devel/7409 in which Josselin Mouette <joss <at> debian.org> seems to say that Twisted and/or Nevow should change the way they do things to avoid this bug. Is this bug in one of those awful "stalemates" that arise in open source where two different developers each refuse to change the way they do things, with the result that users who want to use both open source tools together have to work-around the breakage?