This release is a pre-release and may not be stable for production use.
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.
1 maintainer
Metadata
1 maintainer
Release files for gaepytz 2011b
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distributions (sdists)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| gaepytz-2011b.zip | 393.8 kB | Without provenance | Details | |
| gaepytz-2011b.tar.gz | 390.4 kB | Without provenance | Details |
Release files / gaepytz-2011b.zip
| Download URL | gaepytz-2011b.zip |
|---|---|
| Size | 393.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fdadd957a40bd6d3facb91446779108bebd9a19e7eeda9a44a7b445ba3cd8ea9
|
|
BLAKE2b-256 checksum How to use checksums |
761905b639d7150bbbfd5497f77a570fdbd900d3ca6ad7e9523a703cd9bb176b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / gaepytz-2011b.tar.gz
| Download URL | gaepytz-2011b.tar.gz |
|---|---|
| Size | 390.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3e18b43480b8e332beb72b8b5c42effc7998f1b65cdcd96e641d8504804e8c32
|
|
BLAKE2b-256 checksum How to use checksums |
ad8d082d4c83a06fed1dbec355fe98401ff97b17502c75fd67257ea428d3cd33
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for gaepytz 2011b
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.
