minus7

I don't see the problem; reading and writing different encoding works fine. The CSV module makes no problems either:

  in_file = open("in.csv", 'r', encoding='latin-1')
  in_csv = csv.reader(in_file)
  out_file = open("out.csv", 'w', encoding='utf-8')
  out_csv = csv.writer(out_file)
  out_csv.writerows(row for row in in_csv)

Exactly. Its clear distinction between (unicode) strings and (binary) data is Python 3's biggest plus, imho. No more randomly popping up errors because something is trying to handle the binary data in your str as string; instead you'll get a nice type error. I don't understand how people do _not_ find that terribly annoying with Python 2. (seriously, tell me)

Very cool! If you're familiar with CFFI already just skip the first half of the video or check out the blog post: http://codelle.com/blog/2016/5/embedding-pypy-in-a-c-applica...

Using IP-to-country resolution and ignoring the Accept-Language HTTP header seems to be a pretty common tactic these days.

Add a gif/webm of it in action to your readme. That will make it a lot easier and nicer to see what it's doing.

We removed the donation button because we don't really have any running costs to cover.

Thanks for the hint. I moved the files to another host, check the site again.