On 8/12/22 11:36 AM, Jon Evans wrote:
The surface area of wxPython on KiCad critical functionality is fairly low. I
would recommend moving forward and seeing what happens.
How long do we have to make this decision/recommendation? It seems easy enough
to spot-check the most popular KiCad plugins that make use of wxPython to see
if there are any obvious problems, if we know that's the goal.
I'm not really sure. Today is actually the scheduled F37 freeze date, but the
schedule [1] says the date is approximate. I can go back and ask when they
absolutely need to know, but I think we have the best chance of influencing the
decision if we can comment in the next day or two. I realize that isn't much
time...
I've tested KiCad 6.0.7 with wxPuthon 4.2.0 on Rawhide, both x86_64 and
aarch64. I've tried opening the python console and I've used the footprint
wizard to create a BGA. What plugins should I test?
Also, if others want to test, they'll need a Rawhide VM. I can provide a link
to the builds of wxPython and KiCad, as well as instructions on how to install.
Steve
[1] https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html
--
You received this message because you are subscribed to the Google Groups "KiCad
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to devlist+unsubscr...@kicad.org.
To view this discussion on the web visit
https://groups.google.com/a/kicad.org/d/msgid/devlist/8c57b812-d219-36bc-6646-08d5c5eee603%40gmail.com.
