-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jim Fulton wrote:
> Tres Seaver wrote:
> 
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Jim Fulton wrote:
>>
>>> Tim Peters wrote:
>>> ...
>>>
>>>
>>>> Well, I understand why that works, but it's not part of pprint's
>>>> contract either.
>>>
>>>
>>>
>>> What contract. :)
>>
>>
>>
>> The documented behavior, e.g. from '$ pydoc pprint' or the online
>> equivalent, http://python.org/doc/current/lib/module-pprint.html ?
> 
> 
> The Python documentation is incomplete in lots of places. It can
> hardly be considered a complete contract.

(Pulling numbers out of the air) ... 97% of Zope3 has less
well-specified contracts than the Python standard library.  Relying on
implementation details beyond the documented API is risky, period.  As
Tim notes, there isn't even any guarantee that dictionary keys are
*ordereable*.


Tres.
- --
===================================================================
Tres Seaver          +1 202-558-7113          [EMAIL PROTECTED]
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDpv3P+gerLs4ltQ4RAslWAKClKbqWIzHLobI1zb9+ciFhJgZkEACcDzQR
htZpQ+RaaeBAeujqPQxG9nI=
=B8fr
-----END PGP SIGNATURE-----
_______________________________________________
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to