Log message:
py-phonenumbers: updated to 8.8.6
v8.8.6
Metadata changes:
- Updated alternate formatting data for country calling code(s):
34, 62, 91, 94, 971, 972
- Updated phone metadata for region code(s):
AE, AR, AU, BB, BN, BR, BW, BY, BZ, CC, CL, CW, CX, DE, EC, EG, ET, GB, GE,
GG, GP, HK, HR, ID, IE, IL, IN, JO, KH, LK, LU, LV, LY, MG, MO, MR, MY, NL,
NR, OM, PH, PK, PM, PS, RE, RU, RW, SA, SE, SG, SH, SK, SM, TH, TJ, UZ, VN,
ZM, ZW
- New geocoding data for country calling code(s): 61 (en)
- Updated geocoding data for country calling code(s): 20 (en)
- New carrier data for country calling code(s): 674 (en)
- Updated carrier data for country calling code(s):
61 (en), 91 (en), 234 (en), 593 (en), 1246 (en)
- Updated / refreshed time zone meta data.
|
Log message:
py-phonenumbers: update to 8.8.2
v8.8.2
Metadata changes:
- Updated phone metadata for region code(s):
CA, CR, EG, FI, HN, IS, KM, KR, LU, MV, PA, TW, UG, US, VN
- Updated short number metadata for region code(s): IE, IR, KE, TR
- New geocoding data for country calling code(s): 1223 (en)
- Updated geocoding data for country calling code(s): 84 (en, vi)
- Updated carrier data for country calling code(s): 20 (en)
|
Log message:
What's new in 8.0.0
Merge to upstream commit 1eb06f31e1dd; relevant code changes:
Removing the ability for .._for_region methods in shortnumberinfo.py to work \
on strings, as well of phone number objects. These have been marked deprecated \
for months. Any users of these methods should call phonenumbers.parse first to \
create a PhoneNumber object, and pass this in.
Support semicolon as extension character while parsing phone numbers. This \
is not applicable when you are trying to find the phone numbers.
What's new in 7.7.5
Merge to upstream commit e905483f87cf; relevant code changes:
Removing all references to possible_number_pattern other than in the \
metadata itself.
What's new in 7.7.4
Merge to upstream commit fedbc7020703; code changes:
GitHub project changes:
Changed tag to vX.Y.Z from release-X.Y.Z; this may affect ports and \
derived projects.
Metadata structure changes in XML file:
Mobile and Fixed-Line blocks are no longer assumed to inherit missing \
data from the GeneralDesc, but are treated like every other phone number type. \
This means that for the non-geographical country codes, like +800, the example \
number has been moved from generalDesc to the relevant number types, and the \
code in getExampleNumberForNonGeoEntity has been changed to look at these \
sub-types for an example number. This also means that the "NA" and \
"-1" blocks present in the metadata to indicate that no mobile or \
fixed-line numbers appear for the entity have been removed. There should no \
longer be an exampleNumber at the generalDesc level, but it should be present at \
every PhoneNumberDesc with data.
Code changes:
Using new possibleLengthInfo to decide whether a short number is the \
right length or not. This could result in more specific results; whereas before, \
a number from length 3 to length 6 may have been deemed possible, now we may \
exclude a number of length 5.
Add hash (#) as a diallable character. Numbers with # in them will no \
longer have formatting applied in format_n_original_format, and \
normalize_diallable_chars_only now retains the # symbol.
example_number_for_non_geo_entity has been changed to look at the \
specific number types, not just the generalDesc, for the example numbers; this \
is a necessary change after the metadata structure change detailed above.
What's new in 7.7.3
Merge to upstream commit ad0ce0c94501; code changes:
Fixed phonemetadata.py not to merge from a NumberFormat's unset bool \
national_prefix_optional_when_formatting.
What's new in 7.7.2
Merge to upstream commit 2d0d216f6032; code changes:
Stop setting empty preferred_domestic_carrier_code, and if we are passed \
such a number then treat the empty field as if unset.
What's new in 7.7.1
Merge to upstream commit 8c37310deb49; code changes:
Switching the internal implementation of is_possible_number and related \
functions to use the new possibleLengths metadata. This affects a lot of \
countries, making is_possible_number more restrictive as more precise data is \
available. It also affects parsing ambiguous and invalid numbers, as we decide \
whether to strip a possible national prefix (1) or country code based on the \
length of the number and whether it is possible before or after this.
Formatting, naming and comment tweaks to follow style guide
Removal of unneeded _can_be_geocoded method in the timezone.py file, using \
phonenumberutil.py instead
What's new in 7.7.0
Merge to upstream commit 1ec4d341c3cd; no code changes that affect the Python \
version so this is just a version bump to stay in sync with upstream.
What's new in 7.6.1
Merge to upstream commit 7cc500f588db; code changes:
phonemetadata.py has two more fields to represent possible lengths of phone \
numbers. Changed buildmetadatafromxml.py to alter the way that metadata about \
possible-lengths information is consumed when constructing metadata to populate \
these. Discussion list email
What's new in 7.6.0
Merge to upstream commit ddf60b1c175e; code changes:
Made is_number_geographical() public and added \
is_number_type_geographical(), and changed the geocoder to use this when \
checking whether to give a detailed answer or country-level only.
What's new in 7.5.0
Merge to upstream commit 3f83454ed62b; no code changes that affect the Python \
version so this is just a version bump to stay in sync with upstream.
|