Hooray — Ruby 1.9.3 is out.
So inquiring minds (at least my inquiring mind) wanted to know — does it really help with the rake issues related to the ruby require code?
$ rvm get head$ rvm install 1.9.3$ rvm use 1.9.3@exrails31 --create$ gem install bundler$ cd project; bundle install
Results of a time rails console with immediate exit with a patched 1.9.2 (it’s a little slower than my previous post due to additional gems we’ve put in our project):
rubydev:learn (ruby-1.9.2@exrails31)$ time rails consoleexitLoading development environment (Rails 3.1.1)>> exit real 0m13.684suser 0m12.257ssys 0m1.452s
In Ruby 1.9.3:
rubydev:learn (ruby-1.9.3@exrails31)$ time rails consoleexit/Users/jayoung/.rvm/gems/ruby-1.9.3-p0@exrails31/gems/activesupport-3.1.1/lib/active_support/dependencies.rb:240:in `block in require': iconv will be deprecated in the future, use String#encode instead.Loading development environment (Rails 3.1.1)>> exit real 0m10.803suser 0m10.020ssys 0m0.777s
I’m personally still trying to get my app started — going to have to install my own rails_config for a few days until a new gem is released, so I’m not all sure what else might be a problem in 1.9.3 yet. But that will all work out, and I’ll take the three seconds!
[Update: everything’s working in our current under-development app with my own rails_config, and I’m not sure the iconv error is a rails issue as I trace through things]
[Update 2: The deprecation warning is coming from css_parser which is required by inline-style which we have forked in order to provide specific functionality we apparently need to reference an external mobile stylesheet but still convert inline styles.]
[Update 3: if you are landing on this post from search for the iconv error — you’ve got something requiring it in your app — see this stack overflow post]