Skip to content
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

Depend on ruby/debug, replacing Byebug #43187

Merged
merged 1 commit into from
Sep 8, 2021
Merged

Depend on ruby/debug, replacing Byebug #43187

merged 1 commit into from
Sep 8, 2021

Conversation

fxn
Copy link
Member

@fxn fxn commented Sep 8, 2021

What

This patch generates a dependency on debug in the Gemfile of new applications, replacing byebug.

Why

  1. debug is planned to ship with Ruby 3.1. With this change we align Rails with Ruby.
  2. Byebug and Zeitwerk are not fully compatible. Mind you, that is not a bug of either gem, it is a technical limitation. See Incompatibility with Zeitwerk deivid-rodriguez/byebug#564 for details.

Caveat

While debug has not been heavily tested with rails/main, and it is right now in 1.0.0 RC2, casual usage suggests we can attempt the switch.

Praise

Byebug has been helping Rails programmers debug their applications for more than 7 years. ❤️

@fxn fxn force-pushed the debug branch 2 times, most recently from 4373f55 to 6f56f9a Compare September 8, 2021 15:33
ruby/debug is a new debugger that is going to ship with CRuby.

It makes sense for Rails to switch to this one because that is
where the language is heading, and because Byebug is not fully
compatible with Zeitwerk. See

    deivid-rodriguez/byebug#564

While ruby/debug has not been heavily tested with Zeitwerk,
casual usage seems to suggest it works without issues, including
explicit namespaces, which is where Byebug and Zeitwerk conflict.

Byebug is terrific, thanks a lot for all these years. ❤️
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants