Pynonymizer

Latest version: v2.4.0

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

Scan your dependencies

Page 6 of 8

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.

1.9.0

Fixed
- Fixed a bug where using no fake_update columns would cause an error
Changed
- Changed Documentation for `fake_update` strategies to remove an erroneous example type.

1.8.0

Added
- Added `--dry-run` / `$PYNONYMIZER_DRY_RUN` option to run all the non-destructive fail-fast options without fear of actual process execution.
Fixed
- Fixed a bug in mysql provider where using the default unspecified port would cause an error.
- Fixed a bug in postgres provider where seed_rows was being ignored.
- Fixed a bug in the Postgres provider that would cause all rows to be updated with the same 'random' value.
- Fixed a bug in mysql/postgres providers that would cause before/after scripts to fail to run.

1.7.0

Added
- Added option `--db-port`/`-P`/`$PYNONYMIZER_DB_PORT` to specify your database provider's connection port.
- Added option `--verbose` to increase the verbosity of the logging feature. Currently, this is used to log more info
from a database error, but more areas will be included in future.

1.6.2

Fixed
- Fixed a mysql provider issue: in MariaDB, multiple string columns in a strategy could cause a row length error when constructing the seed table.

1.6.1

Fixed
- Fixed a bug where static code relying on pyodbc would cause a ModuleNotFoundError

Page 6 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.