jrmccluskey commented on issue #40709: URL: https://github.com/apache/beam/issues/40709#issuecomment-6609893051
Partitioning the dependency based on Python 3.10 is a no-op since Beam Python has already dropped 3.10 support. You have some options based on the approach here, but since this blocks 3.15 support in the Python SDK you're better off not partitioning at all. Post-3.15 support we can make the decision to allow 3.11-3.14 to use pandas 3+ or not. Separately, phase 2 is not particularly well-planned. Why run against 3.0 pre-releases instead of the full 3.0+ releases we're looking to support? Doing that in CI is also something you'll need a Beam committer to help with, since they'll need to open a branch on the main repo to configure those changes and run modified workflows. I would also be interested in if there are any new features in pandas 3+ that would be worth surfacing via the dataframes API. This has been largely focused on making everything that already exists within the SDK work, but we should consider benefits to pandas 3+ as well. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
