Eric Hodel wrote:
> On Mar 1, 2010, at 15:28, Joshua Kolden wrote:
>> Any more clues would be appreciated.  Also if the author of the 
>> offending gem would please step forward for your flogging.
> 
> grep -r require_paths `gem env home`/specifications | grep -v \\[
> 
> Should help you locate it.

Having the same problem here.

Running `gem` with any parameters did not really help since it died 
right away with the same exception.

The problem is caused by faulty gemspec of "unicode" gem (new version of 
that gem was released not so long ago). Removed unicode gemspec and 
gemcode, good as new.
-- 
Posted via http://www.ruby-forum.com/.