Run tests in Python 3.13

[antonpirker]

Description

In this PR we run the tests suite against Python 3.13 to see if this works.

I know this is not something we can merge yet, because we probably have to wait until the final Python 3.13 is released. But this PR should be a starting point to see what still needs to be done to make opentelementry-python compatible with Python 3.13.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

I ran all the test suites using tox against Python 3.13 locally. One is still failing:

  py313-test-opentelemetry-api: commands succeeded
  py313-test-opentelemetry-proto-0: commands succeeded
  py313-test-opentelemetry-proto-1: commands succeeded
  py313-test-opentelemetry-sdk: commands succeeded
  py313-test-opentelemetry-semantic-conventions: commands succeeded
ERROR:   py313-test-opentelemetry-getting-started: parallel child exit code 1
  py313-test-opentelemetry-opentracing-shim: commands succeeded
  py313-test-opentelemetry-opencensus-shim: commands succeeded
  py313-test-opentelemetry-exporter-opencensus: commands succeeded
  py313-test-opentelemetry-exporter-otlp-proto-common-0: commands succeeded
  py313-test-opentelemetry-exporter-otlp-proto-common-1: commands succeeded
  py313-test-opentelemetry-exporter-otlp-combined: commands succeeded
  py313-test-opentelemetry-exporter-otlp-proto-grpc-0: commands succeeded
  py313-test-opentelemetry-exporter-otlp-proto-grpc-1: commands succeeded
  py313-test-opentelemetry-exporter-otlp-proto-http-0: commands succeeded
  py313-test-opentelemetry-exporter-otlp-proto-http-1: commands succeeded
  py313-test-opentelemetry-exporter-prometheus: commands succeeded
  py313-test-opentelemetry-exporter-zipkin-combined: commands succeeded
  py313-test-opentelemetry-exporter-zipkin-proto-http: commands succeeded
  py313-test-opentelemetry-exporter-zipkin-json: commands succeeded
  py313-test-opentelemetry-propagator-b3: commands succeeded
  py313-test-opentelemetry-propagator-jaeger: commands succeeded
  py313-test-opentelemetry-test-utils: commands succeeded

But I guess this is because I need to set CONTRIB_REPO_SHA to a commit in the contrib repo that has the Python 3.13 changes in it (which is not possible, because I forked the contrib repo)

Does This PR Require a Contrib Repo Change?

• Yes. - Link to PR: Add support for Python 3.13 opentelemetry-python-contrib#2724
• No.

Checklist:

• Followed the style guidelines of this project
• Changelogs have been updated
• Unit tests have been added
• Documentation has been updated

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: antonpirker / name: Anton Pirker (2e08a91, 20dc2b0, 6eb32ae, 2bf39f3, d10e0c8, 5138447, ee71a5c, 12ef0b7, c4d5b6c)
• ✅ login: xrmx / name: Riccardo Magliocchetti (7adfb2a)

[antonpirker]

Currently the show blocker is, that grpcio does not yet support Python 3.13. But will do so by the end of September 2024, see this comment: grpc/grpc#34922 (comment)

[alexmojaki]

Seems like grpc support for 3.13 has been released: grpc/grpc#34922 (comment)

[emdneto]

Seems like grpc support for 3.13 has been released: grpc/grpc#34922 (comment)

@antonpirker is there any other blocker for this PR to make it ready for review?