Timestamp.now() throws an Error

[jankatins]

Not sure if that is expected, but if it is expected it would be nice if the error message and the docsring of Timestamp.now() could be improved.

from pandas.tslib import Timestamp
Timestamp.now()

---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-45-634034a47269> in <module>()
----> 1 Timestamp.now()

C:\portabel\Python27\lib\site-packages\pandas\tslib.pyd in pandas.tslib.Timestamp.__new__ (pandas\tslib.c:5167)()

TypeError: __new__() takes at most 5 positional arguments (9 given)

[cancan101]

Timestamp.today() raises the same exception.

[jtratner]

Trivial implementations of this would just need to add these to the Cython
Timestamp (NOT to the _timestamp class). Not sure if time.time() is
actually accurate enough.

cdef now(self):
    return Timestamp(time.time() * 1e9)

cdef today(self):
    return Timestamp(datetime.today())

[jankatins]

It would also be nice if Timestamp.__float__() (probably simple setting __float__ = toordinal) could be implemented. That would make some special casing in https://github.com/yhat/ggplot/blob/master/ggplot/geoms/geom_density.py unnecessary.

[jtratner]

@JanSchulz care to take a stab at it? I don't think Cython will let you do __float__ = toordinal like that, so you'd probably need to define as:

cdef __float__(self):
     return self.toordinal()

[jreback]

@JanSchulz __float__ IMHO should raise, this is not an automatic conversion, with the ambiguity of the units, Timestamp.value is your best bet (in ns from epoch)

[cpcloud]

Arent these class methods in datetime? Also u can call datetime.now instead
of calling time.time

On Saturday, October 26, 2013, jreback wrote:

@JanSchulz https://github.com/JanSchulz float IMHO raise, this is
not an automatic conversion, with the ambiguity of the units,
Timestamp.value is your best bet (in ns from epoch)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5339#issuecomment-27154028
.

Best,
Phillip Cloud

[cancan101]

@cpcloud I think @jreback's solution was to have the class methods for Timestamp call down to the class methods for datetime and then to pass the resulting datetime object to the Timestamp constructor.

[jtratner]

datetime.now() has less resolution than time.time() right?

[cpcloud]

The precision of time is system dependent. The class method now, for
example, should return the same thing as Timestamp('now').

On Sunday, October 27, 2013, Jeff Tratner wrote:

datetime.now() has less resolution than time.time() right?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5339#issuecomment-27175693
.

Best,
Phillip Cloud