Activity for Jérome Laheurte
-
Jérome Laheurte posted a comment on ticket #1723
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
-
I'll take a look. I'm not sure I want to go back to the maintenance nightmare of native packages.
-
Fix german translation
-
Mailer test and py3
-
Settings test
-
Get rid of ExceptionAsUnicode
-
Render
-
Third party tests. Not passing yet.
-
App tests
-
python 3: domain.date
-
python 3: domain.datetime
-
Fix import order
-
Use pytest
-
Remove trailing spaces
-
Use new-style metaclass
-
Use new-style super
-
No need to inherit from object
-
Assume _ is installed as builtin
-
More python3 fixes
-
There's more to that
-
Avoid circular import
-
Remove tests already ported to py3
-
Fix tests
-
Font tests
-
DateTime tests
-
Recurrence tests
-
Scheduler tests
-
Owner test
-
Note container test
-
Categorizable test
-
Category test
-
Note test
-
Category container test
-
Task test
-
Category filter test
-
Domain object owner metaclass test
-
Task status test
-
Sorter test
-
Filter test
-
Task filter test
-
Task list test
-
Task recurrence test
-
Effort test
-
Task relations test
-
Effort list test
-
Effort composite test
-
Effort aggregator test
-
Last domain test
-
Fix Observable for python 3
-
Use new-style super()
-
Composite for python 3
-
Fix test
-
And Command for python 3
-
No need to inherit from object
-
Minor python3 fixes
-
Add AppImage script
-
Merge
-
Set release date
-
Fix syntax in changes.py
-
Remove obsolete distros
-
Merge
-
Fix release date
-
Backport cfd135f888fe
-
Update changelog
-
Update release date
-
I'll see if I can make a release this week-end. The AppImage is more complicated though; I'll have to revamp the download page on the website, change the CI builds, check the various download links...
-
We use the uuid1 function from Python's uuid module.
-
I'm thinking of ditching the various distro-specific packages. They are a pain in the ass to maintain. I recently made an AppImage for another project; I think I'll go this way.
-
Works for me on an up to date Windows 10 family 64 bits. Did you try deleting your taskcoach.ini file ?
-
Expand recurrence frequency and max count dialog entries
-
I’m not familiar with merge requests on SF (this is not a Mercurial feature per se), but I copy/pasted the pull command suggested by SF itself and there wasn’t any incoming revision. Also note the SF description at the top (attached). "0 commits" ?
-
There seems to be a problem: iMac:TaskCoach fraca7$ hg inc ssh://fraca7@hg.code.sf.net/u/abliznyuk/taskcoach comparing with ssh://fraca7@hg.code.sf.net/u/abliznyuk/taskcoach searching for changes no changes found
-
Unfortunately I don't have a Mac with Mojave to test this but it looks like a code signing problem. Can you try to open Task Coach using right click -> Open in the Application folder ?
-
Here, sorry for the delay. Next time feel free to ping us at developers@taskcoach.org
-
Use modern exception syntax
-
Handle long integers properly for all Python versions
-
Automated merge with https://hg.code.sf.net/p/taskcoach/repo
-
Dunno what happens with SF, I didn't get any notification. Looking at this now.
-
Not DBus, "ibus" ? I don't even know what that is :)
-
Interesting. I wonder what chain of events caused this since we don't use dbus (directly)..
-
Fix changelog url
-
Works for me on Linux, but I don't have a Windows system to test that right now
-
Sorry, for some reason I didn't receive a notification. Task Coach does not support Python 3 at the moment.
-
What the hell :) I'll give it a try anyway since I have to install 18.04 for different reasons, but if it's random I'll probably won't be able to reproduce it. On the other hand if it doesn't happen for you anymore all is well
-
Okay I'll try both configurations when I'm done reinstalling my system
-
So that would point to a problem with wxWidgets then, probably. I realized that I actually have Ubuntu 20 installed, not 18, but I must install 18.04 for other reasons so I'll try to reproduce after that
-
Not what I thought then. If the problem persists after you have deleted your .ini file that means it has something to do with your window manager, or maybe a wx update ? It used to work a few weeks ago IIRC ?
-
The warnings from GTK are probably harmless. The traceback on the other hand is something I've seen when key presses are registered in a state where they aren't expected, like when quitting. Could you check Task Coach's CPU usage using "top" in a terminal ? BTW I'm unable to reproduce this on Ubuntu 18.04LTS
-
What version of Python are you using ?
-
J'ai retrouvé la VM Windows avec tout l'environnement de dev installé (rien que ça ça m'aurait pris des jours je pense), donc le temps de trouver comment désactiver la gestion de session et j'aurais une version de test. On croise les doigts.
-
Yep désolé pour le retard, je bosse sur un autre projet très prenant en ce moment. Merci pour l'analyse détaillée. En ce qui concerne VirtualBox je connais bien entendu mais je n'ai pas de license Windows sous la main, c'est pas gratuit ces trucs-là :) La piste d'un problème avec la gestion de session me semble pas mal, d'autant que c'est quelque chose qui a toujours été assez gore à gérer sous Windows. Un test intéressant serait de désactiver carrément cette fonctionnalité pour voir si ça arrange...
-
Tout à fait, donner des explications techniques dans une seconde langue peut être lourd; ça n'était pas un reproche :) Du coup il semblerait que le shutdown ait eu lieu pendant que TaskCoach sauvait un fichier, d'où la présence du .locked je pense; ensuite comme dit l'autre les emmerdes volent en escadrille. Peut-être que la bibliothèque que nous utilisons pour le verrouillage a des problèmes sous Windows 10, il faudra que j'essaye de reproduire ça à l'occasion. Ça va être compliqué vu que je n'ai...
-
D'après vos captures d'écran vous parlez français, on va peut-être la refaire comme ça parce que je ne comprend pas tout de votre description :) D'après la capture d'écran "conflicts detected", le fichier .tsk est sur un répertoire partagé du style dropbox non ?
1 >