[chirp_devel] chirp-py3 status?

[James Keener]

It sounds like others have a much better idea of the state of the project
than I do, so please consider me as a resource to farm any work out to. I
only have Linux, a UV5R, and a TM-V7 but can ensure those work and work on
the UI, RepeaterBook interface, RadioReference interface, &c

Jim

On Fri, Dec 11, 2020 at 10:03 AM Matthew Poletiek via chirp_devel <
chirp_devel at intrepid.danplanet.com> wrote:

> More good news....
>
> I got this working in Windows 10 after fixing a USB Serial driver issue.
>
> Looks like we have a working Python 3 version in Linux, Mac, and Windows.
> It's definitely not as good as the main branch. Missing quite a few
> features (like importing from RepeaterBook), but it's definitely a start.
>
>
> -------------------------------------------
> Matthew Poletiek
> 303.810.9082
> matthew.poletiek at gmail.com
> www.matthewpoletiek.com
>
>
>
>
> On Fri, Dec 11, 2020 at 8:35 AM Matthew Poletiek <
> matthew.poletiek at gmail.com> wrote:
>
>> Good news. I got this running in windows this morning.
>>
>> I had to use the chirpwx.py script to bring it up.
>>
>> I installed python3.9 for windows and used pip to bring in all the
>> dependencies.
>>
>> pip install pypiwin32
>> pip install wxpython
>> pip install six
>> pip install future
>> pip install pyserial
>>
>> Still working on getting a download from my radio though. Issue might be
>> related to the fact I'm running windows 10 in a VM. Continuing to test, but
>> it looks like we have a path forward in windows.
>>
>> -------------------------------------------
>> Matthew Poletiek
>> 303.810.9082
>> matthew.poletiek at gmail.com
>> www.matthewpoletiek.com
>>
>>
>>
>>
>> On Thu, Dec 10, 2020 at 10:52 PM Matthew Poletiek <
>> matthew.poletiek at gmail.com> wrote:
>>
>>> Hi Mark,
>>>
>>> I'd rather not at this time. Honestly I'd like to focus on getting a
>>> working Python 3 version up and running and while cloning the main branch
>>> and uploading it to github is easy, publishing is not.
>>>
>>> I was able to get the current py3 branch (with some tweaks) running in a
>>> few different linux distros without issue. @Nicolas Pike
>>> <nicolas at jetblackjelly.com> was able to get it running on his mac and
>>> was able to download and upload to a BF88s.
>>>
>>> I'm really struggling with Windows though. I have a Windows 10 VM
>>> running, but getting a proper environment setup to test the py3 branch as
>>> it's written is proving difficult.
>>>
>>> I can't get Python3.9 for Windows 10 to compile PyGObject. When I follow
>>> the documentation on PyGObject's site they recommend using MSYS2, but I
>>> can't get a working version of pypiwin32 (win32api) up and running in
>>> MSYS2. Kindof feels like a rock and a hard place. I might have to compile
>>> my own GTK3 libraries for Windows just to be able to publish something for
>>> Windows which is probably 90% of the user base.
>>>
>>> If anyone has any tips I'd really welcome them. I'm continuing to submit
>>> patches against the py3 branch (https://chirp.danplanet.com/issues/8545),
>>> but I'm also maintaining all my fixes on github:
>>> https://chirp.danplanet.com/issues/8545
>>>
>>> Thanks,
>>>
>>> -------------------------------------------
>>> Matthew Poletiek
>>> 303.810.9082
>>> matthew.poletiek at gmail.com
>>> www.matthewpoletiek.com
>>>
>>>
>>>
>>>
>>> On Thu, Dec 10, 2020 at 3:50 PM Mark Leigh <mark.leigh at shaw.ca> wrote:
>>>
>>>> Hi Matthew,
>>>> As I understand the maintainer is not currently working on CHIRP due to
>>>> (medical?) issues, would you be interested in forking the main branch as
>>>> well? There have been a number of commits but none have been incorporated
>>>> since late November.
>>>> Thanks,
>>>> -Mark
>>>>
>>>> ------------------------------
>>>> *From: *"Matthew Poletiek via chirp_devel" <
>>>> chirp_devel at intrepid.danplanet.com>
>>>> *To: *"RepeaterBook admin" <admin at repeaterbook.com>, "chirp devel" <
>>>> chirp_devel at intrepid.danplanet.com>
>>>> *Sent: *Thursday, December 10, 2020 6:42:21 AM
>>>> *Subject: *Re: [chirp_devel] chirp-py3 status?
>>>>
>>>> Awesome!
>>>>
>>>> Stay tuned. I'm still trying to get a working dev environment in
>>>> Windows.
>>>>
>>>> On Wed, Dec 9, 2020, 2:51 PM RepeaterBook admin via chirp_devel <
>>>> chirp_devel at intrepid.danplanet.com> wrote:
>>>>
>>>>> If you have issues with RepeaterBook that I can help with, please let
>>>>> me know. I am using Cloudflare and have a firewall rule that only let’s the
>>>>> server IP for CHIRP through. We occasionally get folks building their own
>>>>> programs and attempting to use the CHIRP API to funnel data to their own
>>>>> applications (I think). Hopefully I wasn’t blocking legit uses and testing
>>>>> with this project. The user agent even reported as CHIRP, but that can be
>>>>> faked.
>>>>>
>>>>> I’d also like to clean up the queries a bit. Maybe expand the search
>>>>> criteria. CHIRP is also hitting two URL’s and we can reduce that to one.
>>>>>
>>>>>
>>>>> *Garrett Dow**, KD6KPC/WREQ745 *
>>>>>
>>>>> *Owner, RepeaterBook.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
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>> _______________________________________________
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20201211/e190af89/attachment-0001.html