Message147399
| Author | flox |
|---|---|
| Recipients | effbot, fdrake, flox, skip.montanaro |
| Date | 2011-11-10.08:31:38 |
| SpamBayes Score | 9.122328e-05 |
| Marked as misclassified | No |
| Message-id | <1320913899.17.0.916086444056.issue13297@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Maybe a flag "use_builtin_types" is preferred? It should implies both `bytes` and `datetime.datetime` are used for presenting data received. I don't see a use case where we would like to have `bytes` for binary data but keep `xmlrpc.client.DateTime` for date objects. Becomes obsolete, if this change is done: - xmlrpc.client.Binary - xmlrpc.client.DateTime - use_datetime flag of `ServerProxy` class and `loads` function I'm not sure it's necessary to deprecate things here. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-11-10 08:31:39 | flox | set | recipients: + flox, fdrake, effbot, skip.montanaro |
| 2011-11-10 08:31:39 | flox | set | messageid: <1320913899.17.0.916086444056.issue13297@psf.upfronthosting.co.za> |
| 2011-11-10 08:31:38 | flox | link | issue13297 messages |
| 2011-11-10 08:31:38 | flox | create | |