** Changed in: beautifulsoup
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840141
Title:
xmlns attribute issue with XML parser with lxml 4.4.0
To manag
This bug was fixed in the package beautifulsoup4 - 4.8.0-1ubuntu1
---
beautifulsoup4 (4.8.0-1ubuntu1) eoan; urgency=medium
* d/p/fix-definition-default-xml-namespace.patch: fixed the definition of the
default XML namespace with lxml 4.4 (LP: #1840141)
-- Andreas Hasenack Tue
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/beautifulsoup4/+git/beautifulsoup4/+merge/371881
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840141
Title:
xmlns
** Changed in: beautifulsoup4 (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: beautifulsoup4 (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Revision 524 includes a fix based on Isaac's pull request.
** Changed in: beautifulsoup
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840141
Title:
xmlns
I imagine this is a side effect of this change in lxml 4.4.0:
When using Element.find*() with prefix-namespace mappings, the empty string is
now accepted to define
a default namespace, in addition to the previously supported None prefix.
Empty strings are more
convenient since they keep al