Well, if you buy into the whole space time continium thing, "now" doesn't wiggle about of it's own accord. Of course "now" isn't the "now that was then"... I can see how one might think of "now" as an attribute. It's specific and unique for normal space and time, such as exists outside of computers ;) David LeBlanc Seattle, WA USA > -----Original Message----- > From: python-dev-admin@python.org [mailto:python-dev-admin@python.org]On > Behalf Of Ben Laurie > Sent: Monday, January 13, 2003 11:14 > To: Brian Quinlan > Cc: python-dev@python.org > Subject: Re: [Python-Dev] properties on modules? > > > Brian Quinlan wrote: > >>>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. > > Presumably because inutuition says properties should hold still, not > wiggle about of their own accord. > > Cheers, > > Ben. > > -- > http://www.apache-ssl.org/ben.html http://www.thebunker.net/ > > "There is no limit to what a man can do or how far he can go if he > doesn't mind who gets the credit." - Robert Woodruff > > > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev
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