Yeah Moksha seems to work ok with it. I need to closely examine the stderrs it throws with the new efl but the user never sees them and unless something serious is going on they don't break anything. In the past some of them I can't do anything about anyway as they are an "EFL issue" in my mind. If I change nothing in Moksha and a latter efl version makes a error message moksha used to throw go away then I definitely consider it an EFL issue. Only twice since I have using e17 or moksha have these ran error free with the version of efl in our repos. Once was with e17 and once was with moksha only after I undertook an ambitious project to 'fix' them all. Sadly the next efl update introduced more. In time tho I do examine them all closely and try to determine for each one I note whether if:
- It something I can't fix (as it is something going on in efl and not Moksha)
- It is something I can fix and caused by our theme. I tell Štefan about it, lol.
- It is something I can fix with some usually minor change(s) to moksha
- It is serious and can cause bug issues regardless whether I know how to fix it or what is causing it. (These I prioritize!)
- It is insignificant and can cause no issues. I may or may not know what causes it or how to fix it at first glance or even after examining it. These are low priority and I may or may not try to fix them.
As to the python-efl added to the testing repo I briefly tested about a dozen or so of the python-efl examples and they all worked. Going to get around to testing the usual py-efl apps bodhi has in our repos and few more I know about to ensure they work fine. I anticipate no problems tho, I just prefer to BE SURE.
