[Bug 1160944] Re: [raring] python doesn't autogenerate all the *.pyc files

[Launchpad Bug Tracker]

This bug was fixed in the package python3.3 - 3.3.1~rc1-2ubuntu1

---------------
python3.3 (3.3.1~rc1-2ubuntu1) raring; urgency=low

  * Merge with Debian; remaining changes:
    - Build-depend on python3:any instead of python3.

python3.3 (3.3.1~rc1-2) experimental; urgency=low

  * Fix byte-compiliation/-removal for the split-out library packages.
    LP: #1160944.
 -- Matthias Klose <doko at ubuntu.com>   Sat, 30 Mar 2013 18:10:53 +0100

** Changed in: python3.3 (Ubuntu)
       Status: Confirmed => Fix Released

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

Title:
  [raring] python doesn't autogenerate all the *.pyc files

Status in “python2.7” package in Ubuntu:
  Fix Released
Status in “python3.3” package in Ubuntu:
  Fix Released

Bug description:
  I have some python applications that are confined with AppArmor. After
  upgrading to raring months ago, I noticed that whenever I started a
  confined application, I would get an AppArmor denial because it would
  try to write out the .pyc file in /usr. Of course, DAC would take care
  of this, but this seems to indicate a problem with autogenerating .pyc
  files during package install on raring. Eg:

  $ ls -1 /usr/lib/python2.7/*py | wc -l
  207
  $ ls -1 /usr/lib/python2.7/*pyc | wc -l
  88

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1160944/+subscriptions