Pynonymizer

Latest version: v2.2.1

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

Scan your dependencies

Page 4 of 7

1.16.0

Added
- Added support for LZMA `*.xz` compression on file output. To use this feature, Specify an output path ending with `.xz`.
Changed
- Minor improvements to internal test suite.

1.15.0

Added
- Added main function `run` exposure to `pynonymizer` package.
Check out pynonymizer/pynonymize.py for more usage information
python
from pynonymizer import run

- Added more documentation to reflect usage & project features.
Changed
- Exclude `tests/` directory from pip package.

1.14.0

Added
- Added `fake_update` Strategy feature: `sql_type`: Choose an sql datatype to cast to when anonymizing values. The new value will be cast to the chosen datatype.
Fixed
- Fixed PostgreSQL column escaping. Keywords like `SELECT`, `FROM` or `WHERE` can now be used in strategy files.

1.13.0

Added
- Added new table strategy `DELETE`, which should delete _with_ checks (e.g. foreign keys) on most providers.

1.12.0

Added
- Added ability to pipe output to/from pynonymizer from stdout, using `-` in place of the input/output arguments. This functionality is available for mysql and postgres providers.

This means you can now use pynonymizer as part of a pipeline with other tools, e.g.

mysqldump [...] | pynonymizer -i - -o - | aws s3 cp - s3://bucket/aws-test.tar.gz

Changed
- Changed default logging output to stderr. This is to facilitate stdin/out being used for data.
Removed
- Removed production logging feature in favour of stderr/out logging. Logging to files will no longer by considered pynonymizer's concern.

1.11.2

Changed
- Changed package metadata to improve PyPI presence.

Page 4 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.