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

[Python-Dev] properties on modules?

[Python-Dev] properties on modules? [Python-Dev] properties on modules?Guido van Rossum guido@python.org
Mon, 13 Jan 2003 13:49:22 -0500
[NeilS]
> > > 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?

[Me]
> > The idea is not clear to me at all.  Why can't you say
> > 
> > now = lambda: time.time()

[Brian Q]
> Presumably, he would prefer this syntax:
> 
> start = time.now
> 
> to:
> 
> start = time.now()

Aha.

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

I have to agree with you -- I am -1 on such a feature.

--Guido van Rossum (home page: http://www.python.org/~guido/)



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