Parsyfiles

Latest version: v2.9.1

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

Scan your dependencies

Page 3 of 4

2.4.4

* Added a global configuration that can be changed by calling `parsyfiles_global_config(...)`. The only option available for now is controlling the traceback size in case of several parsers exceptions. This fixes [9](https://github.com/smarie/python-parsyfiles/issues/9)

2.4.3

* logger customization was not taken into account - fixed [7](https://github.com/smarie/python-parsyfiles/issues/7)

2.4.2

* does not use internals from `typing` anymore but relies on `typing_inspect` API to guarantee the stability, see https://github.com/smarie/python-parsyfiles/issues/4
* minor travis configuration

2.3.1

* Important bug fix for 2.3.0: custom parsers/converters were appearing in the capabilities but not used. Added a test to prevent this kind of regression to happen again.
* Improved 'usage' documentation page
* Reorganized tests and documented them for better readability, and improved some of them (primitive types, default parsers)
* Test failure do not make travis builds fail anymore
* Fixed file system mappings: now '.' is not mandatory for relative paths

2.3.0

Improved verbosity, quality of parser and converter combinations, performance, sorted collections

**PARSER/CONVERTER COMBINATION ENGINE**

* replaced `None` with an explicit `JOKER` for all 'find' parsers/converters methods. Added sanity check at parser registration time: check that parser handles `JOKER` properly
* split `is_able_to_parse` and `is_able_to_parse_detailed` (and the same for convert) so that the first returns a single boolean while the second returns a tuple. This fixed a number of bugs with parser/converter chain generation
* fixed bug with generic parsers by now using the same piece of code than others for registration
* generic parsers and converters are now allowed to chain with other converters. `is_able_to_convert` is therefore now called at runtime on the value generated because it could not fit the required input of the next element
* fixed a few errors in the plugins so that their chaining is correct

**API**

* better error message when the provided location has an extension
* better separation of logging messages between info and debug
* created a true base `ConversionException`
* added package-level methods to access capabilities easily
* `get_capabilities...` methods now do not return some keys when they are empty: the result is more compact to read
* Added `OrderedDict` so that parsing collections now returns a sorted `list/set/dict/tuple`

**PERFORMANCE**

* Big performance improvement for `_get_constructor_signature`, thanks to profiling
* Big performance improvement for `var_checker`, thanks to profiling
* added singleton cached instance for `RootParser` with default plugins so as not to pay the registration costs several times

**TRAVIS INTEGRATION**
* tests, code coverage, doc generation, and releases deployment on PyPI are now automated

2.2.0

* added new behaviour : genaric parsers can chain with converters. In some cases this may unlock new capabilities (for example parsing object A from its constructor then converting A to B might sometimes be interesting, rather than parsing B from its constructor)
* fixed bug in is_able_to_convert: when from_type was any, the result was False > this was preventing the above use case to execute
* fixed bug with automatic type conversion in collections

Page 3 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.