feat(deps): add support for Python 3.13 and later

[terop]

Python 3.13 has been released last week so add support for it so that early adopters can use it.

[terop]

@TheKevJames could you kindly check this PR?

[meherett]

Any update?

[EvanBldy]

Hi, any update on this ? when do you plan to do a release with this ?

[keyfayaz]

Any update?

[whimboo]

@terop do you know why the circleci jobs are all failing? I'm not able to see the test logs given that it requires a login. :/

[terop]

@terop do you know why the circleci jobs are all failing? I'm not able to see the test logs given that it requires a login. :/

Kind of, the error can be seen below. I am not familiar with the CI setup of this project so I cannot say how this should be fixed.

upload: commands[0]> coveralls --verbose
Missing .coveralls.yml file. Using only env variables.
Error running coveralls: Not on TravisCI. You have to provide either repo_token in .coveralls.yml or set the COVERALLS_REPO_TOKEN env var.
Traceback (most recent call last):
  File "/root/project/coveralls/cli.py", line 65, in main
    coverallz = Coveralls(
                ^^^^^^^^^^
  File "/root/project/coveralls/api.py", line 47, in __init__
    self.ensure_token()
  File "/root/project/coveralls/api.py", line 60, in ensure_token
    raise CoverallsException(
coveralls.exception.CoverallsException: Not on TravisCI. You have to provide either repo_token in .coveralls.yml or set the COVERALLS_REPO_TOKEN env var.
upload: exit 1 (0.24 seconds) /root/project> coveralls --verbose pid=2158
.pkg: _exit> python /usr/local/lib/python3.11/site-packages/pyproject_api/_backend.py True poetry.core.masonry.api
  upload: FAIL code 1 (4.84=setup[4.59]+cmd[0.24] seconds)
  evaluation failed :( (5.11 seconds)

Exited with code exit status 1

[bartvanandel]

@TheKevJames Would you please take a look at this? This PR is effectively blocking downstream packages from updating, see e.g. linked PRs above.

[arcivanov]

What's the estimate on this? Python 3.14 is going to be released soon and 3.13 is still not supported.

[andy-maier]

@TheKevJames Any chance you can take a look at this PR? The current situation forces everyone (i.e. the world) to stay on the 3.3.1 version of coveralls when using Python 3.13, and that version pins coverage to <7.0. This is really not a good situation.

[TheKevJames]

Solved and released as v4.0.2, thanks for all the comments and commits everyone!

[webknjaz]

@TheKevJames did you forget to mark the tag as a GitHub Release, then?

[TheKevJames]

Oops, forgot to click this button. Thanks for calling it out! Should all be correct now: