Bug #1733

require does not look at current directory anymore ?

Added by Chauk-Mean Proum almost 6 years ago. Updated about 4 years ago.

[ruby-core:24153]
Status:Rejected
Priority:Normal
Assignee:-
ruby -v:ruby 1.9.2dev (2009-07-03 trunk 23939) Backport:

Description

=begin
In ruby-1.9 trunk, the behaviour of require has changed.
Require does not look at the current directory anymore.
Is this intentional ?

$ cat a.rb
puts "Hello World"

$ cat b.rb
require 'a'
puts "Goodbye World"

$ ruby -v b.rb
ruby 1.9.2dev (2009-07-03 trunk 23939) [i386-mingw32]
b.rb:1:in require': no such file to load -- a (LoadError)
from b.rb:1:in
'

Replacing require 'a' with require './a' or require_relative 'a' works.
But this introduces incompatibility issues with code that works with ruby-1.8 and ruby-1.9.1-p129.
=end

History

#1 Updated by Yukihiro Matsumoto almost 6 years ago

=begin
Hi,

In message "Re: [Bug #1733] require does not look at current directory anymore ?"
on Mon, 6 Jul 2009 01:53:31 +0900, Chauk-Mean Proum redmine@ruby-lang.org writes:

|In ruby-1.9 trunk, the behaviour of require has changed.
|Require does not look at the current directory anymore.
|Is this intentional ?

Yes, there was a security risk.

                        matz.

=end

#2 Updated by Nobuyoshi Nakada almost 6 years ago

=begin
Hi,

At Mon, 6 Jul 2009 01:53:31 +0900,
Chauk-Mean Proum wrote in :

Replacing require 'a' with require './a' or require_relative
'a' works.
But this introduces incompatibility issues with code that
works with ruby-1.8 and ruby-1.9.1-p129.

In what cases do you need it in the load path?

Command line option -I. or environment variable RUBYLIB="."
can't help you?

--
Nobu Nakada

=end

#3 Updated by Chauk-Mean Proum almost 6 years ago

=begin
Matz, thanks for the explanation/clarification.

Nobu, the RUBYLIB environment variable is a good enough solution. Thanks.

=end

#4 Updated by Yuki Sonoda almost 6 years ago

  • Status changed from Open to Rejected

=begin

=end

Also available in: Atom PDF