Re: Python to be replaced by the new language called Cookie !
On 2014-04-02, Chris Angelico wrote: > On Wed, Apr 2, 2014 at 3:15 PM, Dan Sommers wrote: >> On Wed, 02 Apr 2014 02:19:38 +1100, Chris Angelico wrote: >> >>> These improvements are absolutely critical to the language, and should >>> be made in Python 2.5.7, 2.6.9, and 3.0.2. Anyone using a newer >>> version of Python is paying the price for early adoption, and should >>> back-level immediately to a supported version. >> >> I'm using 2.8. Should I upgrade? > > Definitely. Python 2.8 is supported only on Windows XP 64-bit, and you > should upgrade to 32-bit Python; this will give you a 50% saving on > all pointers, and Python uses a lot of pointers, so your code will be > more efficient. And you'll save a _ton_ of money on ink. -- Grant Edwards grant.b.edwardsYow! Is my fallout shelter at termite proof? gmail.com -- https://mail.python.org/mailman/listinfo/python-list
Re: Python to be replaced by the new language called Cookie !
On 2/04/2014 3:42 PM, Chris Angelico wrote: Python 2.8 is supported only on Windows XP 64-bit, and you should upgrade to 32-bit Python That would be Python 1.4 -- https://mail.python.org/mailman/listinfo/python-list
Re: Python to be replaced by the new language called Cookie !
On Wed, Apr 2, 2014 at 3:15 PM, Dan Sommers wrote: > On Wed, 02 Apr 2014 02:19:38 +1100, Chris Angelico wrote: > >> These improvements are absolutely critical to the language, and should >> be made in Python 2.5.7, 2.6.9, and 3.0.2. Anyone using a newer >> version of Python is paying the price for early adoption, and should >> back-level immediately to a supported version. > > I'm using 2.8. Should I upgrade? Definitely. Python 2.8 is supported only on Windows XP 64-bit, and you should upgrade to 32-bit Python; this will give you a 50% saving on all pointers, and Python uses a lot of pointers, so your code will be more efficient. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Re: Python to be replaced by the new language called Cookie !
On Wed, 02 Apr 2014 02:19:38 +1100, Chris Angelico wrote: > These improvements are absolutely critical to the language, and should > be made in Python 2.5.7, 2.6.9, and 3.0.2. Anyone using a newer > version of Python is paying the price for early adoption, and should > back-level immediately to a supported version. I'm using 2.8. Should I upgrade? *ducking* -- https://mail.python.org/mailman/listinfo/python-list
Re: Python to be replaced by the new language called Cookie !
On Wed, Apr 2, 2014 at 1:32 AM, bob gailer wrote: > How about a "without" statement? > > without ]: > > > Within the Any mention of any identifier in the list raises the > specified or default (WithoutError) exception. In the interests of anti-patterns, we should adopt converses to all the classic patterns. Instead of Object Orientation, where you instantiate a few classes many times, we have Object Disorientation: every object is in a class of its own, and all objects rank equally. No more hierarchies, we have true equality! Also, we should recommend Dysfunctional Programming. Recursion is bad, and all instances of it should be turned into generators. Behold: # Functional programming style def spam(x): return "." + ham(x) def ham(y): return spam(y-1) if y else "!" def __main__(): print(spam(5)) __main__() # Dysfunctional style def spam(x): yield " " + next(ham(x)) def ham(y): if y: yield from spam(y-1) else: yield "!" def __main__(): print(next(spam(5))) __main__() Generators are inherently more Pythonic than recursion; after all, they have language-level support, while recursion doesn't even get the meager support of a "call self" opcode. Finally, Imperative Programming should be replaced with a much more courteous Request Programming. Instead of stating what you expect the program to do with a series of commands, you implement everything using the 'requests' module and the 'http.server' module. As an added bonus, you can very easily separate components of your program across multiple processes or even multiple computers, without any extra effort! These improvements are absolutely critical to the language, and should be made in Python 2.5.7, 2.6.9, and 3.0.2. Anyone using a newer version of Python is paying the price for early adoption, and should back-level immediately to a supported version. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Re: Python to be replaced by the new language called Cookie !
On 4/1/2014 4:20 AM, Skybuck Flying wrote: April Fools =D If you thought spaghetti code was bad, ... in December, 1973 R. Lawrence Clark proposed a new programming construct: COME FROM. See https://www.fortran.com/come_from.html What can we do in this new age of GOTOless programming do to match this incredible achievement? How about an "against" statement. Something like against throw arguments>? This doesn't really capture the same weird behavior of COME FROM, but it is a starter. How about a "without" statement? without ]: Within the Any mention of any identifier in the list raises the specified or default (WithoutError) exception. PEP writers: sharpen your quills! -- https://mail.python.org/mailman/listinfo/python-list
