Revert "Update cython requirement from <1 to <4 in /sdks/python (#320…

[damccorm]

…87)"

This reverts commit 502c728.

This probably shouldn't have been done without some conversation on the mailing list (see #32034 and

beam/sdks/python/container/base_image_requirements_manual.txt

Line 28 in 502c728

# Don't upgrade to Cython 3.x, until it's released, stable and we have consensus

) - I'm not sure why this got reopened FWIW

---

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

• 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 or the workflows README to see a list of phrases to trigger workflows.

[damccorm]

R: @jrmccluskey

[github-actions]

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control. If you'd like to restart, comment assign set of reviewers

[jrmccluskey]

oops, this just got thrown in with a shuffle of dependency upgrade PRs that I got this week. SGTM

[damccorm]

No problem, I just happened to notice it. I think we want to do this anyways (and hope to send something out to the dev list in the next weekish), but it is not obvious to me whether we can do it blindly or not (@robertwb probably has a better idea)