develooper Front page | perl.perl5.porters | Postings from May 2022

Pre-RFC: add version numbers to errors/warnings containing packagenames

Thread Next
From:
Ovid
Date:
May 28, 2022 11:17
Subject:
Pre-RFC: add version numbers to errors/warnings containing packagenames
Message ID:
CA+M4CHv6qgfYDWCeXaN_20Dzm+vDrrmLzMHDqgWASAWYsz7=bw@mail.gmail.com
Hi all,

Not sure what it would take to do this, but this kind of error crops up a
few times:


Can't locate object method "some_method" via package "Some::Class"


In my case, it turns out that some CPAN testers were using versions of a
Type::Tiny released eight years ago.

It would be nice if the error looked like this:

Can't locate object method "some_method" via package "Some::Class, version 1.01"


In another example, CPAN testers failing for
Dist-Zilla-Plugin-BumpVersionAfterRelease 0.018, Package::Stash is missing
a method, but, this package doesn't show up in the package/version list
<http://www.cpantesters.org/cpan/report/3b818100-0c4d-11e9-b2fc-4ec6980eb343>
near the top of the error report. I had to dig into the relevant Changelog
<https://metacpan.org/dist/Package-Stash/changes>, to learn that these CPAN
testers are using a version of Package::Stash released in 2010! Changelogs
are very hit or miss.

I realize that not all packages have properly declared versions, the
package might not be loaded, or the version might be otherwise corrupted,
but this change would make it easier for developers to track down bugs.

Best,
Ovid
--
CTO, All Around the World
World-class software development and consulting
https://allaroundtheworld.fr/

Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About