bluebell wrote:And we learn again "Don't follow the hipsters". New languages and frameworks come and go. If they don't vanish then new "hip" features make newer versions incompatible to older versions. Hipsters give a shit if users of their stuff have to maintain their projects. Change, change, change ist their game.
Guitarix is really cool. It would be such a pity if the Python hipsters would kill it by simply doing nothing.
I must admit that it's lately my own foul. Guitarix use waf to build, and the version it use is now over 10 years old. We've made a couple of modifications to the waflib to cover our needs, and that is the reason why I always was to lazy to update to a newer waf version, as I need to modify it as well. Other than that, the waf developers provided a very smooth way to update and keep track with the latest python developments, but I fail, and now it's to late.
As well I must admit that I know about this issue more than a Year now, but hey, what should I say, I fail.
tseaver wrote:I have a ton of experience porting Python2 to Python2-3 compatible code, and could help with that problem. Is SourceForge still the canonical VCS, or has Guitarix moved to Github?
Yes, it's still on SourceForge. Any help/patches would be welcome.
For notice, it's planned to move the build system to meson, which is based on python as well. That means, all waf-scripts needs to be ported to meson.
If you've some experience with meson as well, it would be very welcome. Currently no work is done in that direction.
On the road again.