In that order, please:
  1. submit a bug report
  2. submit a patch
  3. give the author some time to solve the issue
  4. and finally, if the author is unresponsive or just don't want to solve the issue, then you can complain publicly about the bad status of the module.

It's Open Source, even a non working module is not something useless, it is something you can repair yourself and make functional for much less effort than writing the whole thing from scratch (well, mostly).

Using CPAN Ratings (or any other forum) to complaint about broken modules before letting the author know and solve any issue, well, I think this way of doing is very disrespectful.

In reply to Re^2: Inline::Python sucks by salva
in thread Inline::Python sucks by Anonymous Monk

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.