>>>>> "GvR" == Guido van Rossum <[EMAIL PROTECTED]> writes: GvR> We use long names for most things except local variables in the GvR> Python source code, and it definitely makes the code more GvR> accessible to part-time developers. And let's not confuse part-time developers with people who send "uninformed patches." The cognitive burden of remembering every project's obscure naming conventions limits contributions from bright people who don't devote all their time to the project. I could rant about good design and things that make us smart, but I'll avoid that. Jeremy
- Re: Anachronistic Acronyms in Parrot? Simon Cozens
- Re: Anachronistic Acronyms in Parrot? Guido van Rossum
- Re: Anachronistic Acronyms in Parrot? boris
- Re: Anachronistic Acronyms in Parrot? Simon Cozens
- Re: Anachronistic Acronyms in Parrot? Simon Cozens
- Re: Anachronistic Acronyms in Parrot? David Beazley
- Re: Anachronistic Acronyms in Parrot? Donal K. Fellows
- Re: Anachronistic Acronyms in Parrot? Dave Mitchell
- Re: Anachronistic Acronyms in Parrot? David Cantrell
- Re: Anachronistic Acronyms in Parrot? Andrei Zmievski
- Re: Anachronistic Acronyms in Parrot? Jeremy Hylton
- Re: Anachronistic Acronyms in Parrot? Nathan Torkington
- Re: Anachronistic Acronyms in Parrot? raptor
- Re: Anachronistic Acronyms in Parrot? Dan Sugalski
- Re: Anachronistic Acronyms in Parrot? Guido van Rossum
- Re: Anachronistic Acronyms in Parrot? Dan Sugalski
- Re: Anachronistic Acronyms in Parrot? Yukihiro Matsumoto
- Re: Anachronistic Acronyms in Parrot? Paul Prescod
- Re: Anachronistic Acronyms in Parrot? Donal K. Fellows
- Re: Anachronistic Acronyms in Parrot? Dan Sugalski
- Re: Anachronistic Acronyms in Parrot? Paul Prescod
