Howdy, all,

A user of an open-source project of mine reports that when he upgraded to Fedora 22, the following statement started causing an error:

use open ":encoding(utf8)";

He gets this:

$ perl
use open ":encoding(utf8)";
Can't locate open.pm in @INC (you may need to install the open module)
(@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5
/usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl
/usr/lib64/perl5 /usr/share/perl5 .) at - line 1.
BEGIN failed--compilation aborted at - line 1.

[download]

Running perl --version shows that he's running perl 5.20.2. I'm running 5.18 and can't reproduce the error.

Is "use open" deprecated? I don't see any mention of it in the perldelta. Can anyone who's running perl 5.20 confirm whether or not this error occurs for them, either on Fedora or some other system?

Thanks in advance!

In reply to "use open" fails in perl 5.20? by bcrowell2

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.