Prep for 8.2.0 release

daviddrysdale · Feb 3, 2017 · caac1df · caac1df
1 parent b22c761
commit caac1df
Show file tree

Hide file tree

Showing 3 changed files with 13 additions and 2 deletions.
diff --git a/python/HISTORY.md b/python/HISTORY.md
@@ -1,4 +1,15 @@
 
+What's new in 8.2.0
+-------------------
+
+Merge to
+[upstream commit 3b16d6b06497](https://github.com/googlei18n/libphonenumber/commit/3b16d6b06497);
+relevant code changes:
+
+ - Exported `normalize_diallable_chars_only`. This method is already public in the C++
+   implementation. It has also now been added to the Javascript implementation.
+
+
 What's new in 8.1.0
 -------------------
 

diff --git a/python/phonenumbers/__init__.py b/python/phonenumbers/__init__.py
@@ -139,7 +139,7 @@
 
 # Version number is taken from the upstream libphonenumber version
 # together with an indication of the version of the Python-specific code.
-__version__ = "8.1.0"
+__version__ = "8.2.0"
 
 __all__ = ['PhoneNumber', 'CountryCodeSource', 'FrozenPhoneNumber',
            'REGION_CODE_FOR_NON_GEO_ENTITY', 'NumberFormat', 'PhoneNumberDesc', 'PhoneMetadata',

diff --git a/python/phonenumbers/shortnumberinfo.py b/python/phonenumbers/shortnumberinfo.py
@@ -384,7 +384,7 @@ def _matches_emergency_number_helper(number, region_code, allow_prefix_match):
 def is_carrier_specific(numobj):
     """Given a valid short number, determines whether it is carrier-specific
     (however, nothing is implied about its validity).  Carrier-specific numbers
-    may connect to a different end-point, or  not connect at all, depending
+    may connect to a different end-point, or not connect at all, depending
     on the user's carrier. If it is important that the number is valid, then
     its validity must first be checked using is_valid_short_number or
     is_valid_short_number_for_region.