[issue24069] Option to delete obsolete bytecode files

[Irit Katriel]

Change by Irit Katriel :


--
resolution:  -> rejected
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24069] Option to delete obsolete bytecode files

[Steven D'Aprano]

Steven D'Aprano added the comment:

This would be risky, as byte-code only libraries do exist.

I think that deleting orphaned .pyc files from inside the __pycache__ directory 
is safe, but deleting orphaned .pyc files outside of that risks deleting 
legitimate byte-code libraries which are in use.

--
nosy: +steven.daprano

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24069
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24069] Option to delete obsolete bytecode files

[Brett Cannon]

Changes by Brett Cannon br...@python.org:


--
versions: +Python 3.5 -Python 3.4

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24069
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24069] Option to delete obsolete bytecode files

[Sworddragon]

New submission from Sworddragon:

The library compileall has the option -f to force the rebuilding of the 
bytecode files so I thought maybe there could also be an option to delete all 
bytecode files which haven't a non-bytecode library anymore.

--
components: Library (Lib)
messages: 242189
nosy: Sworddragon
priority: normal
severity: normal
status: open
title: Option to delete obsolete bytecode files
type: enhancement
versions: Python 3.4

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24069
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com