Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Describe timezone data loading in README

  • Loading branch information...
commit 019cf8b91f81415e53a76bc11917e8cc64d06e1f 1 parent 8800c97
@daviddrysdale authored
Showing with 3 additions and 0 deletions.
  1. +3 −0 
3 
@@ -176,6 +176,8 @@ In particular:
or `geocoder.country_name_for_number`).
* The carrier metadata is only loaded on the first use of one of the mapping functions (`carrier.name_for_number`
or `carrier.name_for_valid_number`).
+* The timezone metadata is only loaded on the first use of one of the timezone functions (`time_zones_for_number`
+ or `time_zones_for_geographical_number`).
* The normal metadata for each region is only loaded on the first time that metadata for that region is needed.
If you need to ensure that the metadata memory use is accounted for at start of day (i.e. that a subsequent on-demand
@@ -183,6 +185,7 @@ load of metadata will not cause memory exhaustion):
* Force-load the geocoding metadata by invoking `import phonenumbers.geocoder`.
* Force-load the carrier metadata by invoking `import phonenumbers.carrier`.
+* Force-load the timezone metadata by invoking `import phonenumbers.timezone`.
* Force-load the normal metadata by calling `phonenumbers.PhoneMetadata.load_all()`.
Project Layout
Please sign in to comment.
Something went wrong with that request. Please try again.