[Bug 1287659] [NEW] python2 crash traceback was not caught, yet python3 one was

[Dimitri John Ledkov]

Public bug reported:

Whilst investigating dial-number crash induced by dialer-app AP tests,
we noticed that whilst both python2+pygtk and python3+gi based scripts
crash, only the python3+gi edition generated a .crash file, the python2
edition does not.

This falsely suggested there was a regression, when python2 crash was
simply not caught...

** Affects: whoopsie (Ubuntu)
     Importance: Undecided
         Status: New

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

Title:
  python2 crash traceback was not caught, yet python3 one was

Status in “whoopsie” package in Ubuntu:
  New

Bug description:
  Whilst investigating dial-number crash induced by dialer-app AP tests,
  we noticed that whilst both python2+pygtk and python3+gi based scripts
  crash, only the python3+gi edition generated a .crash file, the
  python2 edition does not.

  This falsely suggested there was a regression, when python2 crash was
  simply not caught...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1287659/+subscriptions