…ready extended it with its own module. These modules duplicate the same behavior and stomp on each other's toes.
…rying to read a body from it.
…ck doesn't change everytime we run something on JRuby.
…o the previous release.
…sed on the gem skeleton that bundler generates.
… that a warning is printed for a version with a greater major or minor version number. This simulates the ~> gem comparison operator, and is inspired by wycats' recent blog post: http://yehudakatz.com/2010/08/21/using-considered-harmful-or-whats-wrong-with/
They should never be instantiated and don't really hold state. A module is more appropriate here.
…ocalhost feature. This is simpler than changing allow_net_connect from false to true and back again in our Net::HTTP extension for a localhost request.
…to create the request uri.
… example groups on 1.8.6.
…avoid an rspec bug that manifests on 1.9.1. See these links for more info: - http://github.com/rspec/rspec-core/issues#issue/41/comment/365562 - http://gist.github.com/543381
… original method rather than super. This works around an error I'm getting on 1.9.2: "super from singleton method that is defined to multiple classes is not supported; this will be fixed in 1.9.3 or later"
On 1.9.2, I'm getting errors like these: dyld: lazy symbol binding failed: Symbol not found: _rb_method_node Referenced from: /Users/mmarston/.rvm/gems/ruby-1.9.2-p0/gems/ruby-debug-base19-0.11.23/lib/ruby_debug.bundle Expected in: flat namespace dyld: Symbol not found: _rb_method_node Referenced from: /Users/mmarston/.rvm/gems/ruby-1.9.2-p0/gems/ruby-debug-base19-0.11.23/lib/ruby_debug.bundle Expected in: flat namespace
On 1.9.2, Set.new([1, 2]).hash != Set.new([2, 1]).hash, but Set.new([1, 2]).hash == Set.new([1, 2]).hash.