[chirp_devel] [patch] [py3] fixed collections traceback

[Jaroslav Skarvada]

So to be clear, is the [1] the official upstream github CHIRP
repository? Currently, I don't care about the sync, and personally git
is better for me than mercurial, so I will just update my links. But I
think the wiki should also be updated. And another question: is it OK
to PR the patches through the github, or is it required to send them
to this mailing list?

thanks & regards

Jaroslav

[1] https://github.com/kk7ds/chirp

On Mon, Aug 29, 2022 at 4:42 PM Martin Cooper <mfncooper at gmail.com> wrote:
>
> Oh, that's very strange. The Mercurial and GitHub repos are supposed to be mirrors of each other. It looks like there might be an issue with the mirroring process. I'm not sure if it's automated or manual. Dan, any thoughts?
>
> Martin.
> KD6YAM
>
> On Mon, Aug 29, 2022 at 7:17 AM Jaroslav Skarvada <jskarvad at redhat.com> wrote:
>>
>> I cannot find it here:
>> https://chirp.danplanet.com/projects/chirp/repository/show?rev=py3
>>
>> What's the official repository for the py3 port?
>>
>> thanks & regards
>>
>> Jaroslav
>>
>> On Mon, Aug 29, 2022 at 3:02 AM Martin Cooper <mfncooper at gmail.com> wrote:
>> >
>> > This change was already committed on March 7. See:
>> >
>> > https://github.com/kk7ds/chirp/commit/8bc8553ccc169405044f27a1037380fe427997b8
>> >
>> > Perhaps your local tree was out of date?
>> >
>> > Martin.
>> > KD6YAM
>> >
>> > On Sun, Aug 28, 2022 at 4:18 PM Jaroslav Skarvada via chirp_devel <chirp_devel at intrepid.danplanet.com> wrote:
>> >>
>> >> It's for the py3 branch. I tested it with the UV-5R and it worked
>> >> without traceback.
>> >> _______________________________________________
>> >> 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
>>