On Jun 7, 3:56 pm, Nate Wiger <nwi...@gmail.com> wrote: > > True, but such a change should be made to all specs at the same time. > > I don't currently test on 1.9.2, but I will after it is officially > > released. If you want to submit a patch now to modify all of the > > specs to use expand_path instead of join, that's fine if it is really > > necessary on 1.9.2. It should only be necessary if __FILE__ is not > > already an absolute path, though. Is __FILE__ not an absolute path on > > 1.9.2? > > Agree about changing all specs at the same time - I actually meant to > remove that but forgot. Just thought I'd mention it. > > The Ruby 1.9.2 change is dumb, but from what I gather, Matz is not > budging:http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/24155
Just thought I should give a heads up that with the patches committed today, Sequel should now be 1.9.2 compatible, and the specs should just pass and be warning free on 1.9.2pre3. Also, tangentially related is that I have tested Sequel on Rubinius 1.0.1 and other than two failing specs due to a bug in Rubinius's block splat handling (which they are aware of), it should work fine there. I've added 1.9.2 to one of the standard test suites, though I haven't tested all adapters with it. I haven't added Rubinius to one of the standard test suites, but I probably will when a version is released with the block splat bug fixed. Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to sequel-t...@googlegroups.com. To unsubscribe from this group, send email to sequel-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
