You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Native datetime instances are enough for basic cases but when you face more complex use-cases
they often show limitations and are not so intuitive to work with.
Pendulum provides a cleaner and more easy to use API while still relying on the standard library.
So it's still datetime but better.
Unlike other datetime libraries for Python, Pendulum is a drop-in replacement
for the standard datetime class (it inherits from it), so, basically, you can replace all your datetime
instances by DateTime instances in your code (exceptions exist for libraries that check
the type of the objects by using the type function like sqlite3 or PyMySQL for instance).
It also removes the notion of naive datetimes: each Pendulum instance is timezone-aware
and by default in UTC for ease of use.
Pendulum also improves the standard timedelta class by providing more intuitive methods and properties.
Limitations
Even though the DateTime class is a subclass of datetime there are some rare cases where
it can't replace the native class directly. Here is a list (non-exhaustive) of the reported cases with
a possible solution, if any:
sqlite3 will use the type() function to determine the type of the object by default. To work around it you can register a new adapter:
mysqlclient (former MySQLdb) and PyMySQL will use the type() function to determine the type of the object by default. To work around it you can register a new adapter:
django will use the isoformat() method to store datetimes in the database. However since pendulum is always timezone aware the offset information will always be returned by isoformat() raising an error, at least for MySQL databases. To work around it you can either create your own DateTimeField or use the previous workaround for MySQLdb:
If you want to help with localization, there are two different cases: the locale already exists
or not.
If the locale does not exist you will need to create it by using the clock utility:
./clock locale create <your-locale>
It will generate a directory in pendulum/locales named after your locale, with the following
structure:
<your-locale>/
- custom.py
- locale.py
The locale.py file must not be modified. It contains the translations provided by
the CLDR database.
The custom.py file is the one you want to modify. It contains the data needed
by Pendulum that are not provided by the CLDR database. You can take the en
data as a reference to see which data is needed.
You should also add tests for the created or modified locale.