[#115244] [Ruby master Feature#19987] add sample method to Range — "horv77@... (Andras Horvath) via ruby-core" <ruby-core@...>
Issue #19987 has been reported by horv77@protonmail.com (Andras Horvath).
6 messages
2023/11/05
[#115247] [Ruby master Feature#19988] AI for inner code behavior analysis at runtime — "horv77@... (Andras Horvath) via ruby-core" <ruby-core@...>
Issue #19988 has been reported by horv77@protonmail.com (Andras Horvath).
3 messages
2023/11/05
[#115404] Ruby 3.2.2 - rbconfig.rb's MAKEFILE_CONFIG — Jay Mav via ruby-core <ruby-core@...>
Hello Ruby Dev Team,
4 messages
2023/11/17
[ruby-core:115230] [Ruby master Feature#19985] Support `Pathname` for `require`
From:
"jeremyevans0 (Jeremy Evans) via ruby-core" <ruby-core@...>
Date:
2023-11-02 14:37:27 UTC
List:
ruby-core #115230
Issue #19985 has been updated by jeremyevans0 (Jeremy Evans).
zverok (Victor Shepelev) wrote in #note-2:
> Even funnier that bare `load` does support the convention:
> ```
> $ ruby --disable-gems -r pathname -e "load Pathname.new('test')"
> -e:1:in `load': cannot load such file -- test (LoadError)
> ```
That's not funny, it's expected, as `load` deals exclusively with paths, and `require` does not generally deal with paths. Example:
```
File.write("x.foo", "p 1")
load("x.foo") # prints 1
load("./x.foo") # prints 1
require("x.foo") # LoadError
require("./x.foo") # LoadError
```
Now, if you have a path ending in `.rb`/`.so`/etc., you can get require to accept it directly. But in general, `require` does not deal with paths. I don't think we should add Pathname support to `require`.
----------------------------------------
Feature #19985: Support `Pathname` for `require`
https://bugs.ruby-lang.org/issues/19985#change-105146
* Author: vo.x (Vit Ondruch)
* Status: Open
* Priority: Normal
----------------------------------------
It seems that RubyGems / Bundler `require` method overrides of accept `Pathname` as and argument
~~~
$ ruby -rpathname -e '
pa = Pathname.new("test")
require pa
'
<internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in `require': cannot load such file -- test (LoadError)
from <internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in `require'
from -e:3:in `<main>'
~~~
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 `<main>'
~~~
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/