| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This is following the advice provided in https://matija.suklje.name/how-and-why-to-properly-write-copyright-statements-in-your-code
|
|
|
|
|
|
|
|
| |
Now that Python 3.7 is the minimum Python version, typing can be done
inline, which makes it easier for mypy to know the files to check.
Indeed, all the files are now typechecked, which uncovered a few minor bugs
and mistakes here and there.
|
|
|
|
|
|
|
|
|
|
|
| |
The f-strings formatted strings are generally simpler to write, read and
debug, with a few exceptions.
Keep the logging strings lazy, keep the CSV-building with %-formatting, as
it makes it more readable.
In fsoptium, keep `'$%s\r\n'` as a %-format, to avoid making it
`f'${command}\r\n'` that would make it easy to mistake for a Shell variable.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
At least the FreeStyle Precision Neo appears to be able to report an invalid
date/time (255/255/255 255:255), probably when the RTC is lost (see issue #58).
This returns a more precise output than N/A, and should suggest to confirm the
date and time setting instead.
|
|
|
|
|
|
|
|
|
|
| |
Most of the epydoc metadata (author, copyright, email) is duplicate in
the package's setup.py or README. These copies are more likely to get out
of date, and increase the amount of work to keep them in line.
The license information should rather be provided with an SPDX identifier,
which is more similar to what the Linux kernel and other projects, such as
pyserial, do.
|
|
|
|
|
|
|
|
| |
Due to EURid threatening to suspend my domain, make sure that the
references are updated to point at the right stable domain.
This includes changes to the files as well as a mailmap to update the
author references in the log.
|
|
|
|
| |
Fixes the nested exception reported in Issue #50.
|
| |
|
| |
|
|
|
|
|
| |
I'm currently implementing a separate HID-based driver that does not use
the Abbott protocol, so this makes my life easier.
|
|
|
|
|
|
|
|
| |
This requires the drivers to validate their device, but also means they can
provide a more explicit error message for the user as to what should be
passed.
This is a first step to help solving Issue 9.
|
|
|
|
|
| |
Most glucometers have *some* sort of checksum, so there is no reason to
implement this on a per-driver basis.
|
| |
|
|
|
|
|
| |
This driver supports dumping of (glucose) readings and reading/setting the
clock.
|
|
|
|
|
| |
There is no reason for me to use GPLv3 now that I'm not using the
CRC32-Sick code, so I'll go with the most liberal license out there.
|
|
|
|
|
|
|
| |
This introduced some changes in the Exception class to simplify the
code, and at the same time it adds a module for multiple lifescan
drivers to share code (multiple OneTouch protocols share the same
checksum for instance).
|
| |
|
|
|