[Python-Dev] Backward incompatible API changes in the pydoc module (original) (raw)
Georg Brandl g.brandl at gmx.net
Mon Nov 8 17:13:45 CET 2010
- Previous message: [Python-Dev] Backward incompatible API changes in the pydoc module
- Next message: [Python-Dev] Backward incompatible API changes in the pydoc module
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Am 08.11.2010 17:02, schrieb Éric Araujo:
Hi Nick,
If there is no enormous difficulty in maintaining compatibility, I think the usual deprecation process should be followed. We don’t know who is using pydoc as a library, so let’s play safe and not risk breaking their code (especially considering that it must not have been easy to write code extending pydoc :). BTW, doesn’t the process start with PendingDeprecationWarnings, then DeprecationWarnings?
PendingDeprecationWarnings only make sense for larger changes, especially now that bot Pending and normal DeprecationWarnings are silent by default. See PEP 387 (which is only a draft though).
Georg
- Previous message: [Python-Dev] Backward incompatible API changes in the pydoc module
- Next message: [Python-Dev] Backward incompatible API changes in the pydoc module
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]