timezone | object oriented representation of all timezones | Natural Language Processing library

Ok so it required a dependency tzlocal==2.1 so it could get local timezone, i assume for some reason the version that the module has does not work on my system

When running the gunicorn command, you can try to add workers parameter with using options -w or --workers.

It defaults to 1 as stated in the gunicorn documentation. You may want to try to increase that value.

Example usage:

You said:

The output gives the same instant:

An Instant is a moment as seen in UTC, that is, with an offset from UTC of zero hours-minutes-seconds. So your code makes no use of your specified time zones.

Instead, try ZonedDateTime. This class does make use of the time zone. For example, calling ZonedDateTime.now() captures the current moment as seen in the JVM’s current default time zone. Calling ZonedDateTime.now( myClock ) captures the current moment tracked by that Clock object as seen through that Clock object’s assigned time zone.

Use the following code:

Yes. The format of acceptable Date strings in JavaScript is standardized:

ECMAScript defines a string interchange format for date-times based upon a simplification of the ISO 8601 calendar date extended format. The format is as follows:

Timestamp objects are certainly of type 'object', and it is possible you cannot escape the index to take this type if you use Timestamps as index.

By "timestamp configuration" I understand "timezone", and that you want to insert new times in the same timezone.

• Either you know the timezone from the start and data of all rows come from a source known to be from the same timezone. In that case you can specify the same timezone when you instantiate the Timestamps.

• Or you do not know the timezone of the data in the first place, and you have new data coming from another source, so potentially from a different timezone, that you certainly know about. Mixing timestamps from different timezones is not a problem, since timezones should be taken into account when you compare them with one another. You can still localize them all later to a timezone you prefer.

As you noted, Calendar was supplanted years ago by the java.time classes defined in JSR 310 (unanimously adopted). And as you note there are many reasons to avoid using Calendar & Date etc.

If you must have a Calendar object to interoperate with old code not yet updated to java.time, convert after doing your work in java.time.

Specify your desired time zone. Note that US/Pacific is merely an alias for the actual time zone, America/Los_Angeles.

tl;dr

Add this to your application.properties:

Your dateTime string is wrong, misunderstood. It obviously tries to conform to the ISO 8601 format and fails. Because the ISO 8601 format uses US-ASCII digits.

The classes of java.time (Instant, OffsetDateTime and ZonedDateTime) would parse your string without any formatter if only the digits were correct for ISO 8601. In the vast majority of cases I would take your avenue: try to parse the string as it is. Not in this case. To me it makes more sense to correct the string before parsing.