Rework our implementation of tarantool.Datetime class. Previously it had relied on pandas.Timestamp and pandas.Timedelta. There were user complaints about pandas as a requirement since it's rather heavy. Now our implementation of datetime uses built-in datetime.datetime, datetime.timedelta and some other built-in tools.
It is expected that the implementation change wouldn't affect users, but some minor behavior traits were broken in this patch:
Now we rely on datetime argument validation which differs from the pandas one. For example, it doesn't allow overflows for fields. Exceptions that user may receive from internal datetime are, of course, had changed as well.
We drop the support of __eq__ for pandas.Timestamp. We simply compared underlying pandas.Timestamp with argument one, and now it's impossible. If the feature would be useful later, we may implement the comparison in some compatible way.
__repr__ has been changed since internal representation has been changed as well.
Rework our implementation of tarantool.Datetime class. Previously it had relied on pandas.Timestamp and pandas.Timedelta. There were user complaints about pandas as a requirement since it's rather heavy. Now our implementation of datetime uses built-in datetime.datetime, datetime.timedelta and some other built-in tools.
It is expected that the implementation change wouldn't affect users, but some minor behavior traits were broken in this patch:
__eq__for pandas.Timestamp. We simply compared underlying pandas.Timestamp with argument one, and now it's impossible. If the feature would be useful later, we may implement the comparison in some compatible way.__repr__has been changed since internal representation has been changed as well.Closes #290