This more or less blocks porting greenwave to python3, since it uses resultsdb directly in its test suite. https://pagure.io/greenwave/issue/166
If you guys don't have cycles for this, let us know. Maybe we can contribute. :)
Any help will be appreciated! We are currently in the process of making all our stuff Python3 compatible, but I had bigger fish to fry so far.
Looks like I can start working on it sometimes next week, but you know how these bold statements usually spawn some weird heisenbugs elsewhere :D
Ohhh, yes. :)
BTW, it turns out greenwave isn't actually blocked on this. The test suite there starts up resultsdb as a subprocess; it can run as py3 while resultsdb stays py2 (until next week!!)
So it happened I had internet connection on the train, and voila! https://pagure.io/taskotron/resultsdb/pull-request/110
That was easier than I expected. Testsuite and basic usage patterns seem to work OK, but I'd be glad for a second set of eyes.
After PR#113 is merged, I think we can close this ticket as resolved.
Metadata Update from @frantisekz: - Issue close_status updated to: Fixed
Login to comment on this ticket.