Bug#418457: python-mechanize: new upstream version

Brian Sutherland jinty at web.de
Mon Apr 9 22:20:27 UTC 2007


On Mon, Apr 09, 2007 at 11:49:17PM +0200, Bernd Zeimetz wrote:
> Heya,
> > Please don't let this get into testing. Updating to a new mechanize now
> > has very likely broken zope3.
> >   
> 
> would it make sense to ship more than one version of mechanize, as it is
> done with python-snmp for example?

I once tried to actually tried to use python-snmp. It took me a long
time to figure out where was the code I should have been using.

> Breakign zope3 would not be a good
> idea, but not beeing able to use other packages because zope3 depends on
> older versions isn't good either.

Er, take my remarks in the time that I thought we were in. i.e. before
Etch was released.

But, yes Etch has been released !!Hooray!! So I don't have many
objections to uploading a new mechanize.

> 
> Cheers,
> 
> Bernd
> 
> -- 
> Bernd Zeimetz
> <bernd at bzed.de>                         <http://bzed.de/>
> 
> 

-- 
Brian Sutherland




More information about the pkg-zope-developers mailing list