Borgapi

Latest version: v0.7.0

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

Scan your dependencies

Page 1 of 2

0.17.1

- Info on how to set and unset environment variables

Changed
- Formated the README to have shorter line lenghts, no changes in display
- Removed the Roadmap item for loading environment variables

0.7.0

Added
- Borg command `recreate` and `import-tar` [24]
- Async class! Now you can view output logs while the command is running and not only
when it has completed. This makes the `--progress` flag not useless. [21]
- Support for Python version 3.12 and 3.13
- Add `environ` argument to the `BorgAPI` constructor
- Load default environmental variables to prevent the api from freezing while waiting for
user input. They won't be overriden if they are already set. See README for list of
variables that get set and their defaults. [20]

Changed
- Borg version bumped to 1.4.0
- Changed the version requirements for `borgbackup` and `python-dotenv` to use compatible
release clause (`~=`) instead of a version matching (`==`) clause. This should allow any
security patches published to still work while any minor chagnes will need to be verified.
- Using `ruff` to lint and format now. Previously used `pylint` to lint and `black` and
`isort` to format.

Removed
- No longer support Python 3.8 because borgbackup no longer supports that version.

0.6.1

Changed
- Borg version bumped to 1.2.4
- Dotenv version bumped to 1.0.0 in "requirements.txt"

0.6.0

Added
- Borg command `compact`

Changed
- Borg version bumped to 1.2.3
- Dotenv version bumped to 1.0.0
- Dropped support for Python 3.6 and 3.7
- Added support for Python 3.11
- Default log level is "warning" instead of "info"
- Capturing json output uses Borgs JsonFormatter for the logger
- Log level is passed for each command so individual command calls can accurately refelct wanted
output, before if `log_json` was used, it ignored log level

Fixed
- Mounting / Unmounting tests failing due to OS taking some time, added a longer sleep to prevent
them from failing
- `fuse` in the optional install requirements was the incorrect name of the package,
changed to `llfuse`
- Readme reflects acutally current return values for commands, had still referenced an old style

0.5.0

Changed
- Commands not returns a single value
- If multiple values are captured, a `dict` is returned with relevant key names
- Single value is returned by itself
- No captured value returns `None`

Fixed
- Missing benchmark test added back in

0.4.0

Changed
- Type hint for command returns changed to custom type hint `BorgRunOutput` which is a tuple
`Union[str, dict, None]` for stdout and stderr capture

Fixed
- `change`
- `changes` argument now positional magic variable. (`*changes`)
- Passing in strings to get the values returns a list
- Passing in tuples to set the values returns None
- `import` and `export`:
- Appends `path` to end of args instead of trying to extend because only one path can be passed
- `benchmark_crud`:
- Command is now added as two seperate words instead of one
(`"benchmark crud"` -> `["benchmark", "crud"]`)
- `ExclusionOptions`:
- `pattern` now processed as a list

Page 1 of 2

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.