Re: audio/solfege: update and move to python3/gtk3

2020-11-08 Thread Brian Callahan
On Sunday, November 8, 2020 9:51 AM, Jeremie Courreges-Anglas wrote: > cc'ing bcallah@, spotted in cvs log, and ajacoutot@ because py-gtk2 > > The current solfege port seems unstable (lots of errors at runtime). > This update seems to work more reliably in my limited testing. > Moving to

Re: audio/solfege: update and move to python3/gtk3

2020-11-08 Thread Antoine Jacoutot
On Sun, Nov 08, 2020 at 03:51:14PM +0100, Jeremie Courreges-Anglas wrote: > > cc'ing bcallah@, spotted in cvs log, and ajacoutot@ because py-gtk2 > > The current solfege port seems unstable (lots of errors at runtime). > This update seems to work more reliably in my limited testing. > Moving to

audio/solfege: update and move to python3/gtk3

2020-11-08 Thread Jeremie Courreges-Anglas
cc'ing bcallah@, spotted in cvs log, and ajacoutot@ because py-gtk2 The current solfege port seems unstable (lots of errors at runtime). This update seems to work more reliably in my limited testing. Moving to python3 and gtk3 instead of py-gtk2 is the reason why I took a look. Neither