mirror of https://github.com/mitsuhiko/flask.git
Browse Source
It is entirely sufficient to walk the MRO of the exception class, no need to check for classes re-appearing later on, no need to add the MRO of any superclass. * Python refuses point-blank to create a class with a circular MRO. * All classes in a superclass MRO *already* appear in the MRO of the derived type. Re-adding the contents of a superclass MRO is doing double work.pull/2074/head
Martijn Pieters
8 years ago
committed by
David Lord
1 changed files with 1 additions and 13 deletions
Loading…
Reference in new issue