[Bug 1123193] Re: No python2 support for CommandNotFound anymore

[Launchpad Bug Tracker]

This bug was fixed in the package command-not-found - 0.3ubuntu7

---------------
command-not-found (0.3ubuntu7) raring; urgency=low

  [ Danilo Segan ]
  * Reintroduce Python2 support with python-commandnotfound package.
    (LP: #1123193)

  [ Barry Warsaw ]
  * Move the Python 3 library to the python3-commandnotfound package, and
    build depend command-not-found on that.
  * debian/control: Bump to Standards-Version: 3.9.4
  * debian/rules: Remove --without=python-support as no longer needed.
 -- Danilo Segan <danilo at kvota.net>   Wed, 20 Feb 2013 09:51:10 +0100

** Changed in: command-not-found (Ubuntu)
       Status: In Progress => Fix Released

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

Title:
  No python2 support for CommandNotFound anymore

Status in “command-not-found” package in Ubuntu:
  Fix Released

Bug description:
  Since 12.10, there is no Python2 library for accessing command-not-
  found functionality: if a program was using it, it will stop working
  after upgrade to Quantal. An example of such a project is Linaro Image
  Tools which relies on CommandNotFound to find packages missing
  commands are in.

  Solution is either to port code to Python3 (very hard) or simply to
  keep providing a python2 package of command-not-found library.

  A test case is simple:

    python -c "import CommandNotFound"

  I'll be linking a branch (based on lp:ubuntu/quantal/command-not-
  found) that introduces python-command-not-found package with Python2
  libraries: I am sure I've done many things wrong in it, and I'd be
  happy to get any comments on it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1123193/+subscriptions