Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

schwern (1528)

schwern
  (email not shown publicly)
http://schwern.net/
AOL IM: MichaelSchwern (Add Buddy, Send Message)
Jabber: schwern@gmail.com

Schwern can destroy CPAN at his whim.

Journal of schwern (1528)

Monday October 15, 2007
07:29 PM

use_ok() fix to Test::More going back REAL SOON NOW!

[ #34684 ]

The fix to use_ok() in Test::More which revealed failures in DBI, XML::LibXML and WWW::Mechanize (amongst others) is going back in REAL SOON NOW. XML::LibXML has updated but DBI and WWW::Mechanize have not. They've all known about the problem for over a month now. An alpha version has just been released.

This time, I'm not rolling back.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Please provide the full list of affected modules known so far. Saying "Amongst others" isn't helping anybody. This fix is going to break a whole lot of CPAN and will make it difficult to understand which breakages come from Test::Simple and which have other problems. As long as we have not a collection of patches that fix the modules known to affected this step isn't acceptable.
    • To provide the full list is probably well beyond Schwern's forces. This issue affects a lot of testing code out there that is just plain wrong (because use_ok within a BEGIN would succeed even though no plan had been set).

      Some of the affected modules were spotted [perl.org] by Aristotle and others in a thread started one month ago [perl.org] at perl-qa mailing list. Schwern applied a fix and announced it I think he did what people would expect him to do.

      It is a pity if many of the authors of affected modules never

      • Well, it's not only Schwern's duty to fix a bug when he finds it but also to refuse to fix a bug when the community does not work as it should.

        So far there has not been observable effort to provide the list of affected modules. For a smooth transition we'd need a single document or wiki page where interested parties can work together to minimize the damage for the community as a whole.

        Pointing to that mailing list thread is not helpful when one wants to know if all authors have been informed personally. I w
        • Somebody, not necessarily Schwern should start to do it
          That reminds me a saying that I hear often at $work:

          Well volunteered!
  • I'm sorry for the delay getting a new DBI release out. The Test::More fix got stuck behind adding client-side caching to DBD::Gofer, which then got stuck behind other work. Not ideal, but that's the way it worked out this time.

    Anyway, I've accepted your swift kick up the backside and got the DBI chages finished off this morning. A 1.59_90 release is up now for cpan-testers to chew on. If that goes well then I'll make a full release before the end of this week.