-
-
Notifications
You must be signed in to change notification settings - Fork 137
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
Fix ruby 2.7 warning #246
Fix ruby 2.7 warning #246
Conversation
Ruby 2.7 is released, these warnings are annoying. |
Right, I'll try to get a new version out today 👍. |
Probably, we can take out common code with condition… into private method, for example. Or public class method, if it between different classes. Right now there is a duplication of logic. |
CI showed problems for Ruby < 2.6 (missing |
Oh, it's |
My bad too, I should have double-checked before making modifications. |
Don't know what deivid-rodriguez had in mind ... just hoping it helps. AlexWayfer, thanks for your point of view. |
Everything is OK when CI passes. 👌 I just try to improve any code. Thank you for contribution anyway. |
It's looking good to me. Could you rebase and add a changelog entry? |
It'd be nice to add a note about this in |
Done. Hope it's what you were expecting. Thanks for this tool btw. |
Thanks so much @whois-marvin-42! |
Sure @AlexWayfer, can you open a PR? |
Maybe, but it's your requirement, maybe you have others, so, I think, it's better to do you, as Owner (maintainer). For example, I prefer to update Changelog before releases. |
Sure, I'll do it myself. |
When I said, "I'll try to get a new version out today", that was way too optimistic 😅. I'll do it during next week though. |
Any chance for a version bump? |
I'll be releasing 3.8.0 in a bit. One question though, is this warning 2.7.0 specific? Because I can't reproduce it on MRI 2.6. |
Yep. But, probably, in 2.6 too, with warnings flag: #221 From here: https://bugs.ruby-lang.org/issues/4352#note-23
|
Thanks! I'll clarify this in the changelog! |
I'm not sure why, but I see this warning, when I updated to Ruby 2.7.1 using pry-byebug 3.9.0:
|
I'm not sure why. Can you show the full backtrace? |
Sure. What's the simplest way to get the full backtrace for warnings? 🤔 |
Ah, I missed the next line. Looks like it caused by
Do I read this correctly? |
Yeah, |
duh, I believe there is already an issue for this pry/pry-stack_explorer#43 Sorry for the noise here :) |
No problem! |
Fixed warning raised by latest ruby (FILE in eval) in base.rb
Fixes #221.