This removes the legacy GTK GUI from the tree. This is not being
maintained, doesn't work very well, and I'm tired of accidentally
editing files here when I mean to edit wxui/*. When we announce the
chirp-next stuff to the users, I don't want packagers to be confused
about which version to use, what the required dependencies are, etc.
Data files outside the package are not installed in binary distributions, so move them inside. Use importlib_resources to load icon and stock configs.
- use only the newer files(), as_files() and namespace APIs introduced in Python 3.10
- use the importlib_resources package if Python < 3.10
- remove obviated pkg_path()
- bump minimum Python version to 3.7
Fix test paths to account for the move
This is for drivers that share a cloning protocol module with other
tested drivers *and* are tested on a static image in the tree. For
example, all the kenwood live drivers use the same few routines for
communicating with the radio. Icom clone-mode radios (with one
exception) use the icf module for cloning and thus there's really
nothing to convert in the drivers themselves.
First, I was imperfect in my matching of models with special
characters (spaces, parens, slashes, etc) so those were not
represented here.
Second, I wasn't including aliases in the market share for the parent
radio.
This substantially alters the stats (in a good way for total
completion).
This adds some stats about which models are the most widely used to
the test matrix to help guide decisions about total testing versus
relevant testing.
Model stats are captured from our own databases, and are far from
perfect, but are probably sufficiently useful. Stats captured on
9-Dec-2022.
This should be used for drivers that are either exactly identical to
another (i.e. a subclass with only vendor/model changes) or which
can be tested with another model radio with only constraint
differences (i.e. a GMRS-locked version of an amateur model).
Converting a driver to pass tests on python3 is not quite the same
as it actually working in the real world. We need to keep track of
which drivers have been tested in the wild, separate from those that
merely pass tests.
This adds a file tests/py3_driver-testers.txt, which is a simple list
of the driver ID key and the person/date when it was tested. Running
the "makesupported" tox target will also generate
tests/Python3_Driver_Testing.md, which will be render-able in github
for easy viewing.
If you test a driver on python3, please add a line to the tracking
file, run the makesupported target, and update the markdown file.
This looks like a lot of change, but it was pretty trivial. Many
of the conflicts came from d40963b3ed
which fixed a bunch of typos. There were some test adapter changes,
some GTK UI fixes, RR canada additions, and the usual driver
maintenance.
I didn't test the GTK UI since it seems like we're abandoning keeping
that working in python2 or python3 with pygobject (which is fine).
This patch adds support for the Wouxun KG-UV920P-A dual-band mobile transceiver.
Tested on my own KG-UV920P-A. May work with other similar models, but I only
have this one to test against. Based loosely on the KG-UV8D driver.
Addresses #386
I didn't catch that this wasn't in the manifest during review,
and thus the style issues didn't get flagged. Adding it to the
manifest and fixing those here.
Related to #8591
This never really caught on, nor got the attention or maintenance it really needed.
I dunno if it even works in py2 for much anymore, but I don't think converting it
to py3 makes any sense.
(cherry picked from commit 89c85eeeb4)
This patch adds support for the TYT TH-UV88
Initial radio protocol decode, channels and memory layout
by James Berry <james@coppermoth.com>, Summer 2020
Related to #7817
This patch only cleans up driver style issues prior to adding support
for new models. There are no changes in functionality.
Add baofeng_wp970i.py driver to cpep8.manifest
Clean up driver style issues (correct indentation, remove whitespace,
add/remove blank lines, etc)
related to #7163
This never really caught on, nor got the attention or maintenance it really needed.
I dunno if it even works in py2 for much anymore, but I don't think converting it
to py3 makes any sense.
#495
I forgot to add it to the manifest, so I didn't notice these:
./chirp/drivers/kguv9dplus.py:982:74: E222 multiple spaces after operator
./chirp/drivers/kguv9dplus.py:1031:80: E501 line too long (80 > 79 characters)
./chirp/drivers/kguv9dplus.py:1032:80: E501 line too long (80 > 79 characters)
./chirp/drivers/kguv9dplus.py:1890:26: W291 trailing whitespace
Related to #3509
