* Josselin Mouette <[EMAIL PROTECTED]> [2008-04-27 21:07:25 +0200]: > > - python-support could be modified to not use __init__.py for > > twisted/plugins. I don't know what are the consequences of such a > > modification > > Technically this is a very easy fix, but this is opening a can of worms: > if we add an exception for twisted, there will be no reason not to fix > any other broken package that comes up.
Instead of adding a specific exception for twisted/plugins, would it not be possible to implement some mechanism for informing python-support that a particular directory is *not* a namespace package, thus disabling the __init__.py generation for that directory? The "exception" would then need to be in any package installing such a directory, but this does not seem particularly onerous; and indeed, any package that uses the twisted plugin system will have this problem, so "twisted/plugins" is definitely not the only case that needs to be handled. > I think the real solution is to fix python-twisted to use python modules > directories as God intended them to be. Removing the __init__.py check > is a really simple change and will fix the issue as well. As glyph mentions, this isn't really an adequate solution. -- mithrandi, i Ainil en-Balandor, a faer Ambar
signature.asc
Description: Digital signature
