Project

General

Profile

Actions

Bug #3167

closed

Chirp 0.4.1 is incompatible with pyserial v3

Added by Nick oe over 8 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
-
Category:
-
Target version:
-
Start date:
01/15/2016
Due date:
% Done:

0%

Estimated time:
Chirp Version:
0.4.0
Model affected:
(All models)
Platform:
Linux
Debug Log:
I read the instructions above:

Description

I just upgraded to pyserial 3.0 on archlinux the other day, and this cause upload and download in chirp to fail with:

$ chirpw 
ERROR: -- Exception: --
ERROR: Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/chirp/ui/clone.py", line 238, in run
    self.__radio.sync_in()
  File "/usr/lib/python2.7/site-packages/chirp/drivers/uv5r.py", line 705, in sync_in
    raise errors.RadioError("Failed to communicate with radio: %s" % e)
RadioError: Failed to communicate with radio: 'Serial' object has no attribute 'setTimeout'

ERROR: ----------------
ERROR: Clone failed: Failed to communicate with radio: 'Serial' object has no attribute 'setTimeout'
ERROR: --- Exception Dialog: Failed to communicate with radio: 'Serial' object has no attribute 'setTimeout' ---
ERROR: None

ERROR: ----------------------------

I tested with chirp 0.4.1 and the latest as of yesterday.

So the issue is that the setTimeout API has been removed from pyserial v3 and was already deprecated in v2. Please see the thread on pyserial:
https://github.com/pyserial/pyserial/issues/66

So I suggest that chirp will adopt the suggestion mentioned in the pyserial issue.

Actions

Also available in: Atom PDF