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

Jamie Strandboge jamie at ubuntu.com
Wed Mar 27 16:46:36 UTC 2013


** Description changed:

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

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

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




More information about the foundations-bugs mailing list