dhanusharer commented on PR #40768: URL: https://github.com/apache/beam/pull/40768#issuecomment-6504202254
Thank you for the detailed feedback! That approach makes complete sense regarding the blast radius on containers and Python 3.11+ users. I have adjusted this PR to follow **Phase 1** of the proposed rollout: 1. **Restored the Cap:** Kept `setup.py` at `pandas>=2.2.2,<2.4` so the blast radius is zero and existing user environments / containers remain untouched. 2. **Retained Compatibility Hardening:** Kept the backward-compatible defensive reflection in `frame_base.py`, `hasattr()` guards in `frames.py`, and `pd.api.types.is_string_dtype` in `pandas_type_compatibility.py`. 3. **Pandas 2.3 Future Flags CI:** Added `py311-pandas-23future` in `tox.ini` and `build.gradle` running with `PANDAS_MODE__COPY_ON_WRITE=1` and `PANDAS_FUTURE__INFER_STRING=1` to test the Pandas 3 behaviors proactively on 2.3. I've also posted the complete scoping analysis and decision matrix on [#40709](https://github.com/apache/beam/issues/40709). Once this preparation PR lands and Pandas 3.0 pre-releases are verified, raising the cap can follow in a separate PR with a `CHANGES.md` entry. -- 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]
