Automatically clean up cached downloads
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 344
- Forks
- 74
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 7
Description
Background
According to the documentation, the download_dir directory "is a temporary cache, and can be cleaned up from time to time."
Details
If the download_dir directory is a temporary cache, wouldn't it make sense for the default to be %TEMP%\Python (or something similar), rather than a subdirectory of the global_dir directory?
Why?
-
Files in
%TEMP%should be assumed to be temporary (hence the name), so wouldn't it make sense to put temporary downloads there? -
Files in
%TEMP%are, I believe, subject to the Windows automatic "clean up temporary files" feature, aren't they? In this way, old downloads would get cleaned up automatically, wouldn't they? (I'm not an expert on this feature, so I may be all wet here.)
I'm new to this project, so I'm sure others will set me straight if I'm way off here...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing where the download_dir and global_dir defaults are defined and read the linked Windows administrative-configuration documentation. Check how Windows temporary-file cleanup applies to the proposed location; done would require an agreed default location, documented behavior, and tests or verification for the resulting configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100