What timezone is datetime now python?

Aware and Naive Objects¶

Date and time objects may be categorized as “aware” or “naive” depending on whether or not they include timezone information.

With sufficient knowledge of applicable algorithmic and political time adjustments, such as time zone and daylight saving time information, an aware object can locate itself relative to other aware objects. An aware object represents a specific moment in time that is not open to interpretation. 1

A naive object does not contain enough information to unambiguously locate itself relative to other date/time objects. Whether a naive object represents Coordinated Universal Time [UTC], local time, or time in some other timezone is purely up to the program, just like it is up to the program whether a particular number represents metres, miles, or mass. Naive objects are easy to understand and to work with, at the cost of ignoring some aspects of reality.

For applications requiring aware objects, datetime and time objects have an optional time zone information attribute, tzinfo, that can be set to an instance of a subclass of the abstract tzinfo class. These tzinfo objects capture information about the offset from UTC time, the time zone name, and whether daylight saving time is in effect.

Only one concrete tzinfo class, the timezone class, is supplied by the datetime module. The timezone class can represent simple timezones with fixed offsets from UTC, such as UTC itself or North American EST and EDT timezones. Supporting timezones at deeper levels of detail is up to the application. The rules for time adjustment across the world are more political than rational, change frequently, and there is no standard suitable for every application aside from UTC.

Constants¶

The datetime module exports the following constants:

The smallest year number allowed in a date or datetime object. MINYEAR is 1.

The largest year number allowed in a date or datetime object. MAXYEAR is 9999.

Available Types¶

An idealized naive date, assuming the current Gregorian calendar always was, and always will be, in effect. Attributes: year, month, and day.

An idealized time, independent of any particular day, assuming that every day has exactly 24*60*60 seconds. [There is no notion of “leap seconds” here.] Attributes: hour, minute, second, microsecond, and tzinfo.

A combination of a date and a time. Attributes: year, month, day, hour, minute, second, microsecond, and tzinfo.

A duration expressing the difference between two date, time, or datetime instances to microsecond resolution.

An abstract base class for time zone information objects. These are used by the datetime and time classes to provide a customizable notion of time adjustment [for example, to account for time zone and/or daylight saving time].

A class that implements the tzinfo abstract base class as a fixed offset from the UTC.

New in version 3.2.

Objects of these types are immutable.

Subclass relationships:

object
    timedelta
    tzinfo
        timezone
    time
    date
        datetime

timedelta Objects¶

A timedelta object represents a duration, the difference between two dates or times.

All arguments are optional and default to 0. Arguments may be integers or floats, and may be positive or negative.

Only days, seconds and microseconds are stored internally. Arguments are converted to those units:

• A millisecond is converted to 1000 microseconds.

• A minute is converted to 60 seconds.

• An hour is converted to 3600 seconds.

• A week is converted to 7 days.

and days, seconds and microseconds are then normalized so that the representation is unique, with

• 0 delta = timedelta[ ... days=50, ... seconds=27, ... microseconds=10, ... milliseconds=29000, ... minutes=5, ... hours=8, ... weeks=2 ... ] >>> # Only days, seconds, and microseconds remain >>> delta datetime.timedelta[days=64, seconds=29156, microseconds=10]

  If any argument is a float and there are fractional microseconds, the fractional microseconds left over from all arguments are combined and their sum is rounded to the nearest microsecond using round-half-to-even tiebreaker. If no argument is a float, the conversion and normalization processes are exact [no information is lost].

  If the normalized value of days lies outside the indicated range, OverflowError is raised.

  Note that normalization of negative values may be surprising at first. For example:

  >>> from datetime import timedelta
  >>> d = timedelta[microseconds=-1]
  >>> [d.days, d.seconds, d.microseconds]
  [-1, 86399, 999999]
  

  Class attributes:

  timedelta.min¶

  The most negative timedelta object, timedelta[-999999999].

  timedelta.max¶

  The most positive timedelta object, timedelta[days=999999999, hours=23, minutes=59, seconds=59, microseconds=999999].

  timedelta.resolution¶

  The smallest possible difference between non-equal timedelta objects, timedelta[microseconds=1].

  Note that, because of normalization, timedelta.max > -timedelta.min. -timedelta.max is not representable as a timedelta object.

  Instance attributes [read-only]:

  Attribute

  Value

  days	Between -999999999 and 999999999 inclusive
  seconds	Between 0 and 86399 inclusive
  microseconds	Between 0 and 999999 inclusive

  Supported operations:

  Operation

  Result

  t1 = t2 + t3	Sum of t2 and t3. Afterwards t1-t2 == t3 and t1-t3 == t2 are true. [1]
  t1 = t2 - t3	Difference of t2 and t3. Afterwards t1 == t2 - t3 and t2 == t1 + t3 are true. [1][6]
  t1 = t2 * i or t1 = i * t2	Delta multiplied by an integer. Afterwards t1 // i == t2 is true, provided i != 0.
  	In general, t1 * i == t1 * [i-1] + t1 is true. [1]
  t1 = t2 * f or t1 = f * t2	Delta multiplied by a float. The result is rounded to the nearest multiple of timedelta.resolution using round-half-to-even.
  f = t2 / t3	Division [3] of overall duration t2 by interval unit t3. Returns a float object.
  t1 = t2 / f or t1 = t2 / i	Delta divided by a float or an int. The result is rounded to the nearest multiple of timedelta.resolution using round-half-to-even.
  t1 = t2 // i or t1 = t2 // t3	The floor is computed and the remainder [if any] is thrown away. In the second case, an integer is returned. [3]
  t1 = t2 % t3	The remainder is computed as a timedelta object. [3]
  q, r = divmod[t1, t2]	Computes the quotient and the remainder: q = t1 // t2 [3] and r = t1 % t2. q is an integer and r is a timedelta object.
  +t1	Returns a timedelta object with the same value. [2]
  -t1	equivalent to timedelta[-t1.days, -t1.seconds, -t1.microseconds], and to t1* -1. [1][4]
  abs[t]	equivalent to +t when t.days >= 0, and to -t when t.days >> timedelta[hours=-5] datetime.timedelta[days=-1, seconds=68400] >>> print[_] -1 day, 19:00:00 The expression t2 - t3 will always be equal to the expression t2 + [-t3] except when t3 is equal to timedelta.max; in that case the former will produce a result while the latter will overflow. In addition to the operations listed above, timedelta objects support certain additions and subtractions with date and datetime objects [see below]. Changed in version 3.2: Floor division and true division of a timedelta object by another timedelta object are now supported, as are remainder operations and the divmod[] function. True division and multiplication of a timedelta object by a float object are now supported. Comparisons of timedelta objects are supported, with some caveats. The comparisons == or != always return a bool, no matter the type of the compared object: >>> from datetime import timedelta >>> delta1 = timedelta[seconds=57] >>> delta2 = timedelta[hours=25, seconds=2] >>> delta2 != delta1 True >>> delta2 == 5 False For all other comparisons [such as ], when a timedelta object is compared to an object of a different type, TypeError is raised: >>> delta2 > delta1 True >>> delta2 > 5 Traceback [most recent call last]: File "", line 1, in TypeError: '>' not supported between instances of 'datetime.timedelta' and 'int' In Boolean contexts, a timedelta object is considered to be true if and only if it isn’t equal to timedelta[0]. Instance methods: timedelta.total_seconds[]¶ Return the total number of seconds contained in the duration. Equivalent to td / timedelta[seconds=1]. For interval units other than seconds, use the division form directly [e.g. td / timedelta[microseconds=1]]. Note that for very large time intervals [greater than 270 years on most platforms] this method will lose microsecond accuracy. New in version 3.2. Examples of usage: timedelta¶ An additional example of normalization: >>> # Components of another_year add up to exactly 365 days >>> from datetime import timedelta >>> year = timedelta[days=365] >>> another_year = timedelta[weeks=40, days=84, hours=23, ... minutes=50, seconds=600] >>> year == another_year True >>> year.total_seconds[] 31536000.0 Examples of timedelta arithmetic: >>> from datetime import timedelta >>> year = timedelta[days=365] >>> ten_years = 10 * year >>> ten_years datetime.timedelta[days=3650] >>> ten_years.days // 365 10 >>> nine_years = ten_years - year >>> nine_years datetime.timedelta[days=3285] >>> three_years = nine_years // 3 >>> three_years, three_years.days // 365 [datetime.timedelta[days=1095], 3] date Objects¶ A date object represents a date [year, month and day] in an idealized calendar, the current Gregorian calendar indefinitely extended in both directions. January 1 of year 1 is called day number 1, January 2 of year 1 is called day number 2, and so on. 2 class datetime.date[year, month, day]¶ All arguments are required. Arguments must be integers, in the following ranges: MINYEAR > d = date[2002, 12, 31] >>> d.replace[day=26] datetime.date[2002, 12, 26] date.timetuple[]¶ Return a time.struct_time such as returned by time.localtime[]. The hours, minutes and seconds are 0, and the DST flag is -1. d.timetuple[] is equivalent to: time.struct_time[[d.year, d.month, d.day, 0, 0, 0, d.weekday[], yday, -1]] where yday = d.toordinal[] - date[d.year, 1, 1].toordinal[] + 1 is the day number within the current year starting with 1 for January 1st. date.toordinal[]¶ Return the proleptic Gregorian ordinal of the date, where January 1 of year 1 has ordinal 1. For any date object d, date.fromordinal[d.toordinal[]] == d. date.weekday[]¶ Return the day of the week as an integer, where Monday is 0 and Sunday is 6. For example, date[2002, 12, 4].weekday[] == 2, a Wednesday. See also isoweekday[]. date.isoweekday[]¶ Return the day of the week as an integer, where Monday is 1 and Sunday is 7. For example, date[2002, 12, 4].isoweekday[] == 3, a Wednesday. See also weekday[], isocalendar[]. date.isocalendar[]¶ Return a named tuple object with three components: year, week and weekday. The ISO calendar is a widely used variant of the Gregorian calendar. 3 The ISO year consists of 52 or 53 full weeks, and where a week starts on a Monday and ends on a Sunday. The first week of an ISO year is the first [Gregorian] calendar week of a year containing a Thursday. This is called week number 1, and the ISO year of that Thursday is the same as its Gregorian year. For example, 2004 begins on a Thursday, so the first week of ISO year 2004 begins on Monday, 29 Dec 2003 and ends on Sunday, 4 Jan 2004: >>> from datetime import date >>> date[2003, 12, 29].isocalendar[] datetime.IsoCalendarDate[year=2004, week=1, weekday=1] >>> date[2004, 1, 4].isocalendar[] datetime.IsoCalendarDate[year=2004, week=1, weekday=7] Changed in version 3.9: Result changed from a tuple to a named tuple. date.isoformat[]¶ Return a string representing the date in ISO 8601 format, YYYY-MM-DD: >>> from datetime import date >>> date[2002, 12, 4].isoformat[] '2002-12-04' This is the inverse of date.fromisoformat[]. date.__str__[]¶ For a date d, str[d] is equivalent to d.isoformat[]. date.ctime[]¶ Return a string representing the date: >>> from datetime import date >>> date[2002, 12, 4].ctime[] 'Wed Dec 4 00:00:00 2002' d.ctime[] is equivalent to: time.ctime[time.mktime[d.timetuple[]]] on platforms where the native C ctime[] function [which time.ctime[] invokes, but which date.ctime[] does not invoke] conforms to the C standard. date.strftime[format]¶ Return a string representing the date, controlled by an explicit format string. Format codes referring to hours, minutes or seconds will see 0 values. For a complete list of formatting directives, see strftime[] and strptime[] Behavior. date.__format__[format]¶ Same as date.strftime[]. This makes it possible to specify a format string for a date object in formatted string literals and when using str.format[]. For a complete list of formatting directives, see strftime[] and strptime[] Behavior. Examples of Usage: date¶ Example of counting days to an event: >>> import time >>> from datetime import date >>> today = date.today[] >>> today datetime.date[2007, 12, 5] >>> today == date.fromtimestamp[time.time[]] True >>> my_birthday = date[today.year, 6, 24] >>> if my_birthday >> my_birthday datetime.date[2008, 6, 24] >>> time_to_birthday = abs[my_birthday - today] >>> time_to_birthday.days 202 More examples of working with date: >>> from datetime import date >>> d = date.fromordinal[730920] # 730920th day after 1. 1. 0001 >>> d datetime.date[2002, 3, 11] >>> # Methods related to formatting string output >>> d.isoformat[] '2002-03-11' >>> d.strftime["%d/%m/%y"] '11/03/02' >>> d.strftime["%A %d. %B %Y"] 'Monday 11. March 2002' >>> d.ctime[] 'Mon Mar 11 00:00:00 2002' >>> 'The {1} is {0:%d}, the {2} is {0:%B}.'.format[d, "day", "month"] 'The day is 11, the month is March.' >>> # Methods for to extracting 'components' under different calendars >>> t = d.timetuple[] >>> for i in t: ... print[i] 2002 # year 3 # month 11 # day 0 0 0 0 # weekday [0 = Monday] 70 # 70th day in the year -1 >>> ic = d.isocalendar[] >>> for i in ic: ... print[i] 2002 # ISO year 11 # ISO week number 1 # ISO day number [ 1 = Monday ] >>> # A date object is immutable; all operations produce a new object >>> d.replace[year=2005] datetime.date[2005, 3, 11] datetime Objects¶ A datetime object is a single object containing all the information from a date object and a time object. Like a date object, datetime assumes the current Gregorian calendar extended in both directions; like a time object, datetime assumes there are exactly 3600*24 seconds in every day. Constructor: class datetime.datetime[year, month, day, hour=0, minute=0, second=0, microsecond=0, tzinfo=None, *, fold=0]¶ The year, month and day arguments are required. tzinfo may be None, or an instance of a tzinfo subclass. The remaining arguments must be integers in the following ranges: MINYEAR >> datetime.fromisoformat['2011-11-04T00:05:23+04:00'] datetime.datetime[2011, 11, 4, 0, 5, 23, tzinfo=datetime.timezone[datetime.timedelta[seconds=14400]]] New in version 3.7. classmethod datetime.fromisocalendar[year, week, day]¶ Return a datetime corresponding to the ISO calendar date specified by year, week and day. The non-date components of the datetime are populated with their normal default values. This is the inverse of the function datetime.isocalendar[]. New in version 3.8. classmethod datetime.strptime[date_string, format]¶ Return a datetime corresponding to date_string, parsed according to format. This is equivalent to: datetime[*[time.strptime[date_string, format][0:6]]] ValueError is raised if the date_string and format can’t be parsed by time.strptime[] or if it returns a value which isn’t a time tuple. For a complete list of formatting directives, see strftime[] and strptime[] Behavior. Class attributes: datetime.min¶ The earliest representable datetime, datetime[MINYEAR, 1, 1, tzinfo=None]. datetime.max¶ The latest representable datetime, datetime[MAXYEAR, 12, 31, 23, 59, 59, 999999, tzinfo=None]. datetime.resolution¶ The smallest possible difference between non-equal datetime objects, timedelta[microseconds=1]. Instance attributes [read-only]: datetime.year¶ Between MINYEAR and MAXYEAR inclusive. datetime.month¶ Between 1 and 12 inclusive. datetime.day¶ Between 1 and the number of days in the given month of the given year. datetime.hour¶ In range[24]. datetime.minute¶ In range[60]. datetime.second¶ In range[60]. datetime.microsecond¶ In range[1000000]. datetime.tzinfo¶ The object passed as the tzinfo argument to the datetime constructor, or None if none was passed. datetime.fold¶ In [0, 1]. Used to disambiguate wall times during a repeated interval. [A repeated interval occurs when clocks are rolled back at the end of daylight saving time or when the UTC offset for the current zone is decreased for political reasons.] The value 0 [1] represents the earlier [later] of the two moments with the same wall time representation. New in version 3.6. Supported operations: Operation Result datetime2 = datetime1 + timedelta [1] datetime2 = datetime1 - timedelta [2] timedelta = datetime1 - datetime2 [3] datetime1 0, or backward if timedelta.days < 0. The result has the same tzinfo attribute as the input datetime, and datetime2 - datetime1 == timedelta after. OverflowError is raised if datetime2.year would be smaller than MINYEAR or larger than MAXYEAR. Note that no time zone adjustments are done even if the input is an aware object. Computes the datetime2 such that datetime2 + timedelta == datetime1. As for addition, the result has the same tzinfo attribute as the input datetime, and no time zone adjustments are done even if the input is aware. Subtraction of a datetime from a datetime is defined only if both operands are naive, or if both are aware. If one is aware and the other is naive, TypeError is raised. If both are naive, or both are aware and have the same tzinfo attribute, the tzinfo attributes are ignored, and the result is a timedelta object t such that datetime2 + t == datetime1. No time zone adjustments are done in this case. If both are aware and have different tzinfo attributes, a-b acts as if a and b were first converted to naive UTC datetimes first. The result is [a.replace[tzinfo=None] - a.utcoffset[]] - [b.replace[tzinfo=None] - b.utcoffset[]] except that the implementation never overflows. datetime1 is considered less than datetime2 when datetime1 precedes datetime2 in time. If one comparand is naive and the other is aware, TypeError is raised if an order comparison is attempted. For equality comparisons, naive instances are never equal to aware instances. If both comparands are aware, and have the same tzinfo attribute, the common tzinfo attribute is ignored and the base datetimes are compared. If both comparands are aware and have different tzinfo attributes, the comparands are first adjusted by subtracting their UTC offsets [obtained from self.utcoffset[]]. Changed in version 3.3: Equality comparisons between aware and naive datetime instances don’t raise TypeError. Note In order to stop comparison from falling back to the default scheme of comparing object addresses, datetime comparison normally raises TypeError if the other comparand isn’t also a datetime object. However, NotImplemented is returned instead if the other comparand has a timetuple[] attribute. This hook gives other kinds of date objects a chance at implementing mixed-type comparison. If not, when a datetime object is compared to an object of a different type, TypeError is raised unless the comparison is == or !=. The latter cases return False or True, respectively. Instance methods: datetime.date[]¶ Return date object with same year, month and day. datetime.time[]¶ Return time object with same hour, minute, second, microsecond and fold. tzinfo is None. See also method timetz[]. Changed in version 3.6: The fold value is copied to the returned time object. datetime.timetz[]¶ Return time object with same hour, minute, second, microsecond, fold, and tzinfo attributes. See also method time[]. Changed in version 3.6: The fold value is copied to the returned time object. datetime.replace[year=self.year, month=self.month, day=self.day, hour=self.hour, minute=self.minute, second=self.second, microsecond=self.microsecond, tzinfo=self.tzinfo, *, fold=0]¶ Return a datetime with the same attributes, except for those attributes given new values by whichever keyword arguments are specified. Note that tzinfo=None can be specified to create a naive datetime from an aware datetime with no conversion of date and time data. New in version 3.6: Added the fold argument. datetime.astimezone[tz=None]¶ Return a datetime object with new tzinfo attribute tz, adjusting the date and time data so the result is the same UTC time as self, but in tz’s local time. If provided, tz must be an instance of a tzinfo subclass, and its utcoffset[] and dst[] methods must not return None. If self is naive, it is presumed to represent time in the system timezone. If called without arguments [or with tz=None] the system local timezone is assumed for the target timezone. The .tzinfo attribute of the converted datetime instance will be set to an instance of timezone with the zone name and offset obtained from the OS. If self.tzinfo is tz, self.astimezone[tz] is equal to self: no adjustment of date or time data is performed. Else the result is local time in the timezone tz, representing the same UTC time as self: after astz = dt.astimezone[tz], astz - astz.utcoffset[] will have the same date and time data as dt - dt.utcoffset[]. If you merely want to attach a time zone object tz to a datetime dt without adjustment of date and time data, use dt.replace[tzinfo=tz]. If you merely want to remove the time zone object from an aware datetime dt without conversion of date and time data, use dt.replace[tzinfo=None]. Note that the default tzinfo.fromutc[] method can be overridden in a tzinfo subclass to affect the result returned by astimezone[]. Ignoring error cases, astimezone[] acts like: def astimezone[self, tz]: if self.tzinfo is tz: return self # Convert self to UTC, and attach the new time zone object. utc = [self - self.utcoffset[]].replace[tzinfo=tz] # Convert from UTC to tz's local time. return tz.fromutc[utc] Changed in version 3.3: tz now can be omitted. Changed in version 3.6: The astimezone[] method can now be called on naive instances that are presumed to represent system local time. datetime.utcoffset[]¶ If tzinfo is None, returns None, else returns self.tzinfo.utcoffset[self], and raises an exception if the latter doesn’t return None or a timedelta object with magnitude less than one day. Changed in version 3.7: The UTC offset is not restricted to a whole number of minutes. datetime.dst[]¶ If tzinfo is None, returns None, else returns self.tzinfo.dst[self], and raises an exception if the latter doesn’t return None or a timedelta object with magnitude less than one day. Changed in version 3.7: The DST offset is not restricted to a whole number of minutes. datetime.tzname[]¶ If tzinfo is None, returns None, else returns self.tzinfo.tzname[self], raises an exception if the latter doesn’t return None or a string object, datetime.timetuple[]¶ Return a time.struct_time such as returned by time.localtime[]. d.timetuple[] is equivalent to: time.struct_time[[d.year, d.month, d.day, d.hour, d.minute, d.second, d.weekday[], yday, dst]] where yday = d.toordinal[] - date[d.year, 1, 1].toordinal[] + 1 is the day number within the current year starting with 1 for January 1st. The tm_isdst flag of the result is set according to the dst[] method: tzinfo is None or dst[] returns None, tm_isdst is set to -1; else if dst[] returns a non-zero value, tm_isdst is set to 1; else tm_isdst is set to 0. datetime.utctimetuple[]¶ If datetime instance d is naive, this is the same as d.timetuple[] except that tm_isdst is forced to 0 regardless of what d.dst[] returns. DST is never in effect for a UTC time. If d is aware, d is normalized to UTC time, by subtracting d.utcoffset[], and a time.struct_time for the normalized time is returned. tm_isdst is forced to 0. Note that an OverflowError may be raised if d.year was MINYEAR or MAXYEAR and UTC adjustment spills over a year boundary. Warning Because naive datetime objects are treated by many datetime methods as local times, it is preferred to use aware datetimes to represent times in UTC; as a result, using utcfromtimetuple may give misleading results. If you have a naive datetime representing UTC, use datetime.replace[tzinfo=timezone.utc] to make it aware, at which point you can use datetime.timetuple[]. datetime.toordinal[]¶ Return the proleptic Gregorian ordinal of the date. The same as self.date[].toordinal[]. datetime.timestamp[]¶ Return POSIX timestamp corresponding to the datetime instance. The return value is a float similar to that returned by time.time[]. Naive datetime instances are assumed to represent local time and this method relies on the platform C mktime[] function to perform the conversion. Since datetime supports wider range of values than mktime[] on many platforms, this method may raise OverflowError for times far in the past or far in the future. For aware datetime instances, the return value is computed as: [dt - datetime[1970, 1, 1, tzinfo=timezone.utc]].total_seconds[] New in version 3.3. Changed in version 3.6: The timestamp[] method uses the fold attribute to disambiguate the times during a repeated interval. Note There is no method to obtain the POSIX timestamp directly from a naive datetime instance representing UTC time. If your application uses this convention and your system timezone is not set to UTC, you can obtain the POSIX timestamp by supplying tzinfo=timezone.utc: timestamp = dt.replace[tzinfo=timezone.utc].timestamp[] or by calculating the timestamp directly: timestamp = [dt - datetime[1970, 1, 1]] / timedelta[seconds=1] datetime.weekday[]¶ Return the day of the week as an integer, where Monday is 0 and Sunday is 6. The same as self.date[].weekday[]. See also isoweekday[]. datetime.isoweekday[]¶ Return the day of the week as an integer, where Monday is 1 and Sunday is 7. The same as self.date[].isoweekday[]. See also weekday[], isocalendar[]. datetime.isocalendar[]¶ Return a named tuple with three components: year, week and weekday. The same as self.date[].isocalendar[]. datetime.isoformat[sep='T', timespec='auto']¶ Return a string representing the date and time in ISO 8601 format: YYYY-MM-DDTHH:MM:SS.ffffff, if microsecond is not 0 YYYY-MM-DDTHH:MM:SS, if microsecond is 0 If utcoffset[] does not return None, a string is appended, giving the UTC offset: YYYY-MM-DDTHH:MM:SS.ffffff+HH:MM[:SS[.ffffff]], if microsecond is not 0 YYYY-MM-DDTHH:MM:SS+HH:MM[:SS[.ffffff]], if microsecond is 0 Examples: >>> from datetime import datetime, timezone >>> datetime[2019, 5, 18, 15, 17, 8, 132263].isoformat[] '2019-05-18T15:17:08.132263' >>> datetime[2019, 5, 18, 15, 17, tzinfo=timezone.utc].isoformat[] '2019-05-18T15:17:00+00:00' The optional argument sep [default 'T'] is a one-character separator, placed between the date and time portions of the result. For example: >>> from datetime import tzinfo, timedelta, datetime >>> class TZ[tzinfo]: ... """A time zone with an arbitrary, constant -06:39 offset.""" ... def utcoffset[self, dt]: ... return timedelta[hours=-6, minutes=-39] ... >>> datetime[2002, 12, 25, tzinfo=TZ[]].isoformat[' '] '2002-12-25 00:00:00-06:39' >>> datetime[2009, 11, 27, microsecond=100, tzinfo=TZ[]].isoformat[] '2009-11-27T00:00:00.000100-06:39' The optional argument timespec specifies the number of additional components of the time to include [the default is 'auto']. It can be one of the following: 'auto': Same as 'seconds' if microsecond is 0, same as 'microseconds' otherwise. 'hours': Include the hour in the two-digit HH format. 'minutes': Include hour and minute in HH:MM format. 'seconds': Include hour, minute, and second in HH:MM:SS format. 'milliseconds': Include full time, but truncate fractional second part to milliseconds. HH:MM:SS.sss format. 'microseconds': Include full time in HH:MM:SS.ffffff format. Note Excluded time components are truncated, not rounded. ValueError will be raised on an invalid timespec argument: >>> from datetime import datetime >>> datetime.now[].isoformat[timespec='minutes'] '2002-12-25T00:00' >>> dt = datetime[2015, 1, 1, 12, 30, 59, 0] >>> dt.isoformat[timespec='microseconds'] '2015-01-01T12:30:59.000000' New in version 3.6: Added the timespec argument. datetime.__str__[]¶ For a datetime instance d, str[d] is equivalent to d.isoformat[' ']. datetime.ctime[]¶ Return a string representing the date and time: >>> from datetime import datetime >>> datetime[2002, 12, 4, 20, 30, 40].ctime[] 'Wed Dec 4 20:30:40 2002' The output string will not include time zone information, regardless of whether the input is aware or naive. d.ctime[] is equivalent to: time.ctime[time.mktime[d.timetuple[]]] on platforms where the native C ctime[] function [which time.ctime[] invokes, but which datetime.ctime[] does not invoke] conforms to the C standard. datetime.strftime[format]¶ Return a string representing the date and time, controlled by an explicit format string. For a complete list of formatting directives, see strftime[] and strptime[] Behavior. datetime.__format__[format]¶ Same as datetime.strftime[]. This makes it possible to specify a format string for a datetime object in formatted string literals and when using str.format[]. For a complete list of formatting directives, see strftime[] and strptime[] Behavior. Examples of Usage: datetime¶ Examples of working with datetime objects: >>> from datetime import datetime, date, time, timezone >>> # Using datetime.combine[] >>> d = date[2005, 7, 14] >>> t = time[12, 30] >>> datetime.combine[d, t] datetime.datetime[2005, 7, 14, 12, 30] >>> # Using datetime.now[] >>> datetime.now[] datetime.datetime[2007, 12, 6, 16, 29, 43, 79043] # GMT +1 >>> datetime.now[timezone.utc] datetime.datetime[2007, 12, 6, 15, 29, 43, 79060, tzinfo=datetime.timezone.utc] >>> # Using datetime.strptime[] >>> dt = datetime.strptime["21/11/06 16:30", "%d/%m/%y %H:%M"] >>> dt datetime.datetime[2006, 11, 21, 16, 30] >>> # Using datetime.timetuple[] to get tuple of all attributes >>> tt = dt.timetuple[] >>> for it in tt: ... print[it] ... 2006 # year 11 # month 21 # day 16 # hour 30 # minute 0 # second 1 # weekday [0 = Monday] 325 # number of days since 1st January -1 # dst - method tzinfo.dst[] returned None >>> # Date in ISO format >>> ic = dt.isocalendar[] >>> for it in ic: ... print[it] ... 2006 # ISO year 47 # ISO week 2 # ISO weekday >>> # Formatting a datetime >>> dt.strftime["%A, %d. %B %Y %I:%M%p"] 'Tuesday, 21. November 2006 04:30PM' >>> 'The {1} is {0:%d}, the {2} is {0:%B}, the {3} is {0:%I:%M%p}.'.format[dt, "day", "month", "time"] 'The day is 21, the month is November, the time is 04:30PM.' The example below defines a tzinfo subclass capturing time zone information for Kabul, Afghanistan, which used +4 UTC until 1945 and then +4:30 UTC thereafter: from datetime import timedelta, datetime, tzinfo, timezone class KabulTz[tzinfo]: # Kabul used +4 until 1945, when they moved to +4:30 UTC_MOVE_DATE = datetime[1944, 12, 31, 20, tzinfo=timezone.utc] def utcoffset[self, dt]: if dt.year >> tz1 = KabulTz[] >>> # Datetime before the change >>> dt1 = datetime[1900, 11, 21, 16, 30, tzinfo=tz1] >>> print[dt1.utcoffset[]] 4:00:00 >>> # Datetime after the change >>> dt2 = datetime[2006, 6, 14, 13, 0, tzinfo=tz1] >>> print[dt2.utcoffset[]] 4:30:00 >>> # Convert datetime to another time zone >>> dt3 = dt2.astimezone[timezone.utc] >>> dt3 datetime.datetime[2006, 6, 14, 8, 30, tzinfo=datetime.timezone.utc] >>> dt2 datetime.datetime[2006, 6, 14, 13, 0, tzinfo=KabulTz[]] >>> dt2 == dt3 True time Objects¶ A time object represents a [local] time of day, independent of any particular day, and subject to adjustment via a tzinfo object. class datetime.time[hour=0, minute=0, second=0, microsecond=0, tzinfo=None, *, fold=0]¶ All arguments are optional. tzinfo may be None, or an instance of a tzinfo subclass. The remaining arguments must be integers in the following ranges: 0 > time.fromisoformat['04:23:01.000384'] datetime.time[4, 23, 1, 384] >>> time.fromisoformat['04:23:01+04:00'] datetime.time[4, 23, 1, tzinfo=datetime.timezone[datetime.timedelta[seconds=14400]]] New in version 3.7. Instance methods: time.replace[hour=self.hour, minute=self.minute, second=self.second, microsecond=self.microsecond, tzinfo=self.tzinfo, *, fold=0]¶ Return a time with the same value, except for those attributes given new values by whichever keyword arguments are specified. Note that tzinfo=None can be specified to create a naive time from an aware time, without conversion of the time data. New in version 3.6: Added the fold argument. time.isoformat[timespec='auto']¶ Return a string representing the time in ISO 8601 format, one of: HH:MM:SS.ffffff, if microsecond is not 0 HH:MM:SS, if microsecond is 0 HH:MM:SS.ffffff+HH:MM[:SS[.ffffff]], if utcoffset[] does not return None HH:MM:SS+HH:MM[:SS[.ffffff]], if microsecond is 0 and utcoffset[] does not return None The optional argument timespec specifies the number of additional components of the time to include [the default is 'auto']. It can be one of the following: 'auto': Same as 'seconds' if microsecond is 0, same as 'microseconds' otherwise. 'hours': Include the hour in the two-digit HH format. 'minutes': Include hour and minute in HH:MM format. 'seconds': Include hour, minute, and second in HH:MM:SS format. 'milliseconds': Include full time, but truncate fractional second part to milliseconds. HH:MM:SS.sss format. 'microseconds': Include full time in HH:MM:SS.ffffff format. Note Excluded time components are truncated, not rounded. ValueError will be raised on an invalid timespec argument. Example: >>> from datetime import time >>> time[hour=12, minute=34, second=56, microsecond=123456].isoformat[timespec='minutes'] '12:34' >>> dt = time[hour=12, minute=34, second=56, microsecond=0] >>> dt.isoformat[timespec='microseconds'] '12:34:56.000000' >>> dt.isoformat[timespec='auto'] '12:34:56' New in version 3.6: Added the timespec argument. time.__str__[]¶ For a time t, str[t] is equivalent to t.isoformat[]. time.strftime[format]¶ Return a string representing the time, controlled by an explicit format string. For a complete list of formatting directives, see strftime[] and strptime[] Behavior. time.__format__[format]¶ Same as time.strftime[]. This makes it possible to specify a format string for a time object in formatted string literals and when using str.format[]. For a complete list of formatting directives, see strftime[] and strptime[] Behavior. time.utcoffset[]¶ If tzinfo is None, returns None, else returns self.tzinfo.utcoffset[None], and raises an exception if the latter doesn’t return None or a timedelta object with magnitude less than one day. Changed in version 3.7: The UTC offset is not restricted to a whole number of minutes. time.dst[]¶ If tzinfo is None, returns None, else returns self.tzinfo.dst[None], and raises an exception if the latter doesn’t return None, or a timedelta object with magnitude less than one day. Changed in version 3.7: The DST offset is not restricted to a whole number of minutes. time.tzname[]¶ If tzinfo is None, returns None, else returns self.tzinfo.tzname[None], or raises an exception if the latter doesn’t return None or a string object. Examples of Usage: time¶ Examples of working with a time object: >>> from datetime import time, tzinfo, timedelta >>> class TZ1[tzinfo]: ... def utcoffset[self, dt]: ... return timedelta[hours=1] ... def dst[self, dt]: ... return timedelta[0] ... def tzname[self,dt]: ... return "+01:00" ... def __repr__[self]: ... return f"{self.__class__.__name__}[]" ... >>> t = time[12, 10, 30, tzinfo=TZ1[]] >>> t datetime.time[12, 10, 30, tzinfo=TZ1[]] >>> t.isoformat[] '12:10:30+01:00' >>> t.dst[] datetime.timedelta[0] >>> t.tzname[] '+01:00' >>> t.strftime["%H:%M:%S %Z"] '12:10:30 +01:00' >>> 'The {} is {:%H:%M}.'.format["time", t] 'The time is 12:10.' tzinfo Objects¶ class datetime.tzinfo¶ This is an abstract base class, meaning that this class should not be instantiated directly. Define a subclass of tzinfo to capture information about a particular time zone. An instance of [a concrete subclass of] tzinfo can be passed to the constructors for datetime and time objects. The latter objects view their attributes as being in local time, and the tzinfo object supports methods revealing offset of local time from UTC, the name of the time zone, and DST offset, all relative to a date or time object passed to them. You need to derive a concrete subclass, and [at least] supply implementations of the standard tzinfo methods needed by the datetime methods you use. The datetime module provides timezone, a simple concrete subclass of tzinfo which can represent timezones with fixed offset from UTC such as UTC itself or North American EST and EDT. Special requirement for pickling: A tzinfo subclass must have an __init__[] method that can be called with no arguments, otherwise it can be pickled but possibly not unpickled again. This is a technical requirement that may be relaxed in the future. A concrete subclass of tzinfo may need to implement the following methods. Exactly which methods are needed depends on the uses made of aware datetime objects. If in doubt, simply implement all of them. tzinfo.utcoffset[dt]¶ Return offset of local time from UTC, as a timedelta object that is positive east of UTC. If local time is west of UTC, this should be negative. This represents the total offset from UTC; for example, if a tzinfo object represents both time zone and DST adjustments, utcoffset[] should return their sum. If the UTC offset isn’t known, return None. Else the value returned must be a timedelta object strictly between -timedelta[hours=24] and timedelta[hours=24] [the magnitude of the offset must be less than one day]. Most implementations of utcoffset[] will probably look like one of these two: return CONSTANT # fixed-offset class return CONSTANT + self.dst[dt] # daylight-aware class If utcoffset[] does not return None, dst[] should not return None either. The default implementation of utcoffset[] raises NotImplementedError. Changed in version 3.7: The UTC offset is not restricted to a whole number of minutes. tzinfo.dst[dt]¶ Return the daylight saving time [DST] adjustment, as a timedelta object or None if DST information isn’t known. Return timedelta[0] if DST is not in effect. If DST is in effect, return the offset as a timedelta object [see utcoffset[] for details]. Note that DST offset, if applicable, has already been added to the UTC offset returned by utcoffset[], so there’s no need to consult dst[] unless you’re interested in obtaining DST info separately. For example, datetime.timetuple[] calls its tzinfo attribute’s dst[] method to determine how the tm_isdst flag should be set, and tzinfo.fromutc[] calls dst[] to account for DST changes when crossing time zones. An instance tz of a tzinfo subclass that models both standard and daylight times must be consistent in this sense: tz.utcoffset[dt] - tz.dst[dt] must return the same result for every datetime dt with dt.tzinfo == tz For sane tzinfo subclasses, this expression yields the time zone’s “standard offset”, which should not depend on the date or the time, but only on geographic location. The implementation of datetime.astimezone[] relies on this, but cannot detect violations; it’s the programmer’s responsibility to ensure it. If a tzinfo subclass cannot guarantee this, it may be able to override the default implementation of tzinfo.fromutc[] to work correctly with astimezone[] regardless. Most implementations of dst[] will probably look like one of these two: def dst[self, dt]: # a fixed-offset class: doesn't account for DST return timedelta[0] or: def dst[self, dt]: # Code to set dston and dstoff to the time zone's DST # transition times based on the input dt.year, and expressed # in standard local time. if dston 0 Local = LocalTimezone[] # A complete implementation of current DST rules for major US time zones. def first_sunday_on_or_after[dt]: days_to_go = 6 - dt.weekday[] if days_to_go: dt += timedelta[days_to_go] return dt # US DST Rules # # This is a simplified [i.e., wrong for a few cases] set of rules for US # DST start and end times. For a complete and up-to-date set of DST rules # and timezone definitions, visit the Olson Database [or try pytz]: # //www.twinsun.com/tz/tz-link.htm # //sourceforge.net/projects/pytz/ [might not be up-to-date] # # In the US, since 2007, DST starts at 2am [standard time] on the second # Sunday in March, which is the first Sunday on or after Mar 8. DSTSTART_2007 = datetime[1, 3, 8, 2] # and ends at 2am [DST time] on the first Sunday of Nov. DSTEND_2007 = datetime[1, 11, 1, 2] # From 1987 to 2006, DST used to start at 2am [standard time] on the first # Sunday in April and to end at 2am [DST time] on the last # Sunday of October, which is the first Sunday on or after Oct 25. DSTSTART_1987_2006 = datetime[1, 4, 1, 2] DSTEND_1987_2006 = datetime[1, 10, 25, 2] # From 1967 to 1986, DST used to start at 2am [standard time] on the last # Sunday in April [the one on or after April 24] and to end at 2am [DST time] # on the last Sunday of October, which is the first Sunday # on or after Oct 25. DSTSTART_1967_1986 = datetime[1, 4, 24, 2] DSTEND_1967_1986 = DSTEND_1987_2006 def us_dst_range[year]: # Find start and end times for US DST. For years before 1967, return # start = end for no DST. if 2006 Bài Viết Liên Quan What is a complex data type in python Hướng dẫn dùng python eof python Hướng dẫn dùng basecode64 trong PHP Php double quotes in string Hướng dẫn dùng postgres port trong PHP Hướng dẫn program in python Hướng dẫn comparison python How do i start mongodb on mac terminal? Tucson 2023 màu đen What are examples of python? Hướng dẫn rotate trong css Which of the following is correct true about php variables Hướng dẫn php weekday index Left and right rotation of string in python Làm game flappy bird bằng javascript Hướng dẫn dùng set difference python How to create unique id php? How do you randomize a seed in python? How do you iterate through an array of objects in php? Công nghệ 2023 Toplist mới #1 Top 7 sự tích hồ gươm - ngữ văn lớp 6 2023 5 tháng trước #2 Top 7 gdcd 6 bài 1 kết nối tri thức 2023 5 tháng trước #3 Top 7 ý nghĩa của xây dựng gia đình văn hóa 2023 5 tháng trước #4 Top 6 mẫu hợp đồng mượn đất làm nhà xưởng 2023 5 tháng trước #5 Top 3 tổng tài biến thái tôi yêu anh tập 27 2023 5 tháng trước #6 Top 6 kết thực phim mỹ nhân vô lệ 2023 5 tháng trước #7 Top 9 trong những câu thơ sau câu nào sử dụng thành ngữ 2023 5 tháng trước #8 Top 8 đề tài và chủ de của tác phẩm tắt đèn 2023 5 tháng trước #9 Top 5 tiểu sử của thầy thích pháp hòa 2023 5 tháng trước Bài mới nhất Có xét ngành nghề khi nhập khẩu hàng hóa năm 2024 Phần mềm khắc phụ lỗi wifi trên an năm 2024 Banner cỡ lớn treo ngoài đường tiếng anh là gì năm 2024 Top hãng mặt nạ nội địa trung quốc năm 2024 Học hỏi những điểm tốt tiếng anh là gì năm 2024 Cường hóa lên thẳng 15 trong nháy mắt năm 2024 Phòng khám trung nguyện ở bình đại bến tre năm 2024 Cải lương chi bảo là gì năm 2024 Bài tập hỗn hợp kim loại tác dụng với hno3 năm 2024 Chủ Đề programming Hỏi Đáp Toplist Là gì Bài Tập Địa Điểm Hay Mẹo Hay Học Tốt Nghĩa của từ Công Nghệ Khỏe Đẹp bao nhiêu Top List Tiếng anh Bao nhiêu Sản phẩm tốt Xây Đựng Ngôn ngữ javascript Ở đâu Đại học Hướng dẫn Bài tập Tại sao Dịch So Sánh Máy tính Món Ngon mẹo hay Bao lâu Thế nào So sánh Khoa Học Vì sao Lớp 9 Lớp 10