yahoo-eng-team team mailing list archive

[OpenStack Infra <1762789@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/560092
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=443980399b03282c37e64e7a529be4960689b34d
Submitter: Zuul
Branch:    master

commit 443980399b03282c37e64e7a529be4960689b34d
Author: Eric Fried <efried@xxxxxxxxxx>
Date:   Tue Apr 10 12:17:17 2018 -0500

    Test case: ResourceClass.normalize_name with ß
    
    Demonstrates the cited bug by invoking ResourceClass.normalize_name on a
    string containing sharp S ('ß').  The result is different for py2 and
    py3.
    
    Change-Id: I632995c1a234f26f05ef0b5675e0e22b9866b03d
    Related-Bug: #1762789


** Changed in: nova
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1762789

Title:
  ResourceClass.normalize_name produces different results for py2 vs.
  py3

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Due to a py3 quirk (read: bug they decided not to fix) [1], .upper()
  works differently in py2 vs. py3 for the sharp S ('ß').  In py2, it
  stays the same (like all other characters not in the a-z range); in
  py3 it becomes the two-character string 'SS'.  This means that, as
  written, ResourceClass.normalize_name('ß') will yield 'CUSTOM__' in
  py2, but 'CUSTOM_SS' in py3.

  [1] https://bugs.python.org/issue4610

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1762789/+subscriptions