This is not related to this bug and parsing in general. The major problem in the +text view of launchpad bugpages is that pages like https://bugs.edge.launchpad.net/bugs/211759/+text, unlike https://bugs.edge.launchpad.net/bugs/211759, are not redirected, so there is no way to find which of the many tasks should be shown as bug.info.
Redirection examples: https://bugs.edge.launchpad.net/bugs/211759 --> https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/211759 but https://bugs.edge.launchpad.net/bugs/211759/+text is not redirected
if https://bugs.edge.launchpad.net/bugs/211759/+text would be redirected to https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/211759/+text then it would be possible to use LPTasks.current_from_url() to parse 'distro' and 'package' out of the url to identify the task shown as bug.info
Markus
This is not related to this bug and parsing in general. The major problem in the +text view of launchpad bugpages is that pages like https:/ /bugs.edge. launchpad. net/bugs/ 211759/ +text, unlike https:/ /bugs.edge. launchpad. net/bugs/ 211759, are not redirected, so there is no way to find which of the many tasks should be shown as bug.info.
Redirection examples: /bugs.edge. launchpad. net/bugs/ 211759 --> https:/ /bugs.edge. launchpad. net/ubuntu/ +source/ xserver- xorg-video- ati/+bug/ 211759 /bugs.edge. launchpad. net/bugs/ 211759/ +text is not redirected
https:/
but
https:/
if https:/ /bugs.edge. launchpad. net/bugs/ 211759/ +text would be redirected to https:/ /bugs.edge. launchpad. net/ubuntu/ +source/ xserver- xorg-video- ati/+bug/ 211759/ +text then it would be possible to use LPTasks. current_ from_url( ) to parse 'distro' and 'package' out of the url to identify the task shown as bug.info
Markus