-
Notifications
You must be signed in to change notification settings - Fork 409
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
Change Pry to Development Dependency #227
Comments
I think this is wrong. Pry is used by the |
We could try to make pry an optional dependency, though. What was the issue you were running into? |
The issue I had was the Version of pry required by the Travis gem prevents upgrading several other gems in my project. If you need to keep it as a runtime dependency could you loosen the version requirement to allow 0.10 and above? On Sat, Sep 6, 2014 at 6:38 AM, Konstantin Haase notifications@github.com
|
We still support 1.8.x at the moment, which is admittedly dubious. This is the reason to keep pry on 0.9.x right now. |
We might want to consider dropping 1.8 support in travis 1.8.x. On Sat, Sep 6, 2014 at 6:44 PM, Hiro Asari notifications@github.com wrote:
|
👍 for dropping 1.8.x support with travis 1.8.0. |
SERIOUS 👍 for dropping 1.8 support. Guys, that version has been deprecated for more than a year. For those who want to use Pry today, this is a handy workaround: |
Good workaround @eherot but +1 on dropping 1.8 like its hot. |
👍 on dropping 1.8 support. |
👍 drop 1.8 |
Please move pry to a development dependency and loosen requirement to allow versions 0.10 and above.
The text was updated successfully, but these errors were encountered: