Pry queries rubygems for all pry plugin gems based on name alone. This causes pry to require gems that conflict with the current pry version.
Example:
I have a bundler managed app with the following gems:
- pry 0.9.12
- pry-byebug 1.2.1
I also have pry 0.10.1 installed. Using pry outside of the bundled app results in the following error:
Unable to activate pry-byebug-1.2.1, because pry-0.10.1 conflicts with pry (~> 0.9.12) (Gem::LoadError)
It should be possible to skip plugins which don't support the current pry.
Pry queries rubygems for all pry plugin gems based on name alone. This causes pry to require gems that conflict with the current pry version.
Example:
I have a bundler managed app with the following gems:
I also have pry 0.10.1 installed. Using pry outside of the bundled app results in the following error:
It should be possible to skip plugins which don't support the current pry.