Pynonymizer

Latest version: v2.3.1

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

Scan your dependencies

Page 5 of 8

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.

1.11.1

Fixed
- Fixed an incorrectly labelled version string: `1.11.10`. Re-releasing under this version.

1.11.0

Changed
- Changed mysql provider to include an arbitrary delay after anonymize_db, to prevent
interference with transactional dump `mysqldump` calls.
Removed
- Removed the database connection pre-test as its use suggests conditions about the database
that are not present in all circumstances with all providers. Pynonymizer will no longer test a connection as part of a dry-run.

1.10.1

Changed
- Fixed a confusing note in the README.md that was introduced accidentally

1.10.0

Added
- Added `--mysql-dump-opts`/ `$PYNONYMIZER_MYSQL_DUMP_OPTS` to allow custom command overrides to the mysqldump process.
Fixed
- Fixed a bug where complex arguments to faker could cause an invalid seed table column name to be generated.

Page 5 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.