MAL: > Hmm, I'd say it doesn't hurt leaving .append() as it is until > 2.0. fwiw, I definitely agree. I've spotted too many places where this change cause a program to silently misbehave, rather than blow up (PIL's JPEG plugin is just one example...). I suggest adding an explicit warning in the 1.6 docs, and removing it in the first post-1.6 release. appendnanny.py, anyone? </F>
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