RetroSearch Browse

Fri May 7 00:29:01 EDT 2004 · http://mail.python.org/pipermail/python-dev/2004-May/044708.html

> Jewett, Jim J wrote:
> > Unfortunately, it breaks client code that did
> > 
> >     urlparse.uses_relative.append('my_protocol')
> > 
> > which was as close to a documented API as existed.
> 
> Why are you saying that (or: what does that mean)?
> 
> The uses_relative attribute of urlparse was never
> documented, AFAICT.
> 
> > (1)  Is this an OK breakage with the 2.4 switch?
> 
> If it wasn't documented, it is OK to break it, but
> it should be mentioned in whatsnew24.tex.

I have a different POV.  I don't think there is a compelling reason to
change this attribute into a set (I doubt it's so time-critical as to
make a difference) and given that the attribute isn't flagged as
"private" by having a name starting with underscore, I think the
change ought to be reverted.

--Guido van Rossum (home page: http://www.python.org/~guido/)

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2004-May/044708.html below:

[Python-Dev] what level of backward compatibility? how