Skip to main content

gae-pytz

pytz has a severe performance problem that impedes its usage on Google App Engine. This is caused because pytz.__init__ builds a list of available zoneinfos checking the entire zoneinfo database (which means: it tries to open hundreds of files). This is done in the module globals, so it is not easily avoidable. And it is far from ideal to do this in App Engine - app initialization becomes unacceptable if every time we import pytz it checks 500+ files.

In this alternative version, pytz is highly optimized for App Engine, following ideas from several recipes around:

  • database files are not automatically reads when the module is imported

  • the database files are loaded using zipimport to reduce number of files

  • it uses memcache to cache already loaded zoneinfos

This results in almost unnoticeable load time and makes pytz usable on App Engine.

Metadata

Release files for gaepytz 2010l

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distributions (sdists)

Source distribution for gaepytz 2010l
File Size Uploaded Provenance Actions
gaepytz-2010l.zip 385.2 kB Without provenance Details for gaepytz-2010l.zip
gaepytz-2010l.tar.gz 381.6 kB Without provenance Details for gaepytz-2010l.tar.gz

Release files / gaepytz-2010l.zip

Download URL gaepytz-2010l.zip
Size 385.2 kB
Tags Source
SHA-256 checksum
How to use checksums
d7c223c88fe982b4973ada1077077616a0fd1ccd58899bb2de16298844104924
BLAKE2b-256 checksum
How to use checksums
26027c34b5cf1d005a4d9038634a9065613a5f7ae257f15339e7b8b6d7d1344b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Release files / gaepytz-2010l.tar.gz

Download URL gaepytz-2010l.tar.gz
Size 381.6 kB
Tags Source
SHA-256 checksum
How to use checksums
448f1123604e644b36ca25bfb0aa9ca46591140e5d83efd94e0a5ec3f42f6a95
BLAKE2b-256 checksum
How to use checksums
34182c9ad1bb7499559315ea463e06e1acdffb91cc61b2fb4f5df0797678a854
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for gaepytz 2010l

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page