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

Remove pry-byebug depedency #857

Merged
merged 1 commit into from
Jan 15, 2022
Merged

Remove pry-byebug depedency #857

merged 1 commit into from
Jan 15, 2022

Conversation

mvz
Copy link
Contributor

@mvz mvz commented Jan 15, 2022

Summary

Remove pry-byebug and byebug.

Details

This removes the hard development dependencies on byebug and pry-byebug. This will allow intalling the latest version of pry. If pry-byebug is needed, it can still be added in Gemfile.local. The pry dependency is set to be lenient enough to allow installing a version compatible with pry-byebug.

Motivation and Context

This keeps dependencies up-to-date. I find I don't use byebug so dropping it from the default set shouldn't be problematic. Once support for Ruby 2.5 has been dropped, the new debug gem can be added as a permanent dependency to provide extended debugging features by default.

How Has This Been Tested?

CI

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Internal change (refactoring, test improvements, developer experience or update of dependencies)

Checklist:

  • I've added tests for my code
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

This will allow intalling the latest version of pry. If pry-byebug is
needed, it can still be added in Gemfile.local.
@mvz mvz merged commit 76d7240 into main Jan 15, 2022
@mvz mvz deleted the remove-pry-byebug-dependency branch January 15, 2022 23:25
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.

1 participant