Rossen
Rossen
> I thought I should explain why we are not using coveralls 1.x on Python 2.7, and the main reason is that it does not combine reports with coverage 2.x...
Hi @craigerl, thanks for the report. Look to me like the packet is parsed correctly. `]=` is whats left in the comment. From the APRS protocol document I can see...
Could you provide examples of such messages? Just because someone is not following that spec, doesn't mean we have to change the library to accommodate their misuse. Exception being if...
APRS full feeds is full of invalid messages, so it is not unusual to see parse errors. It possible that some of them are bugs in library, that needs to...
The error logged is when attempting to read from socket that has not received anything yet. That a result of setting `blocking=False`. The call returns immediately, or processes any packets...
Comment telemetry format is different. Telemetry report is not implemented, since I never needed it. I may implemented it soon™
Hi @hemna, thanks for the PR. Not sure what the exact use case for this would be, but it doesn't make sense to me to be part of the package....
Hi @wsmitchell3, thanks for the contribution, but I feel this doesn't need to part of the package. It can be reduced to single line `path = list(filter(lambda x: not re.match(r'WIDE[0-9\-\*]+$',...
This PR no longer includes the original units/label code
I need to do some refactoring to make `packets` fit with how `parsing` is doing things. I might introduce breaking changes to `parsing`. I will try find time to figure...