Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pin phonenumbers to latest version 8.4.1 #45

Closed
wants to merge 1 commit into from

Conversation

pyup-bot
Copy link

phonenumbers is not pinned to a specific version.

I'm pinning it to the latest version 8.4.1 for now.

These links might come in handy: PyPI | Changelog | Repo

Changelog

8.4.1


Merge to
upstream commit 02dbc0921cf5;
relevant code changes:

Code changes:

  • Changing is_possible_with_reason to return the enums INVALID_LENGTH and
    IS_POSSIBLE_LOCAL_ONLY, where these apply. is_possible_number continues to
    consider IS_POSSIBLE or IS_POSSIBLE_LOCAL_ONLY numbers as possible to dial.
    Announcement: https://groups.google.com/d/msg/libphonenumber-discuss/sPhYzdzFCmg/6tYsS1f6DgAJ
  • Doc updates for region_code_for_number to clarify that it does not
    work for short-codes or invalid numbers.

8.4.0


Merge to
upstream commit 77affd08f65f;
relevant code changes:

  • Doc changes to update references to ISO country codes to CLDR region codes,
    which are what we actually use. Notice in some of the mapper files the
    country code is still the ISO one, because it's used as part of a description
    of a language only (e.g. zh-TW vs zh-CN). Edited the language comments there
    since they can be two or three letters (c.f. fil for filipino). Also edited
    the comment for leadingDigits at the territory level in the
    phonemetadata.proto file.
  • New API methods: is_possible_number_for_type and
    is_possible_number_for_type_with_reason, along with supported_types_for_region and
    supported_types_for_non_geo_entity. These allow you to query which types (e.g.
    Mobile) exist for a particular region, and work out if a number is possible
    for that type (this is a simple length check) rather than for the region as a
    whole.

8.3.3


Merge to
upstream commit 46a38545ba01;
relevant code changes:

  • Doc fix for geocoder.py to explain the cases where an empty string might be returned.

8.3.2


Metadata changes only.

8.3.1


Merge to
upstream commit 5507fdbf623f;
relevant code changes:

  • Making national_significant_number more robust in the face of malicious
    input. This now ignores the number_of_leading_zeros if they are less than
    zero.

8.3.0


Merge to
upstream commit ad297a10ba19;
relevant code changes:

  • Added two new enum values to ValidationResult - IS_POSSIBLE_LOCAL_ONLY and
    INVALID_LENGTH. Added more documentation to the existing values; see the
    docstrings for when these are going to be used. Note that the API for
    is_possible_number_with_reason has not yet been changed to return these values.
    IS_POSSIBLE_LOCAL_ONLY will be returned for some values which currently
    return IS_POSSIBLE, and INVALID_LENGTH will be returned for some values which
    currently return TOO_LONG.
  • Fix for is_number_match to ignore the number_of_leading_zeros field when comparing
    numbers unless italian_leading_zero is True, and to consider default values
    to match the same value when explicitly set for these two fields. This fix
    shouldn't be needed for anyone correctly creating phone numbers using "parse"
    as recommended.

8.2.0


Merge to
upstream 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.

8.1.0


Merge to
upstream commit c210dbca4e93;
relevant code changes:

  • Introduced new is_carrier_specific_for_region API in shortnumberinfo.
    This determines whether the provided short code is carrier-specific or
    not when dialed from the given region.

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.

7.7.5


Merge to
upstream commit e905483f87cf;
relevant code changes:

  • Removing all references to possible_number_pattern other than in the metadata
    itself.

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.

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.

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.

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

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.

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

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.

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.

7.4.0


Merge to upstream commit 598b9a4f89d6; no code changes that affect the Python
version so this is just a version bump to stay in sync with upstream.

7.3.0


Merge to upstream commit d933631fbf15; code changes:

  • Added support for region_code of None in example_number_for_type()
  • Added invalid_example_number()
  • Improvements to docstring for parse method
  • Update is_number_geographical to return true for geographical mobile numbers.

7.2.0


Merge to upstream commit ab5e61acc087ec9f5, which is 7.2.1 (7.2.0 had an immediate
problem on release); upstream changelog mentions no code changes, but the Java
implementation includes a change to use nano protobufs.

7.1.0


Merge to upstream commit 903ac5de5b6e1112; upstream code changelog:

  • Only upstream code change doesn't affect python version
    (New MetadataSource implementation that reads from a single metadata file with
    all regions' phone number metadata.)

7.0.0


Merge to upstream Subversion revision 715; upstream code changelog:

  • New APIs for ShortNumberInfo. The old APIs have been deprecated and will be
    removed in an upcoming release.

6.3.0


Merge to upstream Subversion revision 703; upstream code changelog:

  • Changing the offline geocoder to not return any country at all if the number
    could belong to multiple countries
  • Removing obsolete code that treated countries with no metadata as valid.

6.2.0


Merge to upstream Subversion revision 674; upstream code changelog:

  • Better exclusion of dates when matching phone numbers from text.
  • Handle phone input in RFC3966 with missing tel: prefix

6.1.0


Merge to upstream Subversion revision 656; upstream code changelog:

  • Adding MetadataLoader support to allow custom metadata loading from
    alternative sources (should have no visible impact to users).
  • Fixing bug where digits could be lost in as-you-type formatting and
    formatting patterns incorrectly applied.

6.0.0


Removed beta status.
Merge up to upstream Subversion revision 650; upstream code changelog:

  • Better support for detecting phone numbers in text that are beside each
    other
  • Change to how Japanese numbers beginning with "00" are modelled, with the
    side-effect that the maximum possible number length has been extended by
    1.
  • Handle StringIndexOutOfBoundsException in the AsYouTypeFormatter when the
    national prefix that was extracted was not found in the prefix. This
    affected countries with very long carrier codes, such as Korea.
  • Removal of some of the author attributions - contributions to be tracked
    in CONTRIBUTORS file.

6.0.0a


Split geographic metadata into chunks.
Generate separate phonenumbers-lite package.
(No upstream changes.)

5.9b1


The codebase now supports Python 2.5-2.7 and Python 3.x out of the box, without
needing 2to3 conversion.

The top-level module no longer exports the following functions:

  • country_name_for_number
  • description_for_number
  • description_for_valid_number

These functions now need to be imported via the phonenumbers.geocoder submodule.

The short number functions have been renamed:

  • is_possible_short_number_object becomes is_possible_short_number
  • is_possible_short_number becomes is_possible_short_number_for_object
  • is_valid_short_number_object becomes is_valid_short_number
  • is_valid_short_number becomes is_valid_short_number_for_object
  • expected_cost becomes expected_cost_for_region, and there's a new expected_cost
    function that takes a PhoneNumber object.

Merge up to upstream Subversion revision 622; upstream code changelog:

  • Adding support for numbers with multiple Italian leading zeros, by
    adding a field to the phone number proto to allow an arbitrary number of
    leading zeros, and supporting this when parsing, validating and
    formatting.
  • Adding more functionality to ShortNumberInfo -> such as
    GetExpectedCostForRegion.
  • Fix for parsing short numbers that start with the national prefix.
  • Updating FormatNumberForMobileDialing to work with short numbers.
  • Stop finding Israeli 4-digit "star" numbers in text when no star is in
    fact present.
  • Bug fix for finding phone numbers where the area code was also part of
    the country calling code.

5.8b1


Rename shortnumberutil.py to shortnumberinfo.py.
Merge up to upstream Subversion revision 603; upstream code changelog:

  • Renamed ShortNumberUtil to ShortNumberInfo -> the former class is now
    deprecated and will be deleted in a later release. At the moment it just
    delegates to ShortNumberInfo.
  • New methods in the ShortNumberInfo API - isCarrierSpecific, singleton interface,
    isPossibleShortNumber, isValidShortNumber, getShortNumberCost. Note this
    is an experimental API at the moment and subject to change.
  • Bug fixes:
    • AsYouTypeFormatting: 3-digit numbers can be formatted as a group
      where appropriate
    • AsYouTypeFormatting: Countries with an optional national prefix were
      considered before to have always entered it, resulting in bugs where
      numbers without the national prefix were not properly formatted.
    • Numbers in Chile that overlap with emergency numbers are no longer
      marked as connecting to them
    • Not requiring the NDC to be alone for countries where there is no
      national prefix in strict grouping when extracting phone numbers

5.7b2


Fix setup.py to include new .shortdata sub-package.

5.7b1


Merge up to upstream Subversion revision 594; upstream code changelog:

  • Improve phone number extraction recall.
  • Add support for loading short number metadata.

5.6b1


Merge up to upstream Subversion revision 579; upstream code changelog:

  • Fix for as-you-type-formatting bug affecting countries with no national prefix
    formatting rule, such as China.

5.5b1


Merge up to upstream Subversion revision 574; upstream code changelog:

  • Changed internal initialization code and made more fields final.
    Note that we now throw an exception if an attempt is made to set the
    metadata more than once (which should only happen during testing).
  • Fix problem with formatNumberForMobileDialing for HU and CL.

5.4b1


Load metadata on demand rather than all at start of day.
Merge up to upstream Subversion revision 557; upstream code changelog:

  • Switch formatNumberForMobileDialing to prefer national format to international format when the
    number is dialed from the same region the phone number is from.

5.3b1


Merge up to upstream Subversion revision 550; upstream code changelog:

  • Handling UAN numbers in Argentina better when dialling them locally from a
    mobile

5.2b1


Merge up to upstream Subversion revision 532.

5.1b1


Merge up to upstream Subversion revision 516.

5.0b2


Merge up to upstream Subversion revision 500.
The upstream metadata at r489 didn't match the
generated Java code in 5.0; this upstream revision
fixed the mismatch.

5.0b1


Merge up to upstream Subversion revision 492.

4.9b1


Merge up to upstream Subversion revision 469.

4.8b1


Merge up to upstream Subversion revision 441.

4.7b1


Merge up to upstream Subversion revision 431.

4.6b1


Merge up to upstream Subversion revision 426.
Reinstated Python 2.5 support, accidentally broken since 4.3.

4.5b1


Merge up to upstream Subversion revision 419.

4.4b1


Merge up to upstream Subversion revision 411.

4.3b1


Merge up to upstream Subversion revision 396.
Adjust codebase to allow 2to3 generation of Python 3.x version.

4.2b1


Merge up to upstream Subversion revision 383.

4.1b1


Merge up to upstream Subversion revision 374.

4.0b1


Merge up to upstream Subversion revision 362.

3.9b1


Merge up to upstream Subversion revision 353.

3.8b1


Merge up to upstream Subversion revision 325.
Includes initial simplistic implementation of geocoding functionality.

3.7b1


Merge up to upstream Subversion revision 289 (but
geocoding functionality not yet ported).

3.6b1


Merge up to upstream Subversion revision 277 (but
geocoding functionality not yet ported).
Require Python 2.5, to allow import unicodedata.

3.5b2


Fix GH-3: crash in parse() for number with blank metadata

3.5b1


Merge up to upstream Subversion revision 213.

3.4b1


Merge up to upstream Subversion revision 205.
Changed version marker from a to b.
More unit test coverage

3.3a1


Merge up to upstream Subversion revision 190.

3.2a1


Merge up to upstream version 3.3, Subversion revision 171.

3.1a1


Initial port of libphonenumber, from http://code.google.com/p/libphonenumber/

This version based on upstream version 3.2, Subversion revision 166 of:
http://libphonenumber.googlecode.com/svn/trunk/java

Got merge conflicts? Close this PR and delete the branch. I'll create a new PR for you.

Happy merging! 🤖

@osantana osantana closed this Apr 18, 2017
@osantana osantana deleted the pyup-pin-phonenumbers-8.4.1 branch April 19, 2017 14:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implement Tracking Code status from Correios
2 participants