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-January/032115.html below:

[Python-Dev] properties on modules?

[Python-Dev] properties on modules? [Python-Dev] properties on modules?Brian Quinlan brian@sweetapp.com
Mon, 13 Jan 2003 10:49:12 -0800
> > It would be really cool if this worked:
> >
> > import time
> > now = property(lambda m: time.time())
> >
> > Obviously a silly example but I hope the idea is clear.  Is there a
> > reason this couldn't be made to work?
> 
> The idea is not clear to me at all.  Why can't you say
> 
> now = lambda: time.time()

Presumably, he would prefer this syntax:

start = time.now

to:

start = time.now()

The .NET framework implements "now" as a property rather than a function
and I find it distasteful for some reason. 

Cheers,
Brian




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