yahoo-eng-team team mailing list archive

[Eric Fried <efried@xxxxxxxxxx>]

Public bug reported:

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

** Affects: nova
     Importance: Undecided
     Assignee: Eric Fried (efried)
         Status: In Progress


** Tags: placement

-- 
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):
  In Progress

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