[ python-Bugs-842600 ] xmlrpclib and backward compatibility

SourceForge.net noreply at sourceforge.net
Sun Aug 22 09:10:40 CEST 2004


Bugs item #842600, was opened at 2003-11-15 05:46
Message generated for change (Comment added) made by loewis
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=842600&group_id=5470

Category: Python Library
Group: Python 2.3
>Status: Closed
>Resolution: Duplicate
Priority: 5
Submitted By: George Yoshida (quiver)
Assigned to: Fredrik Lundh (effbot)
Summary: xmlrpclib and backward compatibility

Initial Comment:
This bug is related to patch #531629 "Add multicall 
support to xmlrpclib"
http://www.python.org/sf/531629

His applied patch includes 'yield' statement.
Is this OK?
I think xmlrpclib.py needs to keep compatible with 
older Python.

On the top of xmlrpclib.py there is a note:
# this version is designed to work with Python 1.5.2 
or newer.

I attached a patch to avoid 'yield' but this is a quick 
fix.
I'm not sure if this is the right approach.
There should be a better solution.

I've also changed the coding style of the previous 
change to be consistent with other parts of this 
script.

----------------------------------------------------------------------

>Comment By: Martin v. Löwis (loewis)
Date: 2004-08-22 09:10

Message:
Logged In: YES 
user_id=21627

Closed as a duplicate of #1009803. The patch attached really
doesn't work, as it raises the exceptions out of order. I'm
working on a proper patch to restore 2.1 compatbility.

----------------------------------------------------------------------

Comment By: Martin v. Löwis (loewis)
Date: 2003-11-19 20:43

Message:
Logged In: YES 
user_id=21627

Assigning to Fredrik, as he is listed as the maintainer in
PEP 291. My proposal would be to drop xmlrpclib from PEP
291, and closing this report as "Won't fix". I don't see the
need for this backwards compatibility.

Fredrik, if you consider compatibility with 1.5.2 still
desirable, please indicate so, and assign it back to me so I
can fix the new feature.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=842600&group_id=5470


More information about the Python-bugs-list mailing list