Re: [Python-Dev] to rename or not...

2013-07-31 Thread Ronald Oussoren
On 31 Jul, 2013, at 10:09, Antoine Pitrou wrote: > Le Wed, 31 Jul 2013 08:15:50 +0200, > Ronald Oussoren a écrit : >> >> Because of this I'd like to introduce a new API in plistlib that >> fixes both problems. In particular: >> >> * Add 'load', 'loads', 'dump' and 'dumps', those use "bytes" f

Re: [Python-Dev] to rename or not...

2013-07-31 Thread R. David Murray
On Wed, 31 Jul 2013 20:39:10 +1200, Greg Ewing wrote: > Ronald Oussoren wrote: > > * Add 'load', 'loads', 'dump' and 'dumps', those use "bytes" for binary data > > by default > > > > * Keep and deprecate "readPlist", "writePlist" and the their string > > equivalents, those still use Data objects

Re: [Python-Dev] to rename or not...

2013-07-31 Thread Greg Ewing
Ronald Oussoren wrote: * Add 'load', 'loads', 'dump' and 'dumps', those use "bytes" for binary data by default * Keep and deprecate "readPlist", "writePlist" and the their string equivalents, those still use Data objects +1, makes sense to me. -- Greg _

Re: [Python-Dev] to rename or not...

2013-07-31 Thread Antoine Pitrou
Le Wed, 31 Jul 2013 08:15:50 +0200, Ronald Oussoren a écrit : > > Because of this I'd like to introduce a new API in plistlib that > fixes both problems. In particular: > > * Add 'load', 'loads', 'dump' and 'dumps', those use "bytes" for > binary data by default > > * Keep and deprecate "readPl

[Python-Dev] to rename or not...

2013-07-30 Thread Ronald Oussoren
Hi, The relevant issue for this question is Plistlib contains object serialization logic that is in spirit simular to json and pickle, but has a different output format and different limitations. The functions in the module don't reflect that though, they are