[Bug 1160944] [NEW] [raring] python2.7 autogenerate all the *.pyc files

[Jamie Strandboge]

Public bug reported:

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 on raring. Eg:

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

** Affects: python2.7 (Ubuntu)
     Importance: Undecided
         Status: New

** Summary changed:

- [raring] python2.7 doesn't have all the *.pyc files
+ [raring] python2.7 autogenerate all the *.pyc files

-- 
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] python2.7 autogenerate all the *.pyc files

Status in “python2.7” package in Ubuntu:
  New

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 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