[Bug 1734109] Re: Avoid symbol conflicts with `md5_*' symbols in third party extensions

[Matthias Klose]

packages successfully built. inspected the python binary for the renamed
functions.


** Tags removed: verification-needed verification-needed-xenial verification-needed-zesty
** Tags added: verification-done verification-done-xenial verification-done-zesty

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1734109

Title:
  Avoid symbol conflicts with `md5_*' symbols in third party extensions

Status in python2.7 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  Fix Committed
Status in python2.7 source package in Zesty:
  Fix Committed
Status in python2.7 source package in Artful:
  Fix Released

Bug description:
  SRU

  We link most extensions as built-ins into the python binary. the md5_*
  symbols cause a conflict with external libs/extensions.  So just use
  the _Py-* namespace for these. See the Debian report for details.

  These are internal functions for the md5 module. Renaming them to the
  _Py_* namespace avoids the conflict.  There should not be any case
  where these are intentionally referenced. At least in the archive
  there are no known references, so the regression potential is limited
  to external binaries, and there it should be minimal to non-existing
  as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1734109/+subscriptions