don't use slop in library use

[ytti]

When we do

require 'pry'
pry.binding

We shouldn't need slop. If we do, then the code we're running cannot run different version of slop. Quickly looking at code, it wasn't 100% straight forward to me. Once removed the dependency, I got:

Found plugin pry-byebug, but could not require 'pry-byebug'
Unable to activate byebug-3.5.1, because slop-4.0.0 conflicts with slop (~> 3.6)

Couldn't figure out where the dependencies for slop come to external libraries.

[kyrylo]

Hello, @ytti! Could you please try to test this again? Build Pry from master, please, as we had some changes to that part of code.

[ytti]

I can probably get the hack working. But thinking how to solve this correctly, I see no other solution but to have separate 'pry-lib' and 'pry-cli' packages, both perhaps as dependencies for 'pry' metapackage.

Because even if we fix pry code not to require 'slop' on library run. People who package pry in to their code (like gitlab), will have Gemfile stating 'slop' and some slop version.

Only solution seem to be, that you'd instead depend only on 'pry-lib' in use-cases where actual CLI is not ever going to be needed.

I hope this makes some sense.

[rf-]

Fixed by #1498