Skip to content

Conversation

@scv119
Copy link
Contributor

@scv119 scv119 commented May 20, 2022

Why are these changes needed?

in python3.10, it fixed a bug that a interactively defined class was tagged with a wrong type during inspection; which now throws OSError. detailed pr python/cpython#27171

we need to handle this case properly in otherwise ray actor definition will throw in interactive mode. please refer to #25026 for repo.

Related issue number

closes #25026

Checks

@scv119 scv119 marked this pull request as ready for review May 20, 2022 16:32
Copy link
Member

@mwtian mwtian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe add comment for the issue as well?

@scv119 scv119 merged commit 8960afa into ray-project:master May 20, 2022
scv119 added a commit to scv119/ray that referenced this pull request May 20, 2022
…ct#25032

in python3.10, it fixed a bug that a interactively defined class was tagged with a wrong type during inspection; which now throws OSError. detailed pr python/cpython#27171

we need to handle this case properly in otherwise ray actor definition will throw in interactive mode. please refer to ray-project#25026 for repo.
scv119 added a commit that referenced this pull request May 21, 2022
…25042)

in python3.10, it fixed a bug that a interactively defined class was tagged with a wrong type during inspection; which now throws OSError. detailed pr python/cpython#27171

we need to handle this case properly in otherwise ray actor definition will throw in interactive mode. please refer to #25026 for repo.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Core | Python 3.10] Actor cannot be created when Ray is used within ipython

4 participants