[Python-Dev] source-level backward compatibility requirements - logging and apply() (original) (raw)

Vinay Sajip vinay_sajip at red-dove.com
Mon Dec 8 07:05:33 EST 2003

Sorry that this post starts a new thread - I have python-dev on digest mode and have not been following the list as closely as I ought to have done.

[Guido]

We could deprecate it in the docs but remove the silent warning which slows it down. Then we could leave it in the logging module until 3.0.

[Fred]

+42 Does this warrant a c2 release? I'm happy to make the changes right now.

+1 on deprecating apply() in the docs but not in the code. As Raymond originally said, the only "problem" with apply() and coerce() is that while they are useful, they are not useful in "mainstream" situations and could use up learning bandwidth. However, I think apply() is a useful idiom to have at one's disposal, though it only finds application here and there.

If Raymond's "all-builtins-have-at-least-one-friend" comment is not true for apply(), I'd like to nominate myself as that friend :-)

Regards,

Vinay Sajip

More information about the Python-Dev mailing list