As now python3 support added in weboob 1.4 would it be possible to port kmymoney buildsytem also to python3, please?
Linux/KDE Plasma: Mageia Cauldron
(available in About System)
KDE Plasma Version: 5.12.2
KDE Frameworks Version: 5.55.0
Qt Version: 5.12.1
"weboob"? Umm, is this a joke?
No, it is not a joke. Did you even bother to search the term, or check the KMM cmake options?
Any news about this bug? after about 5 month
As another project I follow says "Patches gratefully accepted."
There are unfortunately, not enough developer hours available to do much more than fix bugs and very slowly work on additional features, and those are most likely to be those features of interest to the person doing the work.
Don't worry that the status is REPORTED and not CONFIRMED, as this (small) team doesn't use those values in any particular way. Bugs often go straight from REPORTED to RESOLVED.
The initial weboob support discussion by Łukasz Wojniłowicz specifically addresses his requirement for Python 2.7 as opposed to 3.6:
I suppose this is essentially a (reversed) guideline on how to proceed here.
Hmmm - that Phabricator diff seemed to be specifically for adding Python 2.x to Craft - the build system for KDE on Windows, so I can't tell how useful it will be for porting the plugin to python 3.
Also, just for the record, there are three python scripts within the KMM git tree
and I suppose someone who knows more about Python than I do (near zero) should check that they are compaptible with Python 3.6 or 3.7.
While I know eventually Python 2 will be going EOL, it seems like it's not going to disappear from the environment any time soon, so while this will certainly need to be done eventually, it's not clear how urgent it is.
Rather urgent, not so much for kmymoney's python dependency on the interpreter, but weboob which has many python library dependencies, and these upstreams are rapidly dropping python2 support now.
weboob upstream says that 1.5 can be used with python3 already, albeit it would be better with 1.6.
Does kmymoney depend on weboob's full feature set including configuring with "--qt"? Being able to drop the resulting dependency on dev-python/google-api-python-client would be some relieve at least.