mime-types 3?
MrJoy opened this issue · comments
Would allowing newer versions of the mime-types gem be feasible at the moment? It looks like, barring use of deprecated methods, it should be a pretty painless changeover...
The mail gem depends on mime-types 1.x or 2.x. The mail gem is used by Rails, so if we were restricted to mime-types 3.x we won't be compatible with rails.
If we supported 1.x through 3.x it would be OK.
@MrJoy Would you show us how mechanize does not work well with mime-types 3? At least I fixed the test suite to work with mime-types 3.x, but haven't looked into real-world use cases.
The upcoming (currently in rc2) mail gem 2.6.4 supports mime-types 3.0, so mechanize could update its gemspec soon.
legacy rails apps will be using legacy mail, so mechanize will still need to be flexible with its dependecy
Wouldn't that imply that running mechanize in an app that requires mail >= 3.0 for some reason will not be possible?
I'll remove the "< 3" requirement later. I thought I had done that already.
@knu The "< 3" requirement is still in mechanize.gemspec – looking forward to the removal, thanks a lot!
+1 3th version has memory optimizations. What status on that?
Sorry, this just slipped from my todo list.
@knu Are you planning release it with bump version soon?
@knu As this issue seems to have been fixed 10 weeks ago: is there anything holding back bumping the version so we can use mime-types 3.x? Thanks!
@knu In case there is a problem that needs to be fixed before bumping the version, could you share the specifics? Maybe we can assist. Thanks.
Finally, I've rolled out a new release 2.7.5. I'd appreciate if any of you could check it out and give some feedback on this!