# New Ticket Created by Kent Fredric # Please include the string: [perl #127875] # in the subject line of all future correspondence about this issue. # <URL: https://rt.perl.org/Ticket/Display.html?id=127875 > There's been a lot of idle chat about this, but not any real commitment to a resolution either to block, or to vocally state an intent to release with a known broken and significant module. - https://rt.cpan.org/Ticket/Display.html?id=112246 - Scope::Upper is broken because of Stack Context Changes - There is a respectable number of consumers of Scope::Upper, including: -- Dancer2 -- TryCatch Both of these are expected to be actively in use in the real world, and TryCatch has been in the Task::Kensho recommendations list for several years, as well as Task::Moose( amusingly, its a hidden dependency due to features ), which stands to reason there would be a considerable amount of darkpan using it. https://metacpan.org/requires/distribution/TryCatch?sort=[[2,1]]&size=500 Given these factors, a resolution of "It shouldn't have done that, so its ok we break a lot of working code" leaves more than a sour taste in the mouth. If we don't fix this now and block release, I fear we're going to be stuck in the same way 5.22 was, breaking known, heavily used modules like Coro, and still without a resolution an entire major release later. ( Please lets not be distracted by my choice of example, but focus on the principle )Thread Previous | Thread Next