-
Notifications
You must be signed in to change notification settings - Fork 333
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JSON 1.8.3 is not compatible with ruby 2.4 preview #303
Comments
Running into the same issues. Happy to provide any additional information if it would be helpful. |
See also #286, which was closed without comment. |
you have to use the 2.0 version with ruby 2.4 |
@alepore that's not doable if you're stuck on Rails 4.2.x - for example from my Gemfile.lock
|
Could it be possible to backport the integer unification commit? 8e16a60 |
- json: "~>2.0" # ruby/json#303 (comment) - pygments.rb: "~>1.1"
- json: "~> 2.0" # ruby/json#303 (comment) - pygments.rb: "~> 1.1"
In case it matters, aws-sdk-v1 depends on ~> json 1.4, and upgrading to aws-sdk v2 is a major project we hope to do later next year. This json incompatibility blocks us from going to ruby 2.3 to 2.4 today :\ |
Ruby 2.4.0 does not work with version 1.8.3 of the JSON gem which was required by ActiveSupport 4.x. Allowing use of ActiveSupport 5.x in turn allows use of JSON 2.x which is compatible with 2.4.0 ruby/json#303
@rhymes I already removed json dependency on 4-2-stable branch of rails/rails. see rails/rails#26334 You can use Ruby 2.4.0 with Rails 4.2.8 that is next minor release. |
fpm depends on 'json < 2.0, >= 1.7.7', but unfortunately json versions before 2.0 does not support Ruby 2.4, see: ruby/json#303
- needs ruby < 2.4.0 due to conflict with son 1.8.3 - see ruby/json#303
I've never seen such a complicated to get working language. For God sake !!! Thru the years I've used apt, rvm, rbenv, chruby ..... nightmare. Always spending much more time setting up than developing !!! |
bundle install failed on my machine because I use ruby 2.4.1 and the json gem version 1.8.3 was not compatible. This problem has now been fixed: ruby/json#303
because we need ruby stuff, not go stuff note: - ruby 2.3 because json library that fpm seemingly wants to use doesn't work with 2.4 (ruby/json#303) - for some reason apt-get update no longer needed
because we need ruby stuff, not go stuff note: - ruby 2.3 because json library that fpm seemingly wants to use doesn't work with 2.4 (ruby/json#303) - for some reason apt-get update no longer needed
Jekyll would not compile against `json-1.8.3` on Ruby 2.4. Reference: ruby/json#303
Version 1.8.3 of the json gem isn't compatable with ruby 2.4 and later. see: ruby/json#303 Specifically require the json gem to ensure we fetch a compatible version.
Version 1.8.3 of the json gem isn't compatable with ruby 2.4 and later. see: ruby/json#303 Specifically require the json gem to ensure we fetch a compatible version.
Ruby 2.4 is already EOL. This issues was resolved at the latest stable versions. |
Because of this I couldn't upgrade my rails
4.2.5
app as I am getting this errorAs per my knowledge this issue has been raised because of ruby unification integer.
The text was updated successfully, but these errors were encountered: