Dbfpy3

Latest version: v4.2.2

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

Scan your dependencies

Page 3 of 3

2.0.0

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

Changed style of doc-strings; added more docs.

``mx.DateTime`` isn't required anymore - internal representation uses
``datetime.date`` and ``datetime.datetime`` classes from the batteries.

'D' and 'T' became "smarter":
- date fields could accept:
- date/time tuples [or tuples with at least
first three components (year, day, month)];
- strings in format 'yyyymmdd' or 'yymmdd';
- ``datetime.date`` and ``datetime.datetime`` instances;
- ``None`` instance - use current date value;
- numbers (``int``, ``long``, ``float``)
which are treated as seconds from epoch;
- objects having 'ticks' method (``mx.DateTime`` for example);
- datetime fields can accept everything date fields do
except string objects (which is a TODO stuff).

Changed identifiers and args of some methods. For example old code

dbf = Dbf()
dbf.openFile("county.dbf", readOnly=1)

now should be written like

dbf = Dbf("county.dbf", True)

All classes now are new-style classes (inherited from the ``object``).

Got rid of ``binnum`` and ``strutil`` modules,
using ``struct`` and string methods instead.

Group classes in different modules instead of having them all in
one, as it was earlier (see dbf.py from the previous release(s)).

Use fields' registry to simplify registering of the new data types.


Previous changes:
-----------------

took over development 2000-10-06 Hans Fiby

changes: 2001-02-07 Hans Fiby
* read long integers as long
* add this CHANGES File

changed: 2000-10-06 Hans Fiby
* added dbfnew.py
* fixed decimal points

0.1.0

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

* First release on PyPI.

Page 3 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.