[chirp_devel] Version of wxPython for py3
Bringing up the py3 branch to have a look at where the UI is, one of the first things I tried was File -> New. This immediately died. It seems that the recently added code for maintaining a recently-opened list relies on a function that was present in old versions of wxPython (e.g. 2.8.x) but has been supplanted by a more flexible set of functions in the latest version (i.e. Phoenix).
This raises the question of what the target version of wxPython is intended to be. There is a comment in the recently added developer module related to Phoenix, so I'd assume that it's intended to work under Phoenix. The question is whether that's what we should be working with, or if support for an older version is also required.
The particular issue I encountered is easily fixed for 2.8.6.0 and later, but I think it would be worth putting a stake in the ground in specifying a minimum version of wxPython as a target, so that people know what they should develop with.
Thoughts?
Martin. KD6YAM
wxPython is now on version 4.1.1, so I’d say at least 4.0.
Joe Pizzi
From: chirp_devel-bounces@intrepid.danplanet.com chirp_devel-bounces@intrepid.danplanet.com On Behalf Of Martin Cooper via chirp_devel Sent: Saturday, September 25, 2021 11:35 AM To: chirp-devel chirp_devel@intrepid.danplanet.com Subject: [chirp_devel] Version of wxPython for py3
Bringing up the py3 branch to have a look at where the UI is, one of the first things I tried was File -> New. This immediately died. It seems that the recently added code for maintaining a recently-opened list relies on a function that was present in old versions of wxPython (e.g. 2.8.x) but has been supplanted by a more flexible set of functions in the latest version (i.e. Phoenix).
This raises the question of what the target version of wxPython is intended to be. There is a comment in the recently added developer module related to Phoenix, so I'd assume that it's intended to work under Phoenix. The question is whether that's what we should be working with, or if support for an older version is also required.
The particular issue I encountered is easily fixed for 2.8.6.0 and later, but I think it would be worth putting a stake in the ground in specifying a minimum version of wxPython as a target, so that people know what they should develop with.
Thoughts?
Martin.
KD6YAM
I’m using wxPython 4.0.7.
What function needs to be changed? I’m still learning wxPython.
On 25 Sep 2021, at 13:25, Joe Pizzi via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
wxPython is now on version 4.1.1, so I’d say at least 4.0.
Joe Pizzi
From: chirp_devel-bounces@intrepid.danplanet.com chirp_devel-bounces@intrepid.danplanet.com On Behalf Of Martin Cooper via chirp_devel Sent: Saturday, September 25, 2021 11:35 AM To: chirp-devel chirp_devel@intrepid.danplanet.com Subject: [chirp_devel] Version of wxPython for py3
Bringing up the py3 branch to have a look at where the UI is, one of the first things I tried was File -> New. This immediately died. It seems that the recently added code for maintaining a recently-opened list relies on a function that was present in old versions of wxPython (e.g. 2.8.x) but has been supplanted by a more flexible set of functions in the latest version (i.e. Phoenix).
This raises the question of what the target version of wxPython is intended to be. There is a comment in the recently added developer module related to Phoenix, so I'd assume that it's intended to work under Phoenix. The question is whether that's what we should be working with, or if support for an older version is also required.
The particular issue I encountered is easily fixed for 2.8.6.0 and later, but I think it would be worth putting a stake in the ground in specifying a minimum version of wxPython as a target, so that people know what they should develop with.
Thoughts?
Martin. KD6YAM _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
I made the change as part of a pull request I submitted yesterday, so no worries. MenuItem.GetLabel() is gone, and replaced, for our purposes, with MenuItem.GetItemLabelText().
Martin. KD6YAM
On Sun, Sep 26, 2021 at 3:27 PM Joseph.P.Scanlan@n7xsd.us wrote:
I’m using wxPython 4.0.7.
What function needs to be changed? I’m still learning wxPython.
On 25 Sep 2021, at 13:25, Joe Pizzi via chirp_devel < chirp_devel@intrepid.danplanet.com> wrote:
wxPython is now on version 4.1.1, so I’d say at least 4.0.
Joe Pizzi
*From:* chirp_devel-bounces@intrepid.danplanet.com < chirp_devel-bounces@intrepid.danplanet.com> *On Behalf Of *Martin Cooper via chirp_devel *Sent:* Saturday, September 25, 2021 11:35 AM *To:* chirp-devel chirp_devel@intrepid.danplanet.com *Subject:* [chirp_devel] Version of wxPython for py3
Bringing up the py3 branch to have a look at where the UI is, one of the first things I tried was File -> New. This immediately died. It seems that the recently added code for maintaining a recently-opened list relies on a function that was present in old versions of wxPython (e.g. 2.8.x) but has been supplanted by a more flexible set of functions in the latest version (i.e. Phoenix).
This raises the question of what the target version of wxPython is intended to be. There is a comment in the recently added developer module related to Phoenix, so I'd assume that it's intended to work under Phoenix. The question is whether that's what we should be working with, or if support for an older version is also required.
The particular issue I encountered is easily fixed for 2.8.6.0 and later, but I think it would be worth putting a stake in the ground in specifying a minimum version of wxPython as a target, so that people know what they should develop with.
Thoughts?
Martin. KD6YAM _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
Thanks. I didn’t find that one.
I did find a deprecated use of Append and submitted a patch to change it to AppendSubMenu.
On 26 Sep 2021, at 15:33, Martin Cooper mfncooper@gmail.com wrote:
I made the change as part of a pull request I submitted yesterday, so no worries. MenuItem.GetLabel() is gone, and replaced, for our purposes, with MenuItem.GetItemLabelText().
Martin. KD6YAM
On Sun, Sep 26, 2021 at 3:27 PM <Joseph.P.Scanlan@n7xsd.us mailto:Joseph.P.Scanlan@n7xsd.us> wrote: I’m using wxPython 4.0.7.
What function needs to be changed? I’m still learning wxPython.
On 25 Sep 2021, at 13:25, Joe Pizzi via chirp_devel <chirp_devel@intrepid.danplanet.com mailto:chirp_devel@intrepid.danplanet.com> wrote:
wxPython is now on version 4.1.1, so I’d say at least 4.0.
Joe Pizzi
From: chirp_devel-bounces@intrepid.danplanet.com mailto:chirp_devel-bounces@intrepid.danplanet.com <chirp_devel-bounces@intrepid.danplanet.com mailto:chirp_devel-bounces@intrepid.danplanet.com> On Behalf Of Martin Cooper via chirp_devel Sent: Saturday, September 25, 2021 11:35 AM To: chirp-devel <chirp_devel@intrepid.danplanet.com mailto:chirp_devel@intrepid.danplanet.com> Subject: [chirp_devel] Version of wxPython for py3
Bringing up the py3 branch to have a look at where the UI is, one of the first things I tried was File -> New. This immediately died. It seems that the recently added code for maintaining a recently-opened list relies on a function that was present in old versions of wxPython (e.g. 2.8.x) but has been supplanted by a more flexible set of functions in the latest version (i.e. Phoenix).
This raises the question of what the target version of wxPython is intended to be. There is a comment in the recently added developer module related to Phoenix, so I'd assume that it's intended to work under Phoenix. The question is whether that's what we should be working with, or if support for an older version is also required.
The particular issue I encountered is easily fixed for 2.8.6.0 and later, but I think it would be worth putting a stake in the ground in specifying a minimum version of wxPython as a target, so that people know what they should develop with.
Thoughts?
Martin. KD6YAM _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com mailto:chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers http://chirp.danplanet.com/projects/chirp/wiki/Developers
Bringing up the py3 branch to have a look at where the UI is, one of the first things I tried was File -> New. This immediately died. It seems that the recently added code for maintaining a recently-opened list relies on a function that was present in old versions of wxPython (e.g. 2.8.x) but has been supplanted by a more flexible set of functions in the latest version (i.e. Phoenix).
This raises the question of what the target version of wxPython is intended to be. There is a comment in the recently added developer module related to Phoenix, so I'd assume that it's intended to work under Phoenix. The question is whether that's what we should be working with, or if support for an older version is also required.
The particular issue I encountered is easily fixed for 2.8.6.0 and later, but I think it would be worth putting a stake in the ground in specifying a minimum version of wxPython as a target, so that people know what they should develop with.
Yeah, I dunno. When I was working with it I was kinda flipping back and forth, as there were several things that weren't working (known broken) in Phoenix, IIRC, and definitely some incorrect documentation which made it hard to determine what was supposed to work.
If Phoenix is what makes sense to target, then we should do that, but at the time it seemed like it might be possible to be reasonably compatible with both with some care.
Anyway, as long as the version we target is available in current distros and isn't too unstable (as Phoenix seemed to be at the time), I'm fine with it.
--Dan
participants (4)
-
Dan Smith -
Joe Pizzi -
Joseph.P.Scanlan＠n7xsd.us -
Martin Cooper