• Instead of using the DATA handle to get at as-yet-unloaded locale data in
  DateTime::Locale::Data, we now read the raw data into memory once, and use
  eval to turn it into Perl data structures as a particular locale is
  requested. This may fix a problem where reading from the DATA handle somehow
  returned the wrong chunk of data (or overlapped multiple locales). The
  downside is that loading DateTime::Locale now uses an additional 4MB of
  memory on my system, regardless of how many individual locales are
  instantiated. Reported by Greg Oschwald. GitHub #3.