Closed baldurmen closed 1 year ago
spl0k
commented
1 year ago Hello.
I was watching Pony for any news on Python 3.11, also getting worried about the lack of update. Even before the conflict started I was considering replacing Pony with something else as development seemed to slow down over the years, Pony requiring more time to be compatible for each new Python version. I guess this replacement is becoming a necessity now...
baldurmen
commented
1 year ago So we agree... I certainly don't want to pressure you, but I thought you should know that:
This pretty much means if ponyorm doesn't magically become Python 3.11 compatible and supysonic still depends on it, it won't be in the next Debian stable version :(
This whole situation makes me very sad, as supysonic is one of the packages I really care about in Debian, but there is little I can do on my side. One of my Debian colleagues has been looking at pony to see how it can be patched, but although he's a Python wizard, I don't think we can rely on him...
spl0k
commented
1 year ago Thank you for the information.
I started replacing pony with peewee which is already available in Debian packages and, if I understand correctly, is already safe for the next Debian stable. It's a few versions behind though so I'll aim for a compatibility with the 3.14.10 version. It's far from done but you can follow the progress on the peewee branch. Hopefully I'll get it ready before the freeze.
baldurmen
commented
1 year ago That's great news!
Peewee does seem to be in a good shape in Debian, yes.
If you need me to run tests, I'd be more than happy to.
baldurmen
commented
1 year ago Well well well, sometime heroes come through! My Debian colleagues worked hard and managed to patch Pony for 3.11.
The pony testsuite passes and with this patch, so does the supysonic one. I guess the move to peewee is less time critical then :)
I'm sure they'll make a proper PR on the pony git repo soon.
Cheers,
spl0k
commented
1 year ago Hello, happy New Year!
That's some impressive work, and it seems the PR triggered a bit of activity on pony's repo.
Meanwhile I progressed on replacing pony with peewee: all tests now pass. I still need to check some stuff as we don't have a 100% test coverage and some tests just call the code and aren't actually checking anything (especially the tests for the API endpoints provided by the supysonic.api.album_songs module)
spl0k
commented
1 year ago After using it a bit I didn't notice anything problematic, so I it got merged into master and I published a new version (0.7.3). Say hello to Supysonic now rid of Pony!
spl0k
commented
1 year ago Well, it seems a major issue eluded me: #241 :(
spl0k
commented
1 year ago Published a new version (0.7.4). It should now be stable.
Hello!
Debian is currently busy migrating to Python 3.11 and I'm getting some testsuite failures. Everything but the failure on
test_unstarspawns from pony not supporting 3.11.Somewhat unrelated, but there has been no commit to the pony source code since May 2022 and I fear it's a casualty of the current Russia-Ukraine war... Anyway, the current situation is worrisome.
I'm attaching the full tracelog, as apparently, Github has decided I can't post more than 65536 characters in an issue (what nonsense).
supysonic_failure_3.11.txt