Le vendredi 30 mai 2008 à 13:00 +0200, Tristan Seligmann a écrit : > > 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.
It is indeed possible to implement that, as already suggested in #459468. I don't like it because it is only a workaround for packages that *are* buggy. > > 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. His explanation is all but satisfactory. Installing two versions of a python package in different paths is always going to cause issues, and this workaround is merely working by accident. If plugins are really incompatible between versions, the very first thing to do is to version the directory containing them. Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `- our own. Resistance is futile.
signature.asc
Description: Ceci est une partie de message numériquement signée
