[Pythonmac-SIG] Fixing the documentation...

[has]

Bob Ippolito wrote:

[EasyDialogs]
>>Didn't see a waste dependency in the module; you sure about that? I've tried it and it still seems to be working okay (as well as it ever did, anyway), in which case immediate removal is not necessary. I wouldn't be averse to deprecating it just on general principle though. :)
>
>I thought it depended on W, which I think depends on waste.  Maybe I'm wrong though.  I've steered clear of all that stuff for quite a while.

Nope, just the Carbon extensions from what I can tell.


>A PyObjC-based replacement for EasyDialogs would be convenient though.  The problems with EasyDialogs are mostly just because the implementation is ancient.

Yep. The only catch about doing a set of simple, general-purpose in PyObjC is that you'd have PyObjC as a heavyweight dependency, and the main motivations for having something like ED are its simplicity and lightweightedness. It fills a low-end niche. The Nav module provides file dialogs, so really all that's needed is modern message, text entry and progress bar dialog implementations - preferably without requiring any new external dependencies.

But anyway... any replacement is some way off. For now it's just a case of deciding whether to leave ED and its documentation as-is or deprecate it. I say deprecate if other folks agree.


>>>plistlib works ok.  It used to be horribly broken, but the current version should be spec compliant.
>>
>>Including binary plists and all that? I've not tried it recently so wouldn't know.
>
>No, it does not support binary plists or NeXT style plists.  It supports XML plists.  Still useful though.

Sounds like a future reimplementation/replacement that uses the Core Foundation API instead of trying to parse things itself would be a wise move.

For now though, I'd say just add a short page to the documentation so folk know the plistlib module exists and put a note on it indicating its limitations.

Cheers,

has
-- 
http://freespace.virgin.net/hamish.sanderson/