➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2009-09-16 23:33 by terry.reedy, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Messages (2) | |||
|---|---|---|---|
| msg92732 - (view) | Author: Terry J. Reedy (terry.reedy) *  |
Date: 2009-09-16 23:33 | |
3.3.3. Customizing class creation 3.1/3.2 docs say "If the metaclass keyword argument is based with the bases, it is used." (new version for 3.x) I presume 'based' was meant to be 'passed'. However, with that correction, would it really be correct? I presume the metaclass compatibility issue discussed in #1294232 for 2.x is still relevant for 3.x. The next line "Otherwise, if there is at least one base class, its metaclass is used." (same as for 2.x docs) does not say which 'its' is used if there is more than one. See paragraph above and #1294232. I do not know the actual rule well enough to improve the neglected suggestion in the referenced issue. |
|||
| msg94362 - (view) | Author: Georg Brandl (georg.brandl) * |
Date: 2009-10-22 16:08 | |
Fixed based/passed in r75616, the rest will be done for #1294232. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:53 | admin | set | github: 51176 |
| 2009-10-22 16:08:38 | georg.brandl | set | status: open -> closed resolution: fixed superseder: Error in metaclass search order messages: + msg94362 |
| 2009-09-16 23:33:31 | terry.reedy | create | |