develooper Front page | perl.perl5.porters | Postings from March 2023

Re: Deprecation doesn't mean we have two release cycles beforethings break.

Thread Previous | Thread Next
From:
Karen Etheridge
Date:
March 1, 2023 00:01
Subject:
Re: Deprecation doesn't mean we have two release cycles beforethings break.
Message ID:
CAPJsHfC9MsK0M-CvhMm9ZAhOQokUcVwcu8pLTW0u81hczEr1+A@mail.gmail.com
On Tue, Feb 28, 2023 at 5:42 AM demerphq <demerphq@gmail.com> wrote:

> I can see the argument, but i can also see the counter argument; that
> people want to test that their code functions correctly and is warning
> free. Modules like Test::Warn wouldn't exist if this weren't a common
> practice. I don't think we will get a lot of traction telling people not to
> do it. Maybe Test::Warn should know to ignore deprecation warnings except
> when AUTHOR_TESTING is true.
>
> See
> https://github.com/Perl-Toolchain-Gang/toolchain-site/blob/master/lancaster-consensus.md
>
> Even then i can see people arguing that one either way. Regardless for
> perl5-porters, i believe our position is we take responsibility if
> something we do breaks something on CPAN, even if really it shouldnt have.
> Hyrums law in a nutshell i guess.
>
> https://www.hyrumslaw.com/
>

 Yes, it's been my practice for many years to only enable fail-on-warnings
when AUTHOR_TESTING is true. All test files in my distributions do this:

   use if $ENV{AUTHOR_TESTING}, 'Test::Warnings';

Thread Previous | 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