Dbfpy3

Latest version: v4.2.2

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

Scan your dependencies

Page 2 of 3

2.2.1

---------------------------

Fix: raise ValueError if a name passed to field constructor
is longer than 10 characters.

2.2.0

---------------------------

Features:
- date fields are allowed to contain values stored with leading spaces
instead of leading zeroes.
- dbf.header returns field definition objects if accessed as a list
or as a dictionary.
- added raw data access methods: DbfRecord.rawFromStream(),
DbfFieldDef.rawFromRecord().
- added conversion error handling: if ignoreErrors=True is passed
with Dbf constructor arguments, then failing field value conversions
will not raise errors but instead will return special object
INVALID_VALUE which is equal to None, empty string and zero.
.ignoreErrors property of the Dbf instances may be toggled also
after instance initialization.

2.1.0

---------------------------

Features:
- support field types 'F' (float), 'I' (integer) and 'Y' (currency)

Fix processing of empty Timestamp values

2.0.3

---------------------------

Fixes:
- compatibility fix for Python versions prior to 2.4 (sf bug 1574526)
- wrong record length when reading from file object (sf bug 1586619)

2.0.2

---------------------------

Fix dbfnew (legacy API for DBF creation)

2.0.1

---------------------------

Fixes in Numeric field processing:
- decoding inserted decimal point where it shouldn't;
- encoded value never exceeds field length.
If encoded value is too large for the field, decimal digits get
removed (rounding the value down). When integer value is larger
than the field length, ValueError is raised.

Fix: Date and Logical fields were not able to decode empty values.

Errors raised from field processing include field name.

This file is included in the source distribution.

Page 2 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.