-
Notifications
You must be signed in to change notification settings - Fork 967
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please ignore. #1318
Please ignore. #1318
Conversation
…TERS macros. The include and the PYBIND11_SMART_HOLDER_TYPE_CASTERS were made obsolete by pybind/pybind11#5257 (merged on Jul 31, 2024).
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Sorry it's stubbornly using my corporate email address for the CLA. I'll close this also. Could you please clone the diff? |
PYBIND11_SMART_HOLDER_TYPE_CASTERS
macros.
Look at this positive success of open-source software at work.. !! The thing broke so very recently, and @tsogoo submitted a fix independently. I'm so grateful for the help, thanks to both of you. However: @rwgk, what I need more than this fix at the moment is the simplest way for OpenSpiel to co-exist internally + externally without having two different states of the code to maintain. So, for that reason I would prefer to pin OpenSpiel's dependency downloader to an old version of the code until the Python team at Google imports the recent changes to pybind11 (i.e. something like #1315). So is it ok with you to keep this PR around until that happens? Meanwhile I'll contact the Python team internally to let them know that this solves it? Wdyt? |
That's what this PR is meant to be. Sorry I didn't explain that here. Copying what I wrote in a chat: First:
Later:
|
My suggestion: Run this CI here with this PR. Apply the same diff internally. If both work as I hope, submit internally and done. |
Oh, cool!! Ok, sorry -- my bad. I've been traveling and only quickly read those messages and misunderstood. Thanks so much! I'll follow the steps you've suggested. |
Ok, can you make the same change as to |
Please refer to #1321