On Tue, Jul 30, 2013 at 8:28 PM, Christian Heimes wrote:
> Am 29.07.2013 21:48, schrieb Antoine Pitrou:
> > Ideally, we should run coverage runs on different systems (Unices,
> > Windows...) and merge the results together, so that we know which paths
> > are really uncovered.
>
> I don't that is e
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
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
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
_
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
