Failures with Ruby 2.0.0 #193
Comments
|
in ruby 2.0 proc = Proc.new { x = 1 }
proc == proc.clone #=> false
proc.eql? proc.clone #=> falseTo countinue testing this might need to look into something like |
|
As for the other bug it's a bit odd. httparty is dynamicly creating methods to access responce codes by name, For example: response = HTTParty::Response(...)
::Net::HTTPResponse::CODE_TO_OBJ['100'] #=> Net::HTTPContinue
response.continue? #=> Not an exceptionNow for the interesting part. ruby 1.9.3 irb(main):008:0> ::Net::HTTPResponse::CODE_TO_OBJ["300"]
=> Net::HTTPMultipleChoiceruby 2.0.0 irb(main):002:0> ::Net::HTTPResponse::CODE_TO_OBJ["300"]
=> Net::HTTPMultipleChoicesThey did do a little to help backwards compatibility. ruby 2.0.0 irb(main):015:0> ::Net::HTTPMultipleChoices
=> Net::HTTPMultipleChoices
irb(main):016:0> ::Net::HTTPMultipleChoice
=> Net::HTTPMultipleChoices
irb(main):017:0> Too bad it's for the pluralized name 😦 |
|
This can be closed now thanks to 1fde99b |
|
jruby compat.version=2.0 irb(main):002:0> ::Net::HTTPResponse::CODE_TO_OBJ["300"]
=> Net::HTTPMultipleChoiceGrrrrrr 😦 |
Hi,
I'm observing these failures with Ruby 2.0.0:
Any idea what's going on in there?
Thanks.
The text was updated successfully, but these errors were encountered: