Future of (development) dependency for byebug?

[mtasaka]

Currently for power_assert testsuite, it depends on byebug: https://github.com/ruby/power_assert/blob/297fa68908c45c4ca6c41e0940ebcc069744d580/power_assert.gemspec#L26 https://github.com/ruby/power_assert/blob/297fa68908c45c4ca6c41e0940ebcc069744d580/test/trace_test.rb#L10

So can I rely on byebug?

Why I am asking here is that

• The last activity on https://github.com/deivid-rodriguez/byebug seems more than 2 years ago.
• And it seems that with ruby 3.3 (I tested https://github.com/ruby/ruby/commit/cd67c0d2040f1ade0fe8b1533816281553bfe6e6 ) byebug testsuite fails , and looks like byebug does not work with ruby 3.3 properly.

So I think if power_assert is going to use byebug, someone has to support byebug maintainership. Or can power_assert be switched to use debug gem?

[voxik]

@deivid-rodriguez FYI

[k-tsj]

PowerAssert.trace depends on byebug, but I think this method is only used by my PoC gem pry-byebug-power_assert.

So I'll remove this feature. (At least for now. I might implement the same feature using debug.gem)