☮ lapeace
Bring peace to your Downloads folder.
Your Downloads folder is chaos: screenshots, PDFs, installers you ran once, zips from three semesters ago. lapeace walks in calmly, sorts every file into its rightful place, and leaves. If you change your mind, it puts everything back.
$ lapeace
☮ lapeace · Downloads
214 restless files seek their place
Images 88 ━━━━━━━━━━━━━━━━━━
Documents 41 ━━━━━━━━
Installers 23 ━━━━━
Archives 12 ━━
Other 50 ━━━━━━━━━━
Bring peace? [y/N] y
✓ 214 files found their place.
undo anytime: lapeace --undo
la peace.
Install
pip install lapeace
No dependencies. Works on Windows, macOS and Linux, Python 3.9+.
Usage
lapeace # tidy ~/Downloads (asks before moving anything)
lapeace ~/Desktop # tidy any folder
lapeace --dry-run # preview only, nothing moves
lapeace -autopilot # no questions, just peace
lapeace --undo # put everything from the last run back
| Flag | Short | What it does |
|---|---|---|
--dry-run |
-n |
Show what would move. Touch nothing. |
-autopilot / --autopilot |
-a |
Skip the confirmation. |
--undo |
-u |
Reverse the last run. |
--version |
-V |
Print the version. |
How it decides
Files are sorted by extension into Images, Videos, Audio, Documents, Spreadsheets, Slides, Archives, Installers, Code, and Other.
lapeace is careful by design:
- Asks first. Nothing moves until you say yes (unless you choose
-autopilot). - Never overwrites. If
Images/photo.pngalready exists, the new one becomesphoto (1).png. - Leaves some things alone: folders, hidden files (including Windows hidden/system files like
desktop.ini), and downloads still in progress (.crdownload,.part, …). - Skips files that are busy. If a file is open in another app, it stays put and lapeace tells you; everything else still moves.
- Remembers. Every run is logged to
~/.lapeace_last_run.json, so--undocan restore it.
Set NO_COLOR=1 if you prefer plain output. On terminals that can't show symbols like ☮, lapeace falls back to plain ASCII.
macOS: the first run may ask whether your terminal can access the Downloads folder. Click Allow.
License
MIT
Metadata
Release files for lapeace 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| lapeace-0.1.0.tar.gz | 6.7 kB | Without provenance | Details for lapeace-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lapeace-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for lapeace-0.1.0-py3-none-any.whl |
Total release size: 13.7 kB
Release files / lapeace-0.1.0.tar.gz
| Download URL | lapeace-0.1.0.tar.gz |
|---|---|
| Size | 6.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
17bcf95199c13115f8b3482e5852d1574e501427c4e8f727199ad14409909a30
|
|
BLAKE2b-256 checksum How to use checksums |
a818ead690571213441bfdc027b392e06f3d40f1ef5a29a4da84f1b0243fa35f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / lapeace-0.1.0-py3-none-any.whl
| Download URL | lapeace-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
82a95875e29a579b62c952adb373915ecf70e12b53d2d16dd9a13aae2a69d2ab
|
|
BLAKE2b-256 checksum How to use checksums |
76d20a46e688bb34472d14a8f7962db8c1785500763a4fbdbbd33137c5208575
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for lapeace 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.