--WIyZ46R2i8wDzkSu
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 31, 2010 at 03:13:32PM +0900, NARUSE, Yui wrote:
> 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.
>=20
> I noticed this is from API incompatibility:
> YAML.dump( obj, io =3D nil )
> Psych.dump o, options =3D {}
>=20
> def YAML.dump( obj, io =3D nil )
>   obj.to_yaml( io || io2 =3D StringIO.new )
>=20
> def psych_to_yaml options =3D {}
>   Psych.dump self, options
>=20
> def self.dump o, options =3D {}
>   visitor =3D Psych::Visitors::YAMLTree.new options
>=20
> So if Psych.dump can treat io like dump(o, io, options =3D{}),
> it can be fixed fundamentally.
> Is this acceptable solution?

This is a bit of work.  I'm fixing it now.  :-)

--=20
Aaron Patterson
http://tenderlovemaking.com/

--WIyZ46R2i8wDzkSu
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)

iQEcBAEBAgAGBQJLs7ZEAAoJEJUxcLy0/6/GgaUH/0rJ6Q6xdCy/1fXcznuC+/8w
ToypZlC9/VkPfENAyLpevYJQ3BOnDw4UyoDJAVKntKPeB9Jliju+PvrihsXUlZLu
/F+2ggLDA8jZXXjhC4tGrIgDi6mXBSlvq09yWsvl6p0xxGKddxlmfttG0PxMw8mj
PTA7GB8N/EBWkCW/7f2FvY2SHPYNg1v1ksfvus3cl1jtJ6YwsMUE0EkpROdzPwJS
R7m7y/yWj8BkaFujL7l9ggwa/YkoCaK/TgLwm+T7Ra46JtaadeHyXOcIAPRIuX3A
4QuPVyCDmf3PEJEeZMmk0flKK1UFa1ymiKTaJlwzW3ucLf2Ukl4j0KGD6QF/fo4=
=p4Jv
-----END PGP SIGNATURE-----

--WIyZ46R2i8wDzkSu--

On Wed, Mar 31, 2010 at 03:13:32PM +0900, NARUSE, Yui wrote:
> 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.
>=20
> I noticed this is from API incompatibility:
> YAML.dump( obj, io =3D nil )
> Psych.dump o, options =3D {}
>=20
> def YAML.dump( obj, io =3D nil )
>   obj.to_yaml( io || io2 =3D StringIO.new )
>=20
> def psych_to_yaml options =3D {}
>   Psych.dump self, options
>=20
> def self.dump o, options =3D {}
>   visitor =3D Psych::Visitors::YAMLTree.new options
>=20
> So if Psych.dump can treat io like dump(o, io, options =3D{}),
> it can be fixed fundamentally.
> Is this acceptable solution?

This is a bit of work.  I'm fixing it now.  :-)

--=20
Aaron Patterson
http://tenderlovemaking.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)

iQEcBAEBAgAGBQJLs7ZEAAoJEJUxcLy0/6/GgaUH/0rJ6Q6xdCy/1fXcznuC+/8w
ToypZlC9/VkPfENAyLpevYJQ3BOnDw4UyoDJAVKntKPeB9Jliju+PvrihsXUlZLu
/F+2ggLDA8jZXXjhC4tGrIgDi6mXBSlvq09yWsvl6p0xxGKddxlmfttG0PxMw8mj
PTA7GB8N/EBWkCW/7f2FvY2SHPYNg1v1ksfvus3cl1jtJ6YwsMUE0EkpROdzPwJS
R7m7y/yWj8BkaFujL7l9ggwa/YkoCaK/TgLwm+T7Ra46JtaadeHyXOcIAPRIuX3A
4QuPVyCDmf3PEJEeZMmk0flKK1UFa1ymiKTaJlwzW3ucLf2Ukl4j0KGD6QF/fo4=
=p4Jv
-----END PGP SIGNATURE-----