huoxito has quit [Remote host closed the connection]
ixti has quit [Ping timeout: 264 seconds]
EduardoBautista has joined #bundler
iamjarvo has joined #bundler
iamjarvo has quit [Max SendQ exceeded]
iamjarvo has joined #bundler
Fooster has joined #bundler
huoxito has joined #bundler
Fooster has quit [Ping timeout: 264 seconds]
huoxito has quit [Ping timeout: 244 seconds]
djbkd has joined #bundler
boddhisattva has joined #bundler
<boddhisattva>
Hi all, I'm writing a simple ruby application(basically using PORO's). I've added a Gemfile to it and I'm trying to load pry gem(for debugging purposes) but I'm unable to load that gem using Bundler.setup, things work fine with Bundler.require
<boddhisattva>
Since using Bundler.setup is preferable to Bundler.require as stated for reasons like in this link - http://myronmars.to/n/dev-blog/2012/12/5-reasons-to-avoid-bundler-require, could one give me an idea of what I could be possibly missing when I'm trying to require the pry gem via Bundler.setup.
<Radar>
boddhisattva: what happens when you try to load Pry?
<boddhisattva>
I get the below error -
<boddhisattva>
Failure/Error: expect(total_score(scores)).to eq(16) NoMethodError: undefined method `pry' for #<Binding:0x007fa7f29643e8>
<Radar>
boddhisattva: Bundler.setup just adds the gems to the load path and doesn't require them.
<Radar>
boddhisattva: You will need to require 'pry' after Bundler.setup
<boddhisattva>
A I thought it should pick it up from the gemfile
<Radar>
Nope.
<boddhisattva>
hmm, I see the docs specify using Bundler.require(:default) too
<boddhisattva>
but I guess there isn't a way I can avoid specifying Bundler.require
<Radar>
boddhisattva: Please look at the SO answer. I have provided a way to avoid it.
<boddhisattva>
radar: thanks, I just saw it and I've just posted a question as a comment, can you please look at that ?
<Radar>
done.
<boddhisattva>
Thanks Ryan, just one last question about limiting usage of pry to dev and test env(posted as a comment on the same SO link), I think require 'pry' wouldn't allow me to do that, right /
<boddhisattva>
*right ?
<Radar>
You'd typically remove the require once you're done debugging anything.
<boddhisattva>
Hmm, Thanks for your valuable time Ryan. I have accepted your answer.
<boddhisattva>
the only thing with removing pry is, it has to be added every time one wants to debug, I wish there was a way to do this in the context of this discussion
<boddhisattva>
..without re adding pry, time and again
boddhisattva has quit [Quit: Page closed]
briangonzalez has joined #bundler
briangonzalez has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
simi has quit [Ping timeout: 264 seconds]
huoxito has joined #bundler
iamjarvo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Fooster has joined #bundler
Fooster has quit [Ping timeout: 264 seconds]
huoxito has quit [Remote host closed the connection]
djbkd has quit [Quit: Leaving...]
kangguru_away is now known as kangguru
prime- has quit [Ping timeout: 252 seconds]
prime has joined #bundler
robbyoconnor has quit [Ping timeout: 256 seconds]
robbyoconnor has joined #bundler
Fooster has joined #bundler
Fooster has quit [Ping timeout: 264 seconds]
kangguru is now known as kangguru_away
EduardoBautista has quit [Quit: Connection closed for inactivity]
kangguru_away is now known as kangguru
chouhoulis has joined #bundler
chouhoulis has quit [Remote host closed the connection]