-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathCHANGELOG
54 lines (44 loc) · 1.93 KB
/
CHANGELOG
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
## 0.8.3
* Fixed KeyError for missing 'GRIDSQUARE' in logs
## 0.8.2
* Correcting quotes values handling in .env
* Updating Makefile for better local testing
## 0.8.1
* adjusting re-syntax for python 3.12 compatibility
* switching to Debian bookworm for builds & tests
* Testing in docker using python 3.10, 3.11, 3.12
* linting using flake8 & pylint
* building docker image & uploading to hub.docker.com
* reworked README.md
## 0.8
* switching to Debian bullseye (11.6) for builds & tests
* removed python2 support, keeping only python3.X
* corrected IOError exceptions handling
* corrected various smaller typos
## 0.7
* added qrz.com api-response handling
## 0.6
* A local cache of QSO entries is built when adding records to logbook.
The app will not retry to upload the cached entries then again and again stumbling upon QRZ.com's error messages
about "duplicates".
Caching is now a default behaviour when "delete" flag is not in use (which is also the default).
## 0.5
* The app can now handle partially corrupted log lines
* improved debug logging
* improved qrz.com api response logging
* updated documentation
## 0.4
* Added xml lookups ability via xml-interface of qrz.com.
While WSJT-X provides only 4 chars of the grid locator, on 2m the precision of 4 chars long locator and 6 chars long
is quite a difference. The new functionality fetches provided grid locator data - if available - for the given callsign
and enriches the QSO data before saving in qrz.com's logbook.
## 0.3
* the "idle" message, thus message when an empty log is processed, is now not written into logfile by default.
This prevents the log to grow only because of these, not really interesting, log records. The new switch "-e" allows,
however, to re-enable it, so on every run you can see whether the script was actually executed or not.
## 0.2
* ensured python3 compatibility
* corrected connection error handling
* corrected remote call display in logs
## 0.1
* initial release