[issue9761] stale .pyc files aren't cleaned out

2012-11-17 Thread Brett Cannon
Brett Cannon added the comment: Never heard back from OP. -- resolution: -> out of date status: open -> closed ___ Python tracker ___

[issue9761] stale .pyc files aren't cleaned out

2010-09-07 Thread R. David Murray
R. David Murray added the comment: Note that issue 6074 may be relevant to your problem. -- nosy: +r.david.murray ___ Python tracker ___ _

[issue9761] stale .pyc files aren't cleaned out

2010-09-05 Thread Éric Araujo
Changes by Éric Araujo : -- versions: -Python 2.6 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue9761] stale .pyc files aren't cleaned out

2010-09-05 Thread Éric Araujo
Éric Araujo added the comment: Can you reproduce the bug with a newer Python? 2.6 only gets security fixes now, bug fixes go into stable (2.7 and 3.1) and active (3.2) versions. (Minor remarks: Could you set up your email client not to send HTML email to the tracker? It creates unnamed files

[issue9761] stale .pyc files aren't cleaned out

2010-09-05 Thread Éric Araujo
Changes by Éric Araujo : Removed file: http://bugs.python.org/file18735/unnamed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue9761] stale .pyc files aren't cleaned out

2010-09-05 Thread Éric Araujo
Changes by Éric Araujo : Removed file: http://bugs.python.org/file18734/unnamed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue9761] stale .pyc files aren't cleaned out

2010-09-03 Thread Brett Cannon
Brett Cannon added the comment: This could still be an issue with the .pyc files being set with permissions that prevent them from being re-generated. Double-check the .pyc files are read-write and have the proper owners to allow them to be overwritten. -- ___

[issue9761] stale .pyc files aren't cleaned out

2010-09-03 Thread Steve Thompson
Steve Thompson added the comment: Hmmm... this definitely sounds like the issue for version controlled files, but does not explain the issue when installing packages from source. On Sep 3, 2010 3:16 PM, "Amaury Forgeot d'Arc" wrote: Amaury Forgeot d'Arc added the comment: Does your version

[issue9761] stale .pyc files aren't cleaned out

2010-09-03 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc added the comment: Does your version control system let the files read-only by default? In this case, see issue6074. -- nosy: +amaury.forgeotdarc ___ Python tracker

[issue9761] stale .pyc files aren't cleaned out

2010-09-03 Thread Steve Thompson
Steve Thompson added the comment: "Setup.py install". We've also seen this happen when checking our python files out of our version control system. Also seen a .pyc get used when the .py no longer exists, but I could see that being intentional behavior. On Sep 3, 2010 2:57 PM, "Brett Cannon"

[issue9761] stale .pyc files aren't cleaned out

2010-09-03 Thread Brett Cannon
Brett Cannon added the comment: So are you installing new versions of a package you already have installed using ``python setup.py install``? Exactly what command are you using to do the install? -- nosy: +brett.cannon ___ Python tracker

[issue9761] stale .pyc files aren't cleaned out

2010-09-03 Thread Steve Thompson
New submission from Steve Thompson : I'm running pythong 2.6.1 on Windows XP SP3. On many occasions I have ran into cases where I've installed a new package via the package's setup.py (pylint, logilab-common, etc) and new .pyc files don't get generated when I attempt to run the tools/packages.