[chirp_devel] Python3 Update - Need Help Testing

Joe Pizzi
Sun May 23 15:54:09 PDT 2021


I've decided to try my hand at this port.

I found the run_tests.py file in the tests folder, and am going through 
everything in there to ensure it doesn't crash or fail. I have the 
latest pull from Mercury, and am running all the tests there, too, to 
ensure they don't fail (or crash) in that version - I bet they don't.

Right now, I've gotten to the Wouxun radios, and am having an issue with 
the mode_password and reset_password settings. I've gotten around the 
problem, but I think there might be a better way to do it. The way I've 
currently done it is in set_settings, where it calls setattr(obj, 
setting, element.value) I've tested element.value to see if it is a 
dict_values instance, and if it is, I create a list out of element.value 
before calling setattr.

I'm wondering, however, if it wouldn't be better to make the 
mode_password and reset_password lists right off the bat, however?

Joe
KI5LST


On 12/20/2020 9:57 PM, Matthew Poletiek via chirp_devel wrote:
> Hi All,
>
> I've made a lot of progress on getting the latest py3 branch working 
> across multiple platforms. I'm maintaining all my working changes here 
> for now: https://github.com/mpoletiek/py3-CHIRP 
> <https://github.com/mpoletiek/py3-CHIRP>
>
> I've even made a list of supported devices and am marking the ones 
> I've personally tested: 
> https://github.com/mpoletiek/py3-CHIRP/blob/main/RADIOS.md 
> <https://github.com/mpoletiek/py3-CHIRP/blob/main/RADIOS.md>
>
> Currently I only own a BF-F8HP so I've marked all the Radios that use 
> that driver `TESTED`.
>
> I've been playing around with Tox and testing the other drivers that 
> way too. With a few changes I was able to get it working and run every 
> test against every driver. A lot of them passed every test just fine, 
> but a lot of them are failing here and there.
>
> As expected the debug.log is quite long and I figured I'd go through 
> the drivers one by one that way, but the recommended syntax for doing 
> that doesn't seem to work as expected.
>
> https://chirp.danplanet.com/projects/chirp/wiki/DevelopersProcess 
> <https://chirp.danplanet.com/projects/chirp/wiki/DevelopersProcess>
>
> `tox -e driver -- -d Icom_IC-2820H`
>
> Running this command gives me the following in a Python3.7 environment:
>
> |`ERROR: MISSING test execution (tx) nodes: please specify --tx` |
> |When I add '-n 2' or `--tx popen//python=python3.7` to the pytest 
> command it exits with `code: 5 (no tests run)` |
> |Anyone familiar enough with tox to help me out with this? |
> |There's also a py3driver env setup in the tox.ini file, but that 
> doesn't work either. |
> |Thanks, |
> -------------------------------------------
> Matthew Poletiek
> 303.810.9082
> matthew.poletiek at gmail.com <mailto:matthew.poletiek at gmail.com>
> www.matthewpoletiek.com <http://www.matthewpoletiek.com>
>
>
>
> _______________________________________________
> chirp_devel mailing list
> chirp_devel at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers

-- 
Joe Pizzi

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20210523/315ca105/attachment-0001.html 


More information about the chirp_devel mailing list