2010/3/31 NARUSE, Yui <naruse / airemix.jp>:
> Hi,
>
> 2010/3/31 Aaron Patterson <aaron / tenderlovemaking.com>:
>> On Tue, Mar 30, 2010 at 07:13:32PM +0900, NARUSE, Yui wrote:
>>> (2010/03/30 17:55), Tanaka Akira wrote:
>>> I patched rubygems and got following backtrace.
>>> This is not happen when only Rubygems tests run.
>>> On test-all, Psych effects rubygems tests.
>>
>> I believe this is because both YAML and Psych add Object#to_yaml.
>>
>> I am working with Eric to convert Rubygems to take advantage of Psych.
>> That should clear up the problem.
>
> I applied workaround patch in r27125.

I noticed this is from API incompatibility:
YAML.dump( obj, io = nil )
Psych.dump o, options = {}

def YAML.dump( obj, io = nil )
  obj.to_yaml( io || io2 = StringIO.new )

def psych_to_yaml options = {}
  Psych.dump self, options

def self.dump o, options = {}
  visitor = Psych::Visitors::YAMLTree.new options

So if Psych.dump can treat io like dump(o, io, options ={}),
it can be fixed fundamentally.
Is this acceptable solution?

-- 
NARUSE, Yui
naruse / airemix.jp