Autocrop

Latest version: v1.3.0

Safety actively analyzes 682361 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 2

0.3.1

Not secure
Changes

* Add `-r`, `--reject` flag to specify directory where the images that autocrop *couldn't* find a face in are directed to.
* Instead of having the target files copied then cropped, they are instead cropped and saved to their respective target folder.

0.3.0

Not secure
Changes

* Added support for padding (`padLeft`, etc.) in the CLI.

Bugfix

* Fixed warp on crop for `-w` and `-h` values

0.2.0

Not secure
Changes

* Add `-o`, `--output` flag to specify directory where cropped images are to be dumped.
- Error out if output folder set to current directory, i.e. `-o .`
- If directory doesn't exist yet, create it.
- If no face can be found in an image in batch, it is still copied over to `-o` folder.
- If no output folder is added, ask for confirmation ([Y]/n), and destructively crop images in-place.
* Use `-i`, `--input` flags as synonyms for `-p` or `--path`: symmetrical in meaning to "output".
- Is now standard nomenclature in documentation.
* `--input` or `--path` flag is now optional.
- Standard behaviour without input folder is to non-recursively process all images in immediate folder, i.e. `-p .` as currently implemented.

Breaks

* Removed all mentions of the hard-coded 'bkp' and 'crop' folders
* Calling autocrop without specifying an input path, i.e. `autocrop` does not look for the 'images' folder anymore.

Page 2 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.