search for: rdpoor

I''m working through an idea for a db-backed cache for Mechanize#get(). The idea is to use a Mechanize::Agent#post_connect_hook to cached any fetch data, and create a subclass of Mechanize::Agent#get() that checks the cache before calling super. I want to store the un-parsed (raw) page in the db, and call Mechanize#parse when there''s a cache hit, something along these lines:

This is more a Ruby than a Rails question -- feel free to redirect me as appropriate -- but either this is a Ruby 1.9 bug or I have some serious misunderstanding. Essentially, I''ve caught the <=> operator returning nil -- not -1, 0, or 1, but nil. Schematically: class A attr_accessor :slot fun matches?(s) p "s <=> @slot = #{s <=> @slot}" return

I am accustomed to the LIBSVM package, which provides cross-validation on training with the -v option % svm-train -v 5 ... This does 5 fold cross validation while building the model and avoids over-fitting. But I don't see how to accomplish that in the e1071 package. (I learned that svm(... cross=5 ...) only _tests_ using cross-validation -- it doesn't affect the training.) Can

I''m 99% certain that this is what''s being discussed in https://github.com/tenderlove/mechanize/issues/168 But I''m not sure what the remedy is. My production app is running on Heroku, so I need a fix that I can push there. Can someone post instructions that this neophyte can follow? (I gather I''m supposed to fork and add the current master version from