Python 3.10 Fix jump offsets opcodes

[yeandy]

Fixes #21671

The issue was caused by a deliberate change in behavior in Python 3.10 due to bpo-27129. The offsets were originally byte (8 bits) offsets in Python 3.9, but instruction (16 bits) offsets in Python 3.10. The opcode numbers were halved, so to compensate, I had to double them again when reading it.

A few other tests were failing too. I had to add an opcode due to bpo-43683 in which a new bytecode GEN_START was added.

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Choose reviewer(s) and mention them in a comment (R: @username).
• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

[github-actions]

Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment assign set of reviewers

[codecov]

Codecov Report

Merging #22940 (830aaa3) into master (e880fdb) will increase coverage by 0.01%.
The diff coverage is 80.00%.

@@            Coverage Diff             @@
##           master   #22940      +/-   ##
==========================================
+ Coverage   73.90%   73.91%   +0.01%     
==========================================
  Files         713      714       +1     
  Lines       94464    94671     +207     
==========================================
+ Hits        69809    69975     +166     
- Misses      23358    23399      +41     
  Partials     1297     1297              

Flag	Coverage Δ
python	83.50% <80.00%> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
sdks/python/apache_beam/typehints/opcodes.py	84.64% <50.00%> (-0.25%)	⬇️
.../python/apache_beam/typehints/trivial_inference.py	96.15% <87.50%> (-0.27%)	⬇️
sdks/python/apache_beam/typehints/__init__.py	77.77% <0.00%> (-22.23%)	⬇️
.../python/apache_beam/testing/test_stream_service.py	88.09% <0.00%> (-4.77%)	⬇️
.../python/apache_beam/transforms/periodicsequence.py	98.38% <0.00%> (-1.62%)	⬇️
...che_beam/runners/interactive/interactive_runner.py	90.06% <0.00%> (-1.33%)	⬇️
sdks/python/apache_beam/dataframe/schemas.py	96.62% <0.00%> (-1.05%)	⬇️
sdks/python/apache_beam/transforms/combiners.py	93.05% <0.00%> (-0.39%)	⬇️
sdks/python/apache_beam/typehints/schemas.py	93.84% <0.00%> (-0.31%)	⬇️
...s/python/apache_beam/examples/wordcount_minimal.py	92.59% <0.00%> (-0.27%)	⬇️
... and 14 more

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[yeandy]

R: @robertwb

[github-actions]

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control

[yeandy]

retest this please

[yeandy]

R: @AnandInguva

[tvalentyn]

should we use the 2 multiplier for all minor versions >= 10 ?

[yeandy]

Yes, I'll change it. When I wrote == (3, 10), I was thinking of GEN_START which was added in 3.10, but then removed in 3.11.

[yeandy]

Updated.

[yeandy]

Merged into the 3.10 feature branch #22995

[github-actions]

This pull request has been marked as stale due to 60 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@beam.apache.org list. Thank you for your contributions.