json_pure gem conflicts with json gem

[matthauck]

Is there a reason why brakeman depends on "json_pure" gem instead of the more standard "json" gem? Currently brakeman is the only project in my gemfile that depends on json_pure instead of json, resulting in two conflicting classes being loaded into memory. I think I can work around it with some Gemfile trickery, but why not just depend on the JSON library and require "json/pure" to allow for greater compatibility?

[oreoshake]

IIRC it was done so it doesn't depend on anything with C extensions, making it easier to deploy in some scenarios.

[matthauck]

I think it would because I have other gems that depend on it and haven't ever noticed any conflicts

On Oct 9, 2012, at 2:41 PM, Neil Matatall notifications@github.com wrote:

IIRC it was done so it doesn't depend on anything with C extensions, making it easier to deploy in some scenarios. Does MultiJSON help out at all in this situation?

—
Reply to this email directly or view it on GitHub.

[presidentbeef]

I'm fine with using multi_json. I looked into it before and thought it didn't actually provide a JSON library, but I'm re-reading the docs now and I was mistaken.