Public bug reported:

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.

** Affects: python2.7 (Ubuntu)
     Importance: Undecided
         Status: Fix Released

** Affects: python2.7 (Ubuntu Xenial)
     Importance: Undecided
         Status: New

** Affects: python2.7 (Ubuntu Zesty)
     Importance: Undecided
         Status: New

** Affects: python2.7 (Ubuntu Artful)
     Importance: Undecided
         Status: Fix Released

** Also affects: python2.7 (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Also affects: python2.7 (Ubuntu Artful)
   Importance: Undecided
       Status: New

** Also affects: python2.7 (Ubuntu Zesty)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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:
  New
Status in python2.7 source package in Zesty:
  New
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

_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to     : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

Reply via email to