Introducing a new set of duplicate type names and deprecating old ones causes a certain amount of disruption. Given the age of the types module, the disruption is likely to be greater than any potential benefit that could be realized. Plenty of people will have to incur the transition costs, but no one will likely find the benefit to be perceptible. Suggest rejecting this PEP and making a note for Py3.0 to either sync-up the type names or abandon the types module entirely. Raymond
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