➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2006-12-19 01:01 by maxy, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| simplexmlrpcserver-allow_none.patch | maxy, 2006-12-19 01:01 | SimpleXMLRPCServer patch | ||
| Messages (3) | |||
|---|---|---|---|
| msg51577 - (view) | Author: Maximiliano Curia (maxy) | Date: 2006-12-19 01:01 | |
Using SimpleXMLRPCServer I've been having some problems when trying to use "None" values. Apparently it uses a "dumps" function from xmlrpclib to generate the response. This function does support "None" values, but needs an extra parameter to allow them. The patch attached adds a new parameter (allow_none) to the constructor of SimpleXMLRPCServer, that when set is passed to the xmlrpclib.dumps call. This fixes the problem in a consistent way with the usage of xmlrpclib. It might be a better solution to support "None" values by default in SimpleXMLRPCServer and xmlrpclib. The patch is for python 2.4, but should probably be ported to 2.5 and 2.6. Thanks. |
|||
| msg51578 - (view) | Author: Thomas Herve (therve) * | Date: 2007-03-06 13:53 | |
As it's a new feature, it can probably only be in 2.6. Otherwise, that seems good, are you willing to write tests for this ? |
|||
| msg51579 - (view) | Author: Collin Winter (collinwinter) *  |
Date: 2007-03-08 19:27 | |
Something like this (patch #893642) has already been applied and is present in Python 2.5+. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:21 | admin | set | github: 44360 |
| 2006-12-19 01:01:42 | maxy | create | |