I noticed this line in the gemspec which appeared to have been accidentally changed:
# coding: utf-8
This reverts it to:
# encoding: utf-8
While I was at it, I added myself to the gemspec 😎
properly designate gemspec file encoding
Actually, that change was intentional. coding is correct. encoding is a Python thing (but it works in Ruby because it contains the substring coding). See http://hyperpolyglot.org/scripting#source-code-encoding. This is less relevant than it used to be, since UTF-8 is the new default (en)coding for source files in Ruby 2.0.0.
I'm going to close this pull request but it's my honor to add you as an author in the gemspec, which I've just done here: 987ec69.
I had a feeling it was intentional but couldn't find the requisite source referring to the right way to represent it.
Thanks for adding me ❤️
Actually, I was slightly wrong. It doesn't actually match the substring. Here’s the relevant code in parse.y: https://github.com/ruby/ruby/blob/ruby_1_9_3/parse.y#L6422-L6426