QDateTime¶
Synopsis¶
Functions¶
def
__eq__
(other)def
__ge__
(other)def
__gt__
(other)def
__le__
(other)def
__lt__
(other)def
__ne__
(other)def
__reduce__
()def
__repr__
()def
addDays
(days)def
addMSecs
(msecs)def
addMonths
(months)def
addSecs
(secs)def
addYears
(years)def
date
()def
daysTo
(arg__1)def
isDaylightTime
()def
isNull
()def
isValid
()def
msecsTo
(arg__1)def
offsetFromUtc
()def
secsTo
(arg__1)def
setDate
(date)def
setMSecsSinceEpoch
(msecs)def
setOffsetFromUtc
(offsetSeconds)def
setSecsSinceEpoch
(secs)def
setTime
(time)def
setTimeSpec
(spec)def
setTimeZone
(toZone)def
setTime_t
(secsSince1Jan1970UTC)def
setUtcOffset
(seconds)def
swap
(other)def
time
()def
timeSpec
()def
timeZone
()def
timeZoneAbbreviation
()def
toLocalTime
()def
toMSecsSinceEpoch
()def
toOffsetFromUtc
(offsetSeconds)def
toPython
()def
toSecsSinceEpoch
()def
toString
([format=Qt.TextDate])def
toString
(format)def
toString
(format, cal)def
toTimeSpec
(spec)def
toTimeZone
(toZone)def
toTime_t
()def
toUTC
()def
utcOffset
()
Static functions¶
def
currentDateTime
()def
currentDateTimeUtc
()def
currentMSecsSinceEpoch
()def
currentSecsSinceEpoch
()def
fromMSecsSinceEpoch
(msecs)def
fromMSecsSinceEpoch
(msecs, spec[, offsetFromUtc=0])def
fromMSecsSinceEpoch
(msecs, timeZone)def
fromSecsSinceEpoch
(secs, timeZone)def
fromSecsSinceEpoch
(secs[, spe=Qt.LocalTime[, offsetFromUtc=0]])def
fromString
(s, format)def
fromString
(s, format, cal)def
fromString
(s[, f=Qt.TextDate])def
fromTime_t
(secsSince1Jan1970UTC)def
fromTime_t
(secsSince1Jan1970UTC, spec[, offsetFromUtc=0])def
fromTime_t
(secsSince1Jan1970UTC, timeZone)
Detailed Description¶
A
QDateTime
object encodes a calendar date and a clock time (a “datetime”). It combines features of theQDate
andQTime
classes. It can read the current datetime from the system clock. It provides functions for comparing datetimes and for manipulating a datetime by adding a number of seconds, days, months, or years.
QDateTime
can describe datetimes with respect tolocal time
, toUTC
, to a specifiedoffset from UTC
or to a specifiedtime zone
, in conjunction with theQTimeZone
class. For example, a time zone of “Europe/Berlin” will apply the daylight-saving rules as used in Germany since 1970. In contrast, an offset from UTC of +3600 seconds is one hour ahead of UTC (usually written in ISO standard notation as “UTC+01:00”), with no daylight-saving offset or changes. When using either local time or a specified time zone, time-zone transitions such as the starts and ends of daylight-saving time (DST; but see below) are taken into account. The choice of system used to represent a datetime is described as its “timespec”.A
QDateTime
object is typically created either by giving a date and time explicitly in the constructor, or by using a static function such ascurrentDateTime()
orfromMSecsSinceEpoch()
. The date and time can be changed withsetDate()
andsetTime()
. A datetime can also be set using thesetMSecsSinceEpoch()
function that takes the time, in milliseconds, since 00:00:00 on January 1, 1970. ThefromString()
function returns aQDateTime
, given a string and a date format used to interpret the date within the string.
currentDateTime()
returns aQDateTime
that expresses the current time with respect to local time.currentDateTimeUtc()
returns aQDateTime
that expresses the current time with respect to UTC.The
date()
andtime()
functions provide access to the date and time parts of the datetime. The same information is provided in textual format by thetoString()
function.
QDateTime
provides a full set of operators to compare twoQDateTime
objects, where smaller means earlier and larger means later.You can increment (or decrement) a datetime by a given number of milliseconds using
addMSecs()
, seconds usingaddSecs()
, or days usingaddDays()
. Similarly, you can useaddMonths()
andaddYears()
. ThedaysTo()
function returns the number of days between two datetimes,secsTo()
returns the number of seconds between two datetimes, andmsecsTo()
returns the number of milliseconds between two datetimes. These operations are aware of daylight-saving time (DST) and other time-zone transitions, where applicable.Use
toTimeSpec()
to express a datetime in local time or UTC,toOffsetFromUtc()
to express in terms of an offset from UTC, ortoTimeZone()
to express it with respect to a general time zone. You can usetimeSpec()
to find out what time-spec aQDateTime
object stores its time relative to. When that isTimeZone
, you can usetimeZone()
to find out which zone it is using.Note
QDateTime
does not account for leap seconds.
Remarks¶
No Year 0¶
There is no year 0. Dates in that year are considered invalid. The year -1 is the year “1 before Christ” or “1 before current era.” The day before 1 January 1 CE is 31 December 1 BCE.
Range of Valid Dates¶
The range of values that
QDateTime
can represent is dependent on the internal storage implementation.QDateTime
is currently stored in a qint64 as a serial msecs value encoding the date and time. This restricts the date range to about +/- 292 million years, compared to theQDate
range of +/- 2 billion years. Care must be taken when creating aQDateTime
with extreme values that you do not overflow the storage. The exact range of supported values varies depending on theTimeSpec
and time zone.
Use of Timezones¶
QDateTime
uses the system’s time zone information to determine the current local time zone and its offset from UTC. If the system is not configured correctly or not up-to-date,QDateTime
will give wrong results.
QDateTime
likewise uses system-provided information to determine the offsets of other timezones from UTC. If this information is incomplete or out of date,QDateTime
will give wrong results. See theQTimeZone
documentation for more details.On modern Unix systems, this means
QDateTime
usually has accurate information about historical transitions (including DST, see below) whenever possible. On Windows, where the system doesn’t support historical timezone data, historical accuracy is not maintained with respect to timezone transitions, notably including DST.
Daylight-Saving Time (DST)¶
QDateTime
takes into account transitions between Standard Time and Daylight-Saving Time. For example, if the transition is at 2am and the clock goes forward to 3am, then there is a “missing” hour from 02:00:00 to 02:59:59.999 whichQDateTime
considers to be invalid. Any date arithmetic performed will take this missing hour into account and return a valid result. For example, adding one minute to 01:59:59 will get 03:00:00.The range of valid dates taking DST into account is 1970-01-01 to the present, and rules are in place for handling DST correctly until 2037-12-31, but these could change. For dates after 2037,
QDateTime
makes a best guess using the rules for year 2037, but we can’t guarantee accuracy; indeed, for any future date, the time-zone may change its rules before that date comes around. For dates before 1970,QDateTime
doesn’t take DST changes into account, even if the system’s time zone database provides that information, although it does take into account changes to the time-zone’s standard offset, where this information is available.
Offsets From UTC¶
There is no explicit size restriction on an offset from UTC, but there is an implicit limit imposed when using the
toString()
andfromString()
methods which use a [+|-]hh:mm format, effectively limiting the range to +/- 99 hours and 59 minutes and whole minutes only. Note that currently no time zone lies outside the range of +/- 14 hours.
- class PySide2.QtCore.QDateTime¶
PySide2.QtCore.QDateTime(arg__1)
Note
This constructor is deprecated.
PySide2.QtCore.QDateTime(arg__1, arg__2[, spec=Qt.LocalTime])
PySide2.QtCore.QDateTime(date, time, spec, offsetSeconds)
PySide2.QtCore.QDateTime(date, time, timeZone)
PySide2.QtCore.QDateTime(other)
PySide2.QtCore.QDateTime(arg__1, arg__2, arg__3, arg__4, arg__5, arg__6)
PySide2.QtCore.QDateTime(arg__1, arg__2, arg__3, arg__4, arg__5, arg__6, arg__7[, arg__8=Qt.LocalTime])
- param date:
- param time:
- param timeZone:
- param arg__1:
- param arg__2:
- param other:
- param arg__3:
int
- param spec:
- param arg__4:
int
- param arg__5:
int
- param arg__6:
int
- param arg__7:
int
- param arg__8:
int
- param offsetSeconds:
int
Constructs a null datetime (i.e. null date and null time). A null datetime is invalid, since the date is invalid.
See also
Constructs a datetime with the given
date
andtime
, using the time specification defined byspec
andoffsetSeconds
seconds.If
date
is valid andtime
is not, the time will be set to midnight.If the
spec
is notOffsetFromUTC
thenoffsetSeconds
will be ignored.If the
spec
isOffsetFromUTC
andoffsetSeconds
is 0 then thetimeSpec()
will be set toUTC
, i.e. an offset of 0 seconds.If
spec
isTimeZone
then the spec will be set toLocalTime
, i.e. the current system time zone. To create aTimeZone
datetime use the correct constructor.
- PySide2.QtCore.QDateTime.YearRange¶
This enumerated type describes the range of years (in the Gregorian calendar) representable by
QDateTime
:Constant
Description
QDateTime.YearRange.First
The later parts of this year are representable
QDateTime.YearRange.Last
The earlier parts of this year are representable
All dates strictly between these two years are also representable. Note, however, that the Gregorian Calendar has no year zero.
New in version 5.14.
- PySide2.QtCore.QDateTime.__reduce__()¶
- Return type:
object
- PySide2.QtCore.QDateTime.__repr__()¶
- Return type:
object
- PySide2.QtCore.QDateTime.addDays(days)¶
- Parameters:
days – int
- Return type:
Returns a
QDateTime
object containing a datetimendays
days later than the datetime of this object (or earlier ifndays
is negative).If the
timeSpec()
isLocalTime
and the resulting date and time fall in the Standard Time to Daylight-Saving Time transition hour then the result will be adjusted accordingly, i.e. if the transition is at 2am and the clock goes forward to 3am and the result falls between 2am and 3am then the result will be adjusted to fall after 3am.See also
- PySide2.QtCore.QDateTime.addMSecs(msecs)¶
- Parameters:
msecs – int
- Return type:
Returns a
QDateTime
object containing a datetimemsecs
milliseconds later than the datetime of this object (or earlier ifmsecs
is negative).If this datetime is invalid, an invalid datetime will be returned.
See also
- PySide2.QtCore.QDateTime.addMonths(months)¶
- Parameters:
months – int
- Return type:
Returns a
QDateTime
object containing a datetimenmonths
months later than the datetime of this object (or earlier ifnmonths
is negative).If the
timeSpec()
isLocalTime
and the resulting date and time fall in the Standard Time to Daylight-Saving Time transition hour then the result will be adjusted accordingly, i.e. if the transition is at 2am and the clock goes forward to 3am and the result falls between 2am and 3am then the result will be adjusted to fall after 3am.See also
- PySide2.QtCore.QDateTime.addSecs(secs)¶
- Parameters:
secs – int
- Return type:
Returns a
QDateTime
object containing a datetimes
seconds later than the datetime of this object (or earlier ifs
is negative).If this datetime is invalid, an invalid datetime will be returned.
See also
- PySide2.QtCore.QDateTime.addYears(years)¶
- Parameters:
years – int
- Return type:
Returns a
QDateTime
object containing a datetimenyears
years later than the datetime of this object (or earlier ifnyears
is negative).If the
timeSpec()
isLocalTime
and the resulting date and time fall in the Standard Time to Daylight-Saving Time transition hour then the result will be adjusted accordingly, i.e. if the transition is at 2am and the clock goes forward to 3am and the result falls between 2am and 3am then the result will be adjusted to fall after 3am.See also
- static PySide2.QtCore.QDateTime.currentDateTime()¶
- Return type:
Returns the current datetime, as reported by the system clock, in the local time zone.
- static PySide2.QtCore.QDateTime.currentDateTimeUtc()¶
- Return type:
Returns the current datetime, as reported by the system clock, in UTC.
- static PySide2.QtCore.QDateTime.currentMSecsSinceEpoch()¶
- Return type:
int
Returns the number of milliseconds since 1970-01-01T00:00:00 Universal Coordinated Time. This number is like the POSIX time_t variable, but expressed in milliseconds instead.
- static PySide2.QtCore.QDateTime.currentSecsSinceEpoch()¶
- Return type:
int
Returns the number of seconds since 1970-01-01T00:00:00 Universal Coordinated Time.
See also
- PySide2.QtCore.QDateTime.date()¶
- Return type:
Returns the date part of the datetime.
See also
- PySide2.QtCore.QDateTime.daysTo(arg__1)¶
- Parameters:
arg__1 –
PySide2.QtCore.QDateTime
- Return type:
int
Returns the number of days from this datetime to the
other
datetime. The number of days is counted as the number of times midnight is reached between this datetime to theother
datetime. This means that a 10 minute difference from 23:55 to 0:05 the next day counts as one day.If the
other
datetime is earlier than this datetime, the value returned is negative.Example:
QDateTime startDate(QDate(2012, 7, 6), QTime(8, 30, 0)); QDateTime endDate(QDate(2012, 7, 7), QTime(16, 30, 0)); qDebug() << "Days from startDate to endDate: " << startDate.daysTo(endDate); startDate = QDateTime(QDate(2012, 7, 6), QTime(23, 55, 0)); endDate = QDateTime(QDate(2012, 7, 7), QTime(0, 5, 0)); qDebug() << "Days from startDate to endDate: " << startDate.daysTo(endDate); qSwap(startDate, endDate); // Make endDate before startDate. qDebug() << "Days from startDate to endDate: " << startDate.daysTo(endDate);
- static PySide2.QtCore.QDateTime.fromMSecsSinceEpoch(msecs)¶
- Parameters:
msecs – int
- Return type:
Returns a datetime whose date and time are the number of milliseconds,
msecs
, that have passed since 1970-01-01T00:00:00.000, Coordinated Universal Time (UTC
), and converted toLocalTime
. On systems that do not support time zones, the time will be set as if local time wereUTC
.Note that there are possible values for
msecs
that lie outside the valid range ofQDateTime
, both negative and positive. The behavior of this function is undefined for those values.See also
- static PySide2.QtCore.QDateTime.fromMSecsSinceEpoch(msecs, spec[, offsetFromUtc=0])
- Parameters:
msecs – int
spec –
TimeSpec
offsetFromUtc – int
- Return type:
Returns a datetime whose date and time are the number of milliseconds
msecs
that have passed since 1970-01-01T00:00:00.000, Coordinated Universal Time (UTC
) and converted to the givenspec
.Note that there are possible values for
msecs
that lie outside the valid range ofQDateTime
, both negative and positive. The behavior of this function is undefined for those values.If the
spec
is notOffsetFromUTC
then theoffsetSeconds
will be ignored. If thespec
isOffsetFromUTC
and theoffsetSeconds
is 0 then the spec will be set toUTC
, i.e. an offset of 0 seconds.If
spec
isTimeZone
then the spec will be set toLocalTime
, i.e. the current system time zone.See also
- static PySide2.QtCore.QDateTime.fromMSecsSinceEpoch(msecs, timeZone)
- Parameters:
msecs – int
timeZone –
PySide2.QtCore.QTimeZone
- Return type:
Returns a datetime whose date and time are the number of milliseconds
msecs
that have passed since 1970-01-01T00:00:00.000, Coordinated Universal Time (UTC
) and with the giventimeZone
.See also
- static PySide2.QtCore.QDateTime.fromSecsSinceEpoch(secs[, spe=Qt.LocalTime[, offsetFromUtc=0]])¶
- Parameters:
secs – int
spe –
TimeSpec
offsetFromUtc – int
- Return type:
Returns a datetime whose date and time are the number of seconds
secs
that have passed since 1970-01-01T00:00:00.000, Coordinated Universal Time (UTC
) and converted to the givenspec
.Note that there are possible values for
secs
that lie outside the valid range ofQDateTime
, both negative and positive. The behavior of this function is undefined for those values.If the
spec
is notOffsetFromUTC
then theoffsetSeconds
will be ignored. If thespec
isOffsetFromUTC
and theoffsetSeconds
is 0 then the spec will be set toUTC
, i.e. an offset of 0 seconds.If
spec
isTimeZone
then the spec will be set toLocalTime
, i.e. the current system time zone.See also
- static PySide2.QtCore.QDateTime.fromSecsSinceEpoch(secs, timeZone)
- Parameters:
secs – int
timeZone –
PySide2.QtCore.QTimeZone
- Return type:
Returns a datetime whose date and time are the number of seconds
secs
that have passed since 1970-01-01T00:00:00.000, Coordinated Universal Time (UTC
) and with the giventimeZone
.See also
- static PySide2.QtCore.QDateTime.fromString(s[, f=Qt.TextDate])¶
- Parameters:
s – str
f –
DateFormat
- Return type:
- static PySide2.QtCore.QDateTime.fromString(s, format)
- Parameters:
s – str
format – str
- Return type:
- static PySide2.QtCore.QDateTime.fromString(s, format, cal)
- Parameters:
s – str
format – str
cal –
PySide2.QtCore.QCalendar
- Return type:
Returns the
QDateTime
represented by thestring
, using theformat
given, or an invalid datetime if the string cannot be parsed.Uses the calendar
cal
if supplied, else Gregorian.In addition to the expressions, recognized in the format string to represent parts of the date and time, by
fromString()
andfromString()
, this method supports:Expression
Output
t
the timezone (for example “CEST”)
All other input characters will be treated as text. Any non-empty sequence of characters enclosed in single quotes will also be treated (stripped of the quotes) as text and not be interpreted as expressions.
time1 = QTime.fromString("131", "HHh") # time1 is 13:00:00 time1 = QTime.fromString("1apA", "1amAM") # time1 is 01:00:00 dateTime2 = QDateTime.fromString("M1d1y9800:01:02", "'M'M'd'd'y'yyhh:mm:ss") # dateTime is 1 January 1998 00:01:02
If the format is not satisfied, an invalid
QDateTime
is returned. If the format is satisfied butstring
represents an invalid date-time (e.g. in a gap skipped by a time-zone transition), an invalidQDateTime
is returned, whosetoMSecsSinceEpoch()
represents a near-by date-time that is valid. Passing that tofromMSecsSinceEpoch()
will produce a valid date-time that isn’t faithfully represented by the string parsed.The expressions that don’t have leading zeroes (d, M, h, m, s, z) will be greedy. This means that they will use two digits even if this will put them outside the range and/or leave too few digits for other sections.
dateTime = QDateTime.fromString("130", "Mm") # invalid
This could have meant 1 January 00:30.00 but the M will grab two digits.
Incorrectly specified fields of the
string
will cause an invalidQDateTime
to be returned. For example, consider the following code, where the two digit year 12 is read as 1912 (see the table below for all field defaults); the resulting datetime is invalid because 23 April 1912 was a Tuesday, not a Monday:QString string = "Monday, 23 April 12 22:51:41"; QString format = "dddd, d MMMM yy hh:mm:ss"; QDateTime invalid = QDateTime::fromString(string, format);
The correct code is:
QString string = "Tuesday, 23 April 12 22:51:41"; QString format = "dddd, d MMMM yy hh:mm:ss"; QDateTime valid = QDateTime::fromString(string, format);
For any field that is not represented in the format, the following defaults are used:
Field
Default value
Year
1900
Month
1 (January)
Day
1
Hour
0
Minute
0
Second
0
For example:
dateTime = QDateTime.fromString("1.30.1", "M.d.s") # dateTime is January 30 in 1900 at 00:00:01.
Note
If localized month and day names are used, please switch to using
system()
.toDateTime() asQDateTime
methods shall change to only recognize English (C locale) names at Qt 6.See also
- static PySide2.QtCore.QDateTime.fromTime_t(secsSince1Jan1970UTC)¶
- Parameters:
secsSince1Jan1970UTC –
uint
- Return type:
Returns a datetime whose date and time are the number of
seconds
that have passed since 1970-01-01T00:00:00, Coordinated Universal Time (UTC
) and converted toLocalTime
. On systems that do not support time zones, the time will be set as if local time wereUTC
.Note
This function is deprecated. Please use
fromSecsSinceEpoch()
in new code.See also
- static PySide2.QtCore.QDateTime.fromTime_t(secsSince1Jan1970UTC, spec[, offsetFromUtc=0])
- Parameters:
secsSince1Jan1970UTC –
uint
spec –
TimeSpec
offsetFromUtc – int
- Return type:
Returns a datetime whose date and time are the number of
seconds
that have passed since 1970-01-01T00:00:00, Coordinated Universal Time (UTC
) and converted to the givenspec
.If the
spec
is notOffsetFromUTC
then theoffsetSeconds
will be ignored. If thespec
isOffsetFromUTC
and theoffsetSeconds
is 0 then the spec will be set toUTC
, i.e. an offset of 0 seconds.Note
This function is deprecated. Please use
fromSecsSinceEpoch()
in new code.See also
- static PySide2.QtCore.QDateTime.fromTime_t(secsSince1Jan1970UTC, timeZone)
- Parameters:
secsSince1Jan1970UTC –
uint
timeZone –
PySide2.QtCore.QTimeZone
- Return type:
Returns a datetime whose date and time are the number of
seconds
that have passed since 1970-01-01T00:00:00, Coordinated Universal Time (UTC
) and with the giventimeZone
.Note
This function is deprecated. Please use
fromSecsSinceEpoch()
in new code.See also
- PySide2.QtCore.QDateTime.isDaylightTime()¶
- Return type:
bool
Returns if this datetime falls in Daylight-Saving Time.
If the
TimeSpec
is notLocalTime
orTimeZone
then will always return false.See also
- PySide2.QtCore.QDateTime.isNull()¶
- Return type:
bool
Returns
true
if both the date and the time are null; otherwise returnsfalse
. A null datetime is invalid.
- PySide2.QtCore.QDateTime.isValid()¶
- Return type:
bool
Returns
true
if both the date and the time are valid and they are valid in the currentTimeSpec
, otherwise returnsfalse
.If the
timeSpec()
isLocalTime
orTimeZone
then the date and time are checked to see if they fall in the Standard Time to Daylight-Saving Time transition hour, i.e. if the transition is at 2am and the clock goes forward to 3am then the time from 02:00:00 to 02:59:59.999 is considered to be invalid.
- PySide2.QtCore.QDateTime.msecsTo(arg__1)¶
- Parameters:
arg__1 –
PySide2.QtCore.QDateTime
- Return type:
int
Returns the number of milliseconds from this datetime to the
other
datetime. If theother
datetime is earlier than this datetime, the value returned is negative.Before performing the comparison, the two datetimes are converted to
UTC
to ensure that the result is correct if daylight-saving (DST) applies to one of the two datetimes and but not the other.Returns 0 if either datetime is invalid.
See also
- PySide2.QtCore.QDateTime.offsetFromUtc()¶
- Return type:
int
Returns this date-time’s Offset From UTC in seconds.
The result depends on
timeSpec()
:Qt::UTC
The offset is 0.Qt::OffsetFromUTC
The offset is the value originally set.Qt::LocalTime
The local time’s offset from UTC is returned.Qt::TimeZone
The offset used by the time-zone is returned.
For the last two, the offset at this date and time will be returned, taking account of Daylight-Saving Offset unless the date precedes the start of 1970. The offset is the difference between the local time or time in the given time-zone and UTC time; it is positive in time-zones ahead of UTC (East of The Prime Meridian), negative for those behind UTC (West of The Prime Meridian).
See also
- PySide2.QtCore.QDateTime.__ne__(other)¶
- Parameters:
other –
PySide2.QtCore.QDateTime
- Return type:
bool
Returns
true
if this datetime is different from theother
datetime; otherwise returnsfalse
.Two datetimes are different if either the date, the time, or the time zone components are different. Since 5.14, any invalid datetime is less than all valid datetimes.
See also
operator==()
- PySide2.QtCore.QDateTime.__lt__(other)¶
- Parameters:
other –
PySide2.QtCore.QDateTime
- Return type:
bool
- PySide2.QtCore.QDateTime.__le__(other)¶
- Parameters:
other –
PySide2.QtCore.QDateTime
- Return type:
bool
- PySide2.QtCore.QDateTime.__eq__(other)¶
- Parameters:
other –
PySide2.QtCore.QDateTime
- Return type:
bool
Returns
true
if this datetime is equal to theother
datetime; otherwise returnsfalse
.Since 5.14, all invalid datetimes are equal to one another and differ from all other datetimes.
See also
operator!=()
- PySide2.QtCore.QDateTime.__gt__(other)¶
- Parameters:
other –
PySide2.QtCore.QDateTime
- Return type:
bool
Returns
true
if this datetime is later than theother
datetime; otherwise returnsfalse
.
- PySide2.QtCore.QDateTime.__ge__(other)¶
- Parameters:
other –
PySide2.QtCore.QDateTime
- Return type:
bool
Returns
true
if this datetime is later than or equal to theother
datetime; otherwise returnsfalse
.
- PySide2.QtCore.QDateTime.secsTo(arg__1)¶
- Parameters:
arg__1 –
PySide2.QtCore.QDateTime
- Return type:
int
Returns the number of seconds from this datetime to the
other
datetime. If theother
datetime is earlier than this datetime, the value returned is negative.Before performing the comparison, the two datetimes are converted to
UTC
to ensure that the result is correct if daylight-saving (DST) applies to one of the two datetimes but not the other.Returns 0 if either datetime is invalid.
Example:
now = QDateTime.currentDateTime() xmas(QDate(now.date().year(), 12, 25), QTime(0, 0)) print("There are %d seconds to Christmas" % now.secsTo(xmas))
- PySide2.QtCore.QDateTime.setDate(date)¶
- Parameters:
date –
PySide2.QtCore.QDate
Sets the date part of this datetime to
date
. If no time is set yet, it is set to midnight. Ifdate
is invalid, thisQDateTime
becomes invalid.See also
- PySide2.QtCore.QDateTime.setMSecsSinceEpoch(msecs)¶
- Parameters:
msecs – int
Sets the date and time given the number of milliseconds
msecs
that have passed since 1970-01-01T00:00:00.000, Coordinated Universal Time (UTC
). On systems that do not support time zones this function will behave as if local time wereUTC
.Note that passing the minimum of
qint64
(std::numeric_limits<qint64>::min()
) tomsecs
will result in undefined behavior.See also
- PySide2.QtCore.QDateTime.setOffsetFromUtc(offsetSeconds)¶
- Parameters:
offsetSeconds – int
Sets the
timeSpec()
toOffsetFromUTC
and the offset tooffsetSeconds
. The datetime will refer to a different point in time.The maximum and minimum offset is 14 positive or negative hours. If
offsetSeconds
is larger or smaller than that, then the result is undefined.If
offsetSeconds
is 0 then thetimeSpec()
will be set toUTC
.See also
- PySide2.QtCore.QDateTime.setSecsSinceEpoch(secs)¶
- Parameters:
secs – int
Sets the date and time given the number of seconds
secs
that have passed since 1970-01-01T00:00:00.000, Coordinated Universal Time (UTC
). On systems that do not support time zones this function will behave as if local time wereUTC
.See also
- PySide2.QtCore.QDateTime.setTime(time)¶
- Parameters:
time –
PySide2.QtCore.QTime
Sets the time part of this datetime to
time
. Iftime
is not valid, this function sets it to midnight. Therefore, it’s possible to clear any set time in aQDateTime
by setting it to a defaultQTime
:QDateTime dt = QDateTime::currentDateTime(); dt.setTime(QTime());
See also
- PySide2.QtCore.QDateTime.setTimeSpec(spec)¶
- Parameters:
spec –
TimeSpec
Sets the time specification used in this datetime to
spec
. The datetime will refer to a different point in time.If
spec
isOffsetFromUTC
then thetimeSpec()
will be set toUTC
, i.e. an effective offset of 0.If
spec
isTimeZone
then the spec will be set toLocalTime
, i.e. the current system time zone.Example:
QDateTime local(QDateTime::currentDateTime()); qDebug() << "Local time is:" << local; QDateTime UTC(local); UTC.setTimeSpec(Qt::UTC); qDebug() << "UTC time is:" << UTC; qDebug() << "There are" << local.secsTo(UTC) << "seconds difference between the datetimes.";
See also
timeSpec()
setDate()
setTime()
setTimeZone()
TimeSpec
- PySide2.QtCore.QDateTime.setTimeZone(toZone)¶
- Parameters:
toZone –
PySide2.QtCore.QTimeZone
Sets the time zone used in this datetime to
toZone
. The datetime will refer to a different point in time.If
toZone
is invalid then the datetime will be invalid.See also
timeZone()
TimeSpec
- PySide2.QtCore.QDateTime.setTime_t(secsSince1Jan1970UTC)¶
- Parameters:
secsSince1Jan1970UTC –
uint
Sets the date and time given the number of
seconds
that have passed since 1970-01-01T00:00:00, Coordinated Universal Time (UTC
). On systems that do not support time zones this function will behave as if local time wereUTC
.Note
This function is deprecated. For new code, use
setSecsSinceEpoch()
.See also
- PySide2.QtCore.QDateTime.setUtcOffset(seconds)¶
- Parameters:
seconds – int
Note
This function is deprecated.
This method was added in 4.4 but never documented as public. It was replaced in 5.2 with public method
setOffsetFromUtc()
for consistency withQTimeZone
.This method should never be made public.
See also
- PySide2.QtCore.QDateTime.swap(other)¶
- Parameters:
other –
PySide2.QtCore.QDateTime
Swaps this datetime with
other
. This operation is very fast and never fails.
- PySide2.QtCore.QDateTime.time()¶
- Return type:
Returns the time part of the datetime.
See also
- PySide2.QtCore.QDateTime.timeSpec()¶
- Return type:
Returns the time specification of the datetime.
See also
setTimeSpec()
date()
time()
TimeSpec
- PySide2.QtCore.QDateTime.timeZone()¶
- Return type:
Returns the time zone of the datetime.
If the
timeSpec()
isLocalTime
then an instance of the current system time zone will be returned. Note however that if you copy this time zone the instance will not remain in sync if the system time zone changes.See also
setTimeZone()
TimeSpec
- PySide2.QtCore.QDateTime.timeZoneAbbreviation()¶
- Return type:
str
Returns the Time Zone Abbreviation for the datetime.
If the
timeSpec()
isUTC
this will be “UTC”.If the
timeSpec()
isOffsetFromUTC
this will be in the format “UTC[+-]00:00”.If the
timeSpec()
isLocalTime
then the host system is queried for the correct abbreviation.Note that abbreviations may or may not be localized.
Note too that the abbreviation is not guaranteed to be a unique value, i.e. different time zones may have the same abbreviation.
See also
- PySide2.QtCore.QDateTime.toLocalTime()¶
- Return type:
Returns a datetime containing the date and time information in this datetime, but specified using the
LocalTime
definition.Example:
QDateTime UTC(QDateTime::currentDateTimeUtc()); QDateTime local(UTC.toLocalTime()); qDebug() << "UTC time is:" << UTC; qDebug() << "Local time is:" << local; qDebug() << "No difference between times:" << UTC.secsTo(local);
See also
- PySide2.QtCore.QDateTime.toMSecsSinceEpoch()¶
- Return type:
int
Returns the datetime as the number of milliseconds that have passed since 1970-01-01T00:00:00.000, Coordinated Universal Time (
UTC
).On systems that do not support time zones, this function will behave as if local time were
UTC
.The behavior for this function is undefined if the datetime stored in this object is not valid. However, for all valid dates, this function returns a unique value.
See also
- PySide2.QtCore.QDateTime.toOffsetFromUtc(offsetSeconds)¶
- Parameters:
offsetSeconds – int
- Return type:
Returns a copy of this datetime converted to a spec of
OffsetFromUTC
with the givenoffsetSeconds
.If the
offsetSeconds
equals 0 then a UTC datetime will be returned
- PySide2.QtCore.QDateTime.toPython()¶
- Return type:
object
- PySide2.QtCore.QDateTime.toSecsSinceEpoch()¶
- Return type:
int
Returns the datetime as the number of seconds that have passed since 1970-01-01T00:00:00.000, Coordinated Universal Time (
UTC
).On systems that do not support time zones, this function will behave as if local time were
UTC
.The behavior for this function is undefined if the datetime stored in this object is not valid. However, for all valid dates, this function returns a unique value.
See also
- PySide2.QtCore.QDateTime.toString([format=Qt.TextDate])¶
- Parameters:
format –
DateFormat
- Return type:
str
This is an overloaded function.
Returns the datetime as a string in the
format
given.If the
format
isTextDate
, the string is formatted in the default way. The day and month names will be localized names using the system locale, i.e.system()
. An example of this formatting is “Wed May 20 03:40:13 1998”.If the
format
isISODate
, the string format corresponds to the ISO 8601 extended specification for representations of dates and times, taking the form yyyy-MM-ddTHH:mm:ss[Z|[+|-]HH:mm], depending on thetimeSpec()
of theQDateTime
. If thetimeSpec()
isUTC
, Z will be appended to the string; if thetimeSpec()
isOffsetFromUTC
, the offset in hours and minutes from UTC will be appended to the string. To include milliseconds in the ISO 8601 date, use theformat
ISODateWithMs
, which corresponds to yyyy-MM-ddTHH:mm:ss.zzz[Z|[+|-]HH:mm].The
format
optionsSystemLocaleDate
,SystemLocaleShortDate
andSystemLocaleLongDate
shall be removed in Qt 6. Their use should be replaced withShortFormat)
orLongFormat)
.The
format
optionsLocaleDate
,DefaultLocaleShortDate
andDefaultLocaleLongDate
shall be removed in Qt 6. Their use should be replaced withShortFormat)
orLongFormat)
.If the
format
isRFC2822Date
, the string is formatted following RFC 2822.If the datetime is invalid, an empty string will be returned.
Warning
The
ISODate
format is only valid for years in the range 0 to 9999.See also
- PySide2.QtCore.QDateTime.toString(format)
- Parameters:
format – str
- Return type:
str
- PySide2.QtCore.QDateTime.toString(format, cal)
- Parameters:
format – str
cal –
PySide2.QtCore.QCalendar
- Return type:
str
- PySide2.QtCore.QDateTime.toTimeSpec(spec)¶
- Parameters:
spec –
TimeSpec
- Return type:
Returns a copy of this datetime converted to the given time
spec
.If
spec
isOffsetFromUTC
then it is set toUTC
. To set to a spec ofOffsetFromUTC
usetoOffsetFromUtc()
.If
spec
isTimeZone
then it is set toLocalTime
, i.e. the local Time Zone.Example:
QDateTime local(QDateTime::currentDateTime()); QDateTime UTC(local.toTimeSpec(Qt::UTC)); qDebug() << "Local time is:" << local; qDebug() << "UTC time is:" << UTC; qDebug() << "No difference between times:" << local.secsTo(UTC);
See also
- PySide2.QtCore.QDateTime.toTimeZone(toZone)¶
- Parameters:
toZone –
PySide2.QtCore.QTimeZone
- Return type:
Returns a copy of this datetime converted to the given
timeZone
See also
- PySide2.QtCore.QDateTime.toTime_t()¶
- Return type:
uint
Returns the datetime as the number of seconds that have passed since 1970-01-01T00:00:00, Coordinated Universal Time (
UTC
).On systems that do not support time zones, this function will behave as if local time were
UTC
.Note
This function returns a 32-bit unsigned integer and is deprecated.
If the date is outside the range 1970-01-01T00:00:00 to 2106-02-07T06:28:14, this function returns -1 cast to an unsigned integer (i.e., 0xFFFFFFFF).
To get an extended range, use
toMSecsSinceEpoch()
ortoSecsSinceEpoch()
.
- PySide2.QtCore.QDateTime.toUTC()¶
- Return type:
Returns a datetime containing the date and time information in this datetime, but specified using the
UTC
definition.Example:
QDateTime local(QDateTime::currentDateTime()); QDateTime UTC(local.toUTC()); qDebug() << "Local time is:" << local; qDebug() << "UTC time is:" << UTC; qDebug() << "No difference between times:" << local.secsTo(UTC);
See also
- PySide2.QtCore.QDateTime.utcOffset()¶
- Return type:
int
Note
This function is deprecated.
This method was added in 4.4 but never documented as public. It was replaced in 5.1 with public method offsetFromUTC() for consistency with
QTimeZone
.This method should never be made public.
See also
offsetFromUTC()
© 2022 The Qt Company Ltd. Documentation contributions included herein are the copyrights of their respective owners. The documentation provided herein is licensed under the terms of the GNU Free Documentation License version 1.3 as published by the Free Software Foundation. Qt and respective logos are trademarks of The Qt Company Ltd. in Finland and/or other countries worldwide. All other trademarks are property of their respective owners.