tag:blogger.com,1999:blog-1897757324567699379.post1019073968559622105..comments2018-10-15T01:34:08.206-04:00Comments on Code Singer: Gary Poster's Blog: Don't use __*__ in Python unless you are hacking PythonAnonymoushttp://www.blogger.com/profile/02305364761685060789noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1897757324567699379.post-42422556627122475132009-03-11T03:30:00.000-04:002009-03-11T03:30:00.000-04:00Even though D above here has a nice example of why...Even though D above here has a nice example of why not to use your own __*__ functions. However I disagree with the part of the Python interpreter giving warnings about it. Like the title of this blog post says, if you are hacking you might want to overwrite certain built in __*__ functions (not saying this is a wise plan).<BR/><BR/>Some packages are built on this, so that would be breaking Simon Rivadahttps://www.blogger.com/profile/15163510969430086408noreply@blogger.comtag:blogger.com,1999:blog-1897757324567699379.post-12549053154253709102009-03-10T19:10:00.000-04:002009-03-10T19:10:00.000-04:00Here is a long-winded description of how I see the...Here is a long-winded description of how I see the current situation.<BR/><BR/>The Python developers are especially sensitive about changes to the language and go out of their way to demonstrate that making a change will not break existing code (too badly). For example, whenever a new reserved keyword is suggested, someone goes through the standard library and a few major projects (Zope, Twisted,Anonymoushttps://www.blogger.com/profile/11442714620753651697noreply@blogger.com