[Python-Dev] Inheritance vs composition in backcompat (PEP521) (original) (raw)
Guido van Rossum guido at python.org
Mon Oct 2 17:59:52 EDT 2017
- Previous message (by thread): [Python-Dev] Inheritance vs composition in backcompat (PEP521)
- Next message (by thread): [Python-Dev] Inheritance vs composition in backcompat (PEP521)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mon, Oct 2, 2017 at 2:52 PM, Koos Zevenhoven <k7hoven at gmail.com> wrote
I don't mind this (or Nathaniel ;-) being academic. The backwards incompatibility issue I've just described applies to any extension via composition, if the underlying type/protocol grows new members (like the CM protocol would have gained suspend and resume in PEP521).
Since you seem to have a good grasp on this issue, does PEP 550 suffer from the same problem? (Or PEP 555, for that matter? :-)
-- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20171002/e559acd1/attachment.html>
- Previous message (by thread): [Python-Dev] Inheritance vs composition in backcompat (PEP521)
- Next message (by thread): [Python-Dev] Inheritance vs composition in backcompat (PEP521)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]