[#91458] [Ruby trunk Feature#4475] default variable name for parameter — matz@...
Issue #4475 has been updated by matz (Yukihiro Matsumoto).
3 messages
2019/02/07
[ruby-core:91398] [Ruby trunk Bug#15586] Requiring `bundler/setup` gets wrong version
From:
markjreed@...
Date:
2019-02-04 20:04:54 UTC
List:
ruby-core #91398
Issue #15586 has been reported by MarkTheStrange (Mark Reed). ---------------------------------------- Bug #15586: Requiring `bundler/setup` gets wrong version https://bugs.ruby-lang.org/issues/15586 * Author: MarkTheStrange (Mark Reed) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.6.1p33 (2019-01-30 revision 66950) [x86_64-darwin18] * Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN ---------------------------------------- The statement 'require "bundler/setup"' always loads the version that ships with ruby (Bundler 1.17.2 as of Ruby 2.6.1), even if a newer version of Bundler is installed via RubyGems. On the other hand, requiring plain "bundler" gets the gem-installed version. Demo: $ ruby -rbundler -e 'puts Bundler::VERSION' 2.0.1 $ ruby -rbundler/setup -e 'puts Bundler::VERSION' 1.17.2 This breaks pretty much all my bundled applications, which start by requiring `bundler/setup`, which fails when the Gemfile.lock was created by Bundler 2.x and the loaded Bundler is 1.x. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>