On Sun, Jul 11, 2010 at 7:22 PM, rantingrick <rantingr...@gmail.com> wrote: > On Jul 11, 1:19 pm, Mark Dickinson <dicki...@gmail.com> wrote: > >> Okay. What fix do you propose? Would your fix maintain the identity >> "0 == False"? > > No because all integers should bool True. An integer is a value that > IS NOT empty and IS NOT None. Therefore the only logical way to handle > integer bool-ing is to say they are all True. > >> For bonus points, explain how you'd deal with any >> backwards compatibility problems that your fix introduces. > > We would't deal with backwards compatibility as this notion of bool(1) > == True and bool(0) == False if backwards way of thinking. Sure it > saves a few keystrokes but in the end only serves to obfuscate the > code and promote bad programming styles. WE SHOULD NEVER BE USING 1 IN > PLACE OF True AND 0 IN PLACE OF False! > >> Have you considered forking Python? That may be the way forward here. > > I have considered this many times in the past and continue to > consider it even today. I believe the Python language to be the best > high level language ever created up to this point. I also believe GvR > to be a true genius who has forged the path of all 21st century high > level languages. However, like all new inventions eventually the > bright shiny paint job starts to oxidize and expose the rotten and > rusting core that has been slowly disintegrating behind the scenes all > along. > > GvR stood on the shoulders of giants to reach the plateau of elegant > bliss that we know today as Python programming. As we all know > perfection will never be achieved, only lusted after forever and ever. > A perpetual game of cat and mouse. So maybe it is now time for the > next genius (Rick?) to stand on Guido's shoulders and reach the next > "cookie-jar-of-programming-enlightenment" one shelf higher than > Guido's cookies where found. > > Maybe it was fate that CPython 3000 would disturb so many folks as to > create a question in their minds... A splinter lodged deep within the > mind constantly tickling new never before thoughts to form... "Is > Python all it can be?". A lustful yearning to fix the warts that have > been ignored for far too long and were scarified at the alter of the > simplistic development cycle. > > But i think we are now at a crossroads people. We must forge the new > path and resist the temptation to circle around the familiar roads > endlessly. Heck *maybe* Guido himself is the architect of this change? > Maybe he *purposely* sowed discontent in an effort to ignite (or > reignite?) a passion for change within this community...? > > The black monolith is before us. We have reached a crossroads. In the > balance hangs the future of high level programming languages. Will we > understand what the portal is and take the leap of faith forward, or > just bang some bones around like toddlers for another 10,000 years? > Only time will tell...? Only time will tell...?
I literally laughed out loud as I read this. Go write some code, might help connect you back to reality. Geremy Condra -- http://mail.python.org/mailman/listinfo/python-list
