python-anymarkup fails to build with Python 3.9.0a3.

_________________ TestConversionFromJson.test_convert_no_error _________________
self = <test.test_cli_json.TestConversionFromJson object at 0x7f4c114ad0a0>
runner = <click.testing.CliRunner object at 0x7f4c114ad610>
    def test_convert_no_error(self, runner):
        arguments = [
            ['convert'],
            ['convert', '--from-format', 'json'],
            ['convert', '--from-format', 'json', '--to-format', 'ini'],
            ['convert', '--from-format', 'json', '--to-format', 'json'],
            ['convert', '--from-format', 'json', '--to-format', 'json5'],
            ['convert', '--from-format', 'json', '--to-format', 'toml'],
            ['convert', '--from-format', 'json', '--to-format', 'xml'],
            ['convert', '--from-format', 'json', '--to-format', 'yaml']
        ]
        for args in arguments:
            result = runner.invoke(cli, args, input=TEST_DATA_JSON)
>           assert result.exit_code == 0
E           assert 1 == 0
E            +  where 1 = <Result AnyMarkupError()>.exit_code
test/test_cli_json.py:29: AssertionError
=============== 1 failed, 24 passed, 2 warnings in 0.49 seconds ================

Unfortunately, I don't see the actual exception.


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

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

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.