Additionally:
As Pyro4 is substantially different from Pyro3, and there will never be a compatibility
layer, it is probably best to have 2 differently named debian packages as well?
pyro - Pyro 3.x
pyro4 - Pyro 4.x
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589172
Alas, it seems that Pyro 4.x has been included in the recent debian squeeze release as
package 'pyro'... As the above bug report states, that is unfortunate because of
backward compatibility breakage.
http://packages.debian.org/squeeze/pyro
Pyro4 is still in flux quite a bit. The 'pyro' package in debian really should be the
Pyro 3.x series instead of 4.x.
Please advise: I *think* I have done my part by renaming the toplevel package to Pyro4,
but as I'm not the creator/maintainer of the debian package, I don't know how to proceed
with that.
--irmen
_______________________________________________
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team
