Jérome Laheurte

In the meantime you can just do what the current tests are doing, i.e. instantiate Translator at module level in your top-level test script

The very first instantiation of Translator must specify the language, and subsequent ones can just omit it (see the Singleton metaclass in taskcoachlib/patterns). In the base repo this is done at class level in wxTestCase (in tests/test.py) for unit tests.

Nope, sorry. I'm not active any more and this would not be a piece of cake (I think the wx version Task Coach works with will not be supported on M1 anyway)

It is; second "Code" tab in the SF interface. I know this is confusing :( https://sourceforge.net/p/taskcoach/repo/ci/default/tree/

The main effort is on Py3. Doing PyQt concurrently would be a nightmare since I couldn't even test anything before I'm completely finished, so I'm doing py3+wx4, and then Qt5 (or 6, depends when). Everything is in the hg repo. And it's moving very slowly.

The iOS version has never been full-featured and is discontinued anyway. I don't even think it supports 64bits.

I would need an M1 mac for that, and that's not going to happen before some time, I just replaced my iMac in 2019. Not event sure our dependencies would work anyway.

Qt is a well-designed OO framework. wx is a heap of special cases that breaks apart every time you want to do something not "mainstream". For the sake of my mental health I don't want to maintain wx code any more... Anyway since doing both at the same time would be too difficult, the current effort is on Python3 + wx4, then we'll see