On Sonntag 19 April 2009, you wrote: > I could be in addition... There should be one-- and preferably only one --obvious way to do it. (PEP 20)
> Perhaps there could be a .secs() function, which wouldn't require any
> overloading (and arguably make more sense type-wise)?
Please explain what you'd like to see fixed about time_{since,till}. If it is
that it returns milliseconds rather than seconds: I agree that that violates
the rule of least surprise. If you care enough to about this issue that you
want to manage a backward-compatible transition process (deprecation warnings,
doc updates, etc) to .seconds_since() (dropping .seconds_till in the process),
I'll take your patches.
> As is, the documentation for time_till and time_since isn't particularly
> accessible. Please at least convert the doc patch for that to the existing
> functions.
I've added some text to the documentation--let me know if it is to your
liking.
http://documen.tician.de/pycuda/driver.html#pycuda.driver.Event
Andreas
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ PyCuda mailing list [email protected] http://tiker.net/mailman/listinfo/pycuda_tiker.net
