pyotherside fails to build with Python 3.9.0a2.

Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.A3Csrv
+ umask 022
+ cd /builddir/build/BUILD
+ cd pyotherside-1.5.8
+ xvfb-run ./tests/tests
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-mockbuild'
********* Start testing of TestPyOtherSide *********
Config: Using QtTest library 5.13.2, Qt 5.13.2 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 9.2.1 20190827 (Red Hat 9.2.1-1))
PASS   : TestPyOtherSide::initTestCase()
PASS   : TestPyOtherSide::testEvaluate()
PASS   : TestPyOtherSide::testQVariantConverter()

=== Received signal at function time: 0ms, total time: 23ms, dumping stack ===
=== End of stack trace ===
QFATAL : TestPyOtherSide::testPyObjectConverter() Received signal 11
         Function time: 0ms Total time: 23ms
FAIL!  : TestPyOtherSide::testPyObjectConverter() Received a fatal error.
   Loc: [Unknown file(0)]
Totals: 3 passed, 1 failed, 0 skipped, 0 blacklisted, 25ms
********* Finished testing of TestPyOtherSide *********
/usr/bin/xvfb-run: line 181:   548 Aborted                 (core dumped) DISPLAY=:$SERVERNUM XAUTHORITY=$AUTHFILE "$@" 2>&1
error: Bad exit status from /var/tmp/rpm-tmp.A3Csrv (%check)


For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.9/fedora-rawhide-x86_64/01148678-pyotherside/

For all our attempts to build pyotherside with Python 3.9, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.9/package/pyotherside/

Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.9:
https://copr.fedorainfracloud.org/coprs/g/python/python3.9/

Let us know here if you have any questions.

Python 3.9 will be included in Fedora 33. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.9.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon.
We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.