On 2018-04-20 12:02, Jeroen Demeyer wrote: > One solution to improve backwards compatibility would be to duplicate > some classes. For example, make a separate class for bound methods in > extension types, which would be literally a duplicate of the existing > types.MethodType class (possibly with a different name). In other words, > a bound method of an extension type would work exactly the same way as > an existing bound method but it would artificially be a different class > for the benefit of non-duck-typing. I elaborated on this: https://www.python.org/dev/peps/pep-0575/#two-phase-implementation
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