Message200837
| Author |
ncoghlan |
| Recipients |
Arfrever, Trundle, benjamin.peterson, daniel.urban, docs@python, eric.araujo, eric.snow, meador.inge, ncoghlan, pitrou, rhettinger, skrah |
| Date |
2013年10月21日.20:27:32 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CADiSq7e_Gv8-JCd8qLtR-xTp-YYzart3Zsm69S57a2-C+NeCJw@mail.gmail.com> |
| In-reply-to |
<1382369882.06.0.385738542601.issue10977@psf.upfronthosting.co.za> |
| Content |
I haven't fully thought this one through, but perhaps we could:
- deprecate calling the current concrete APIs with subclasses (since doing
so may break subclass invariants)
- add "PyBaseDict_*" APIs (etc) that subclass implementations can call.
- offer a compatibility header for earlier versions that #defines the new
APIs back to the old ones
This would be 3.5 PEP territory, though. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2013年10月21日 20:27:33 | ncoghlan | set | recipients:
+ ncoghlan, rhettinger, pitrou, benjamin.peterson, eric.araujo, Arfrever, Trundle, skrah, meador.inge, daniel.urban, docs@python, eric.snow |
| 2013年10月21日 20:27:33 | ncoghlan | link | issue10977 messages |
| 2013年10月21日 20:27:32 | ncoghlan | create |
|