Kristján Valur Jónsson kristjan at ccpgames.com
Wed Sep 2 14:07:19 CEST 2009

• Previous message: [Python-Dev] default of returning None hurts performance?
• Next message: [Python-Dev] default of returning None hurts performance?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Not advocating a change, merely pointing out that it's how Ruby works.
K

> -----Original Message-----
> From: python-dev-bounces+kristjan=ccpgames.com at python.org
> [mailto:python-dev-bounces+kristjan=ccpgames.com at python.org] On Behalf
> Of Nick Coghlan
> Sent: 2. september 2009 11:12
> To: Greg Ewing
> Cc: python-dev at python.org
> Subject: Re: [Python-Dev] default of returning None hurts performance?


> It also means adding a debugging message, assertion, or otherwise
> side-effect free statement can change the return value of the function.
> Not cool.
> 

---

• Previous message: [Python-Dev] default of returning None hurts performance?
• Next message: [Python-Dev] default of returning None hurts performance?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list