tag:blogger.com,1999:blog-8699431508730375743.post6918557593324602416..comments2016-07-20T07:15:28.987-07:00Guido van Rossumhttp://www.blogger.com/profile/12821714508588242516noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-8699431508730375743.post-40195300237267154002009-07-13T13:06:37.672-07:002009-07-13T13:06:37.672-07:00Uzah, when will you stop beating your wife?Guido van Rossumhttps://www.blogger.com/profile/12821714508588242516noreply@blogger.comtag:blogger.com,1999:blog-8699431508730375743.post-83404004563338938782009-01-29T17:53:00.000-08:002009-01-29T17:53:00.000-08:00@Uzah:<BR/><BR/>b) what's wrong with open() ? it could conceivably return more than files. in 3.0, it returns an io.BufferedReader.<BR/><BR/>c) built in functions are not reserved words. you can define your own function called open, and you can use a local variable called open without any problems.<BR/><BR/>d) ugly underscore methods? methods of what? what are you talking about?<BR/><BR/>e) they all do very different things (except for has_key, which is going away).<BR/><BR/>f) it's nice precisely because it doesn't introduce new syntax.wlesliehttps://www.blogger.com/profile/12093160811053013157noreply@blogger.comtag:blogger.com,1999:blog-8699431508730375743.post-75493180653369034762009-01-28T20:34:00.000-08:002009-01-28T20:34:00.000-08:00Wish all these subversion repositories would quickly move onto a DVCS, like git.<BR/><BR/>Tired of using $ git svn, to slowly painfully accumulate history.Alokhttps://www.blogger.com/profile/00541962357236077809noreply@blogger.comtag:blogger.com,1999:blog-8699431508730375743.post-24271505817931999652009-01-26T20:31:00.000-08:002009-01-26T20:31:00.000-08:00a) how long did it take you to realize the "range" function is using huge amounts of memory when used in a for loop ? Did you not envison people needing more than a few iterations ? If there should only be one way to do something, why have both range and xrange ?<BR/><BR/>b) When are you going to add File.open ?<BR/><BR/>c) how many more special reserved words are you going to use for "built-in" functions, and are there going to be any "free" names left for people to use in their programs without fear of conflict ?<BR/><BR/>d) how many more upgy underscore methods are you going to hack into the "language" ?<BR/><BR/>e) why is everything about this "language" so hacky and provide a million different ways to do the same thing (get/getattr/hasattr/has_key/in/etc) ?<BR/><BR/>f) Is the motivation behind the "property" function/decorator/object? to win the most stupid syntax ever ?<BR/><BR/>when are you goingUzahhttps://www.blogger.com/profile/14414709262810832652noreply@blogger.comtag:blogger.com,1999:blog-8699431508730375743.post-72169331556645059802009-01-21T12:00:00.000-08:002009-01-21T12:00:00.000-08:00Spanish translation: <A HREF="http://www.juanjoconti.com.ar/2009/01/21/la-historia-de-python-cronologia-breve/" REL="nofollow">here</A>.Juanjo Contihttps://www.blogger.com/profile/00311238789779841975noreply@blogger.comtag:blogger.com,1999:blog-8699431508730375743.post-87369078538404205472009-01-20T17:38:00.000-08:002009-01-20T17:38:00.000-08:00I think the coolest way to visualize Python's history is through code_swarm:<BR/><BR/>http://www.vimeo.com/1093745Chrishttps://www.blogger.com/profile/16538671715523016085noreply@blogger.com