reassign 474630 python-twisted-core
thanks

Le mercredi 16 avril 2008 à 19:57 +0200, Vincent Bernat a écrit :
> OoO Peu  avant le  début de  l'après-midi du mardi  15 avril  2008, vers
> 13:18, Matthias Klose <[EMAIL PROTECTED]> disait:
> 
> > this is not a bug in python-twisted-core; it is known that the
> > installation of modules/plugins in two different directories in
> > sys.path breaks things.  python-nevow must install in the same
> > location as python-twisted-core.
> 
> I don't really  see the relation between the new  behavior of twisted of
> not searching plugins in directories containing __init__.py and the fact
> that multiple modules providing plugins may break things.
> 
> Moreover,  your   proposed  fix  will  just  break   more  things  since
> python-support will add __init__.py file into the target directory.
> 
> I could fix this bug easily in python-nevow by removing this __init__.py
> file  in  postinst.  

Please don’t do that. It will be re-added later.

> However,  Sam   seems  to  report  a  more  general
> problem. Fixing it in python-nevow won't solve it.
> 
> If we  don't fix it  in twisted, we  could fix it in  python-support.  I
> don't really  understand why python-support adds  __init__.py files. The
> code says  that otherwise, python will  not take care  of package inside
> those directories. I  don't find a case where a package  is shipped as a
> package without __init__.py.

There are already several packages relying on the "namespace packages"
feature. The problem is when you have two modules, named foo.bar and
foo.baz, shipped in two different packages. If each of them shipped
foo/__init__.py, they couldn’t be installed together, and this is why
the empty __init__.py needs to be generated automaticaly.

> Josselin,   any  hint   on  this   problem?   I  assign   this  bug   to
> python-support.  If  you  don't  agree,  feel free  to  reassign  it  to
> python-nevow, I know how to fix it for python-nevow.

We’ve already discussed the issue on IRC before sam reported the bug,
and I still think the bug lies in python-twisted. Shipping modules in
the site-packages directory without making them available to the user
through 'import' is a clear abuse of the python API. 

Of course it is possible to work around that bug in python-support by
adding a specific exception for python-twisted, but this is a
last-resort measure, and I don’t want to do this when it is so easy to
fix twisted, by removing the __init__.py check that was recently added
by upstream.

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.

Attachment: signature.asc
Description: Ceci est une partie de message numériquement signée

Reply via email to