Skip to content

Conversation

@gvanrossum
Copy link
Member

@gvanrossumgvanrossum commented Mar 16, 2024

Keep Tools/build/deepfreeze.py around (we may repurpose it for deepfreezing non-code objects), and keep basic "clean" targets that remove the output of former deep-freeze activities, to keep the build directories of current devs clean.

Keep Tools/build/deepfreeze.py, we may repurpose it in the future. Put a line in find . -depth -name '__pycache__' -exec rm -rf{} ';' find . -name '*.py[co]' -exec rm -f{} ';' find . -name '*.[oa]' -exec rm -f{} ';' find . -name '*.s[ol]' -exec rm -f{} ';' find . -name '*.so.[0-9]*.[0-9]*' -exec rm -f{} ';' find . -name '*.lto' -exec rm -f{} ';' find . -name '*.wasm' -exec rm -f{} ';' find . -name '*.lst' -exec rm -f{} ';' find build -name 'fficonfig.h' -exec rm -f{} ';' || true find build -name '*.py' -exec rm -f{} ';' || true find build -name '*.py[co]' -exec rm -f{} ';' || true rm -f pybuilddir.txt rm -f _bootstrap_python rm -f python.html python*.js python.data python*.symbols python*.map rm -f ./usr/local/lib/python3.13/os.py rm -f Programs/_testembed Programs/_freeze_module rm -rf Python/deepfreeze rm -f Python/frozen_modules/*.h rm -f Python/frozen_modules/MANIFEST rm -f jit_stencils.h find build -type f -a ! -name '*.gc??' -exec rm -f{} ';' rm -f Include/pydtrace_probes.h rm -f profile-gen-stamp rm -rf iOS/testbed/Python.xcframework/ios-*/bin rm -rf iOS/testbed/Python.xcframework/ios-*/lib rm -rf iOS/testbed/Python.xcframework/ios-*/include rm -rf iOS/testbed/Python.xcframework/ios-*/Python.framework # Profile data. rm -f *.fdata # Pristine binaries before BOLT optimization. rm -f *.prebolt # BOLT instrumented binaries. rm -f *.bolt_inst that removes Python/deepfreeze, for current devs. TODO: Windows project files
Keep removing deepfreeze.c, to clean up for current devs.
@gvanrossumgvanrossum merged commit 9c7b368 into python:mainMar 18, 2024
@gvanrossumgvanrossum deleted the cleanup-deepfreeze branch March 18, 2024 18:13
vstinner pushed a commit to vstinner/cpython that referenced this pull request Mar 20, 2024
…116919) Keep Tools/build/deepfreeze.py around (we may repurpose it for deepfreezing non-code objects), and keep basic "clean" targets that remove the output of former deep-freeze activities, to keep the build directories of current devs clean.
adorilson pushed a commit to adorilson/cpython that referenced this pull request Mar 25, 2024
…116919) Keep Tools/build/deepfreeze.py around (we may repurpose it for deepfreezing non-code objects), and keep basic "clean" targets that remove the output of former deep-freeze activities, to keep the build directories of current devs clean.
diegorusso pushed a commit to diegorusso/cpython that referenced this pull request Apr 17, 2024
…116919) Keep Tools/build/deepfreeze.py around (we may repurpose it for deepfreezing non-code objects), and keep basic "clean" targets that remove the output of former deep-freeze activities, to keep the build directories of current devs clean.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@gvanrossum@zooba@markshannon