> With the new surge of interest in metaclasses, I expect many > competing DBC implementations to come into existence. An early > commitment to one of them may preclude better ideas from > getting a chance. > > Another thought is that all of the machinery is in place to enable > a library of cooperating metaclass tools as envisioned by > Forman and Danforth's metaclass book. Any metaclass work > included in the distribution ought to make allowances for > being included side-by-side with threadsafety metaclasses, > logging metaclasses, auto property creators, auto delegators, > and such. > > In summary, I prefer that DBC not be PEPed. Instead, let things > grow on SF, the cookbook, the vaults, and private offerings. Good suggestions! This can be done many ways. Let's find ot which works best. --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4