Skip to content

Suppress "string returned by #{symbol} will be frozen in the future" warnings #194

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

kou
Copy link
Member

@kou kou commented Apr 8, 2025

For example:

https://github.com/red-data-tools/charty/actions/runs/14327259034/job/40155029515#step:12:1596

pycall-1.5.2/lib/pycall/pyobject_wrapper.rb:37: warning: string returned by :index=.to_s will be frozen in the future

This warnings is started from Ruby 3.4.

@kou
Copy link
Member Author

kou commented Apr 8, 2025

@mrkn Should we fix CI failures before this?

@mrkn
Copy link
Member

mrkn commented Apr 8, 2025

@kou

Should we fix CI failures before this?

The answer is yes if we can.

The CI failures are corresponding to the spec change of begin-less ranges in Ruby 3.4.
As I wrote in the comment in #191, we need to decide how to emulate Python's slice(None, None, -1) in Ruby >= 3.4.

Do you have any idea?

@mrkn
Copy link
Member

mrkn commented Apr 9, 2025

@kou I'm trying to fix CI in #191. Wait a moment.

@kou
Copy link
Member Author

kou commented Apr 9, 2025

Ah, I understand.

I'll add a comment to #191.

…warnings

For example:

https://github.com/red-data-tools/charty/actions/runs/14327259034/job/40155029515#step:12:1596

    pycall-1.5.2/lib/pycall/pyobject_wrapper.rb:37: warning: string returned by :index=.to_s will be frozen in the future

This warnings is started from Ruby 3.4.
@kou kou force-pushed the suppress-frozen-warning branch from f74e96b to 296fdd3 Compare May 7, 2025 00:50
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.

2 participants