A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2003-October/039329.html below:

[Python-Dev] accumulator display syntax

[Python-Dev] accumulator display syntax [Python-Dev] accumulator display syntaxPhillip J. Eby pje at telecommunity.com
Wed Oct 22 22:12:09 EDT 2003
At 02:49 PM 10/23/03 +1300, Greg Ewing wrote:
>This would allow the current delayed-evaluation semantics
>to be kept as the default, while eliminating any need
>for using the default-argument hack when you don't
>want delayed evaluation.

Does anybody actually have a use case for delayed evaluation?  Why would 
you ever *want* it to be that way?  (Apart from the BDFL's desire to have 
the behavior resemble function behavior.)

And, if there's no use case for delayed evaluation, why make people jump 
through hoops to get the immediate binding?


More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4