Bugs item #25564, was opened at 2009-04-21 03:30 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25564&group_id=126
Category: other Group: v1.3.x Status: Open Resolution: None Priority: 3 Submitted By: Emanuele Vicentini (emanuelev) Assigned to: Nobody (None) Summary: Time.today not working with 1.3.2 Initial Comment: $ gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.2 - RUBY VERSION: 1.8.6 (2008-03-03 patchlevel 114) [universal-darwin9.0] - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8 - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby - EXECUTABLE DIRECTORY: /usr/bin - RUBYGEMS PLATFORMS: - ruby - universal-darwin-9 - GEM PATHS: - /Library/Ruby/Gems/1.8 - /Users/emanuele/.gem/ruby/1.8 - /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - REMOTE SOURCES: - http://gems.rubyforge.org/ Running the following gives problem: $ ruby -rubygems -e 'puts Time.today' /Library/Ruby/Site/1.8/rubygems/specification.rb:16:in `today': undefined local variable or method `location_of_caller' for Time:Class (NameError) from -e:1 Noted this even on an Ubuntu GNU/Linux box with Ruby 1.8.7. On both machines there are some gems (Rails, Rake, Rack and many others), but the load paths do not seem to be messed up: $ ruby -rubygems -e 'puts Time.today rescue nil; puts $:' /Library/Ruby/Site/1.8 /Library/Ruby/Site/1.8/powerpc-darwin9.0 /Library/Ruby/Site/1.8/universal-darwin9.0 /Library/Ruby/Site /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8 /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/powerpc-darwin9.0 /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin9.0 . ---------------------------------------------------------------------- >Comment By: Luis Lavena (luislavena) Date: 2009-04-22 08:47 Message: Was under deprecation warning between 1.x and 1.3, now it got removed. ---------------------------------------------------------------------- Comment By: Emanuele Vicentini (emanuelev) Date: 2009-04-22 03:03 Message: Right; that's why I expected it to show a warning, not to raise a NameError exception. Anyway, I agree with you that it is a no-priority issue. Have a nice day. ---------------------------------------------------------------------- Comment By: Luis Lavena (luislavena) Date: 2009-04-21 10:03 Message: Time.today has been deprecated. See the release notes. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=25564&group_id=126 _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers