in reply to Inline::Python sucks

Someone tell the one who wrote this module that it doesn't work please
There are 3 much more effective ways to notify the author of problems than ranting here at PerlMonks:
  1. Rate the module on CPAN ratings.
  2. Submit a bug report on CPAN.
  3. Send an email to the author.
There are links and info at Inline::Python. The 1st 2 require that you create an account, which judging by your anonymity, may be a challenge for you. It would also require a little more effort than "It didn't work.".
I just tried Inline::Python because I thought it would work.
The CPAN Testers provide plenty of indicators to a module's quality, as do the bug reports, both of which can be found at Inline::Python. The next time you try to use a new module, you should glance at them before you take the plunge.
how big CPAN is and how good it is, but really... that's not where it's at.
There are plenty of great modules on CPAN. What... you expect everything to be great? Sometimes you get what you pay for. It's free!

Replies are listed 'Best First'.
Re^2: Inline::Python sucks
by salva (Canon) on May 15, 2010 at 07:17 UTC
    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.

[reply]
A reply falls below the community's threshold of quality. You may see it by logging in.

In Section Seekers of Perl Wisdom