This release introduces the support of extention types
(decimal, uuid, error, datetime, interval) in MessagePack,
various IProto features support (feature discovery and push
protocol) and major infrastructure updates (scm version
computation, full documentation for external and internal
API both as code docstrings and readthedocs HTML, deb and
RPM packages, and everything is processed with CI/CD pipelines).
Breaking changes
This release should not break any existing behavior.
New features
Backport ConnectionPool support for Python 3.6 (PR #245).
Support iproto feature discovery (#206).
Decimal type support (#203).
UUID type support (#202).
Support extra information for iproto errors (#232).
Error extension type support (#232).
Datetime type support and tarantool.Datetime type (#204, PR #252).
Tarantool datetime objects are decoded to tarantool.Datetime
type. tarantool.Datetime may be encoded to Tarantool datetime
objects.
You can create tarantool.Datetime objects either from
MessagePack data or by using the same API as in Tarantool:
tarantool.Datetime exposes year, month, day, hour,
minute, sec, nsec, timestamp and value (integer epoch time
with nanoseconds precision) properties if you need to convert
tarantool.Datetime to any other kind of datetime object:
Thus, if False, datetime is computed from timestamp
since epoch and then timezone is applied without any
convertion. In that case, dt.timestamp won't be equal to
initialization timestamp for all timezones with non-zero offset.
Since tarantool.Interval could contain month and year fields
and such operations could be ambiguous, you can use adjust field
to tune the logic. The behavior is the same as in Tarantool, see
Interval arithmetic RFC.
tarantool.IntervalAdjust.NONE -- only truncation toward the end of
month performed (default mode).
tarantool.IntervalAdjust.EXCESS -- overflow mode, without any snap
or truncation to the end of month, straight addition of days in month,
stopping over month boundaries if there is less number of days.
Overview
This release introduces the support of extention types (decimal, uuid, error, datetime, interval) in MessagePack, various IProto features support (feature discovery and push protocol) and major infrastructure updates (scm version computation, full documentation for external and internal API both as code docstrings and readthedocs HTML, deb and RPM packages, and everything is processed with CI/CD pipelines).
Breaking changes
This release should not break any existing behavior.
New features
Backport ConnectionPool support for Python 3.6 (PR #245).
Support iproto feature discovery (#206).
Decimal type support (#203).
UUID type support (#202).
Support extra information for iproto errors (#232).
Error extension type support (#232).
Datetime type support and tarantool.Datetime type (#204, PR #252).
Tarantool datetime objects are decoded to
tarantool.Datetime
type.tarantool.Datetime
may be encoded to Tarantool datetime objects.You can create
tarantool.Datetime
objects either from MessagePack data or by using the same API as in Tarantool:tarantool.Datetime
exposesyear
,month
,day
,hour
,minute
,sec
,nsec
,timestamp
andvalue
(integer epoch time with nanoseconds precision) properties if you need to converttarantool.Datetime
to any other kind of datetime object:Use
tzoffset
parameter to set up offset timezone:You may use
tzoffset
property to get timezone offset of a datetime object.Use
tz
parameter to set up timezone name:If both
tz
andtzoffset
is specified,tz
is used.You may use
tz
property to get timezone name of a datetime object.timestamp_since_utc_epoch
is a parameter to set timestamp convertion behavior for timezone-aware datetimes.If
False
(default), behaves similar to Tarantooldatetime.new()
:Thus, if
False
, datetime is computed from timestamp since epoch and then timezone is applied without any convertion. In that case,dt.timestamp
won't be equal to initializationtimestamp
for all timezones with non-zero offset.If
True
, behaves similar topandas.Timestamp
:Thus, if
True
, datetime is computed in a way thatdt.timestamp
will always be equal to initializationtimestamp
.Datetime interval type support and tarantool.Interval type (#229).
Tarantool datetime interval objects are decoded to
tarantool.Interval
type.tarantool.Interval
may be encoded to Tarantool interval objects.You can create
tarantool.Interval
objects either from MessagePack data or by using the same API as in Tarantool:Its attributes (same as in init API) are exposed, so you can use them if needed.
Datetime interval arithmetic support (#229).
Valid operations:
tarantool.Datetime
+tarantool.Interval
=tarantool.Datetime
tarantool.Datetime
-tarantool.Interval
=tarantool.Datetime
tarantool.Datetime
-tarantool.Datetime
=tarantool.Interval
tarantool.Interval
+tarantool.Interval
=tarantool.Interval
tarantool.Interval
-tarantool.Interval
=tarantool.Interval
Since
tarantool.Interval
could containmonth
andyear
fields and such operations could be ambiguous, you can useadjust
field to tune the logic. The behavior is the same as in Tarantool, see Interval arithmetic RFC.tarantool.IntervalAdjust.NONE
-- only truncation toward the end of month performed (default mode).tarantool.IntervalAdjust.EXCESS
-- overflow mode, without any snap or truncation to the end of month, straight addition of days in month, stopping over month boundaries if there is less number of days.tarantool.IntervalAdjust.LAST
-- mode when day snaps to the end of month, if happens.Full documentation of internal and external API (#67).
Bugfixes
Infrastructure