From: "usa (Usaku NAKAMURA) via ruby-core" Date: 2023-11-06T11:22:40+00:00 Subject: [ruby-core:115265] [Ruby master Bug#19985] Confusing error message when nonexistent `Pathname` for `require` Issue #19985 has been updated by usa (Usaku NAKAMURA). Backport changed from 3.0: REQUIRED, 3.1: REQUIRED, 3.2: REQUIRED to 3.0: REQUIRED, 3.1: DONE, 3.2: REQUIRED ruby_3_1 881088e06f092d20a361c9528b2927cdc2b1616c merged revision(s) 4329554f171fdb483cafa672df5f2a08741940c5. ---------------------------------------- Bug #19985: Confusing error message when nonexistent `Pathname` for `require` https://bugs.ruby-lang.org/issues/19985#change-105181 * Author: vo.x (Vit Ondruch) * Status: Closed * Priority: Normal * Backport: 3.0: REQUIRED, 3.1: DONE, 3.2: REQUIRED ---------------------------------------- It seems that RubyGems / Bundler `require` method overrides of accept `Pathname` as and argument ~~~ $ ruby -rpathname -e ' pa = Pathname.new("test") require pa ' :85:in `require': cannot load such file -- test (LoadError) from :85:in `require' from -e:3:in `
' ~~~ while plain Ruby require does not: ~~~ $ ruby --disable-gems -rpathname -e ' pa = Pathname.new("test") require pa ' -e:3:in `require': no implicit conversion of Pathname into String (TypeError) from -e:3:in `
' ~~~ This inconsistency is surprising. It seems that RubyGems / Bundler developers think [1] that Ruby `require` should also accept `Pathname`. ~~~ $ ruby -v ruby 3.2.2 (2023-03-30 revision e51014f9c0) [x86_64-linux] ~~~ [1]: https://github.com/rubygems/rubygems/pull/7128 -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/