For the latest news on what's happening in the Perl world, check out these sites:

If you have a Perl-related news item you'd like to share, you may post it in the Perl News section. Please try to avoid duplicating news; but pointers (with summaries) to important stories on other sites are acceptable here.

Perl News
New "miniconf" scheduled for 18th of November
No replies — Read more | Post response
by hippo
on Aug 24, 2021 at 10:20

    As announced in this post there is planned to be a one-day online "miniconf" for Perl and Raku in November. It will be held via Zoom and Thibault Duponchelle has posted the call for papers.

    The talks can be about toolchain, devops, cloud, sysadmin, core, design patterns, web or whatever linked to Perl or Raku.


The ephemeral miniconf
No replies — Read more | Post response
by contra-sh
on Aug 24, 2021 at 10:16
    The ephemeral miniconf is a Perl and Raku virtual miniconf that will take place online the 18 november 2021. Follow the link (announcement/call for papers blog post) for details :)
The Corinna RFC for getting modern OO into the Perl core is taking shape
6 direct replies — Read more / Contribute
by Ovid
on Aug 18, 2021 at 12:04
Proposed change regarding "Taint" support
6 direct replies — Read more / Contribute
by syphilis
on Aug 13, 2021 at 08:41

    This post appeared on the p5p mailing list earlier today.
    As someone who has never personally experienced any utilitarian benefit from perl's purported tainting capabilities, it was something that I was pleased to see.

    However, from twenty years ago (give or take), I do recall a statement from a prominent perl figure named Larry in which he stated that he would not run perl scripts for any purpose at all unless taint checking was applied.
    Are there others here that recall that statement ?
    How do we reconcile that statement with the proposed change ?
    Are there people here who would refuse to use a perl that was built without taint checking capability ?

    Just wonderin' .....

Another resignation, this time from CAT
3 direct replies — Read more / Contribute
by davies
on Aug 09, 2021 at 15:17
OT. Malicious software in PyPI
1 direct reply — Read more / Contribute
by parv
on Jul 30, 2021 at 08:18
Perl/Raku community involvement survey
3 direct replies — Read more / Contribute
by jdporter
on Jul 16, 2021 at 13:53

    Episodic Volunteering in Free/Libre/Open Source (FLOSS) Communities - a survey by kudra

    TPF announcement

    ... research to understand episodic, or occasional, participation in the Perl and Raku communities... The results of the research will be provided as a TPF report and will assist the community in improving practices for managing episodic participation to provide insights into what FLOSS projects could do to become more sustainable.
Net::Clacks Important data corruption bugfix released
2 direct replies — Read more / Contribute
by cavac
on Jul 07, 2021 at 03:39

    I usually try to avoid clobbering the PM News section with release information about my modules. But i found a problem in my Net::Clacks::Server which can, under the wrong circumstances, either prevent startup or lead to all sorts of data corruption in cached data.

    I have fixed this in Version 18 (at least i think it is completely fixed, bug reports are welcome).

    Unfortunately, this upgrade features an incompatible change that clobbers the persistance file. There is a workaround for that to keep your cached data, though. From the UpgradeGuide.pod:

    WARNING: BREAKING CHANGES regarding persistance files.
    Version 18 provides better reliability for the Clacks Server when using a persistance file, including startup problems and prevention of data loss.
    Here is the problem in older versions: If the server process is killed while writing the persistance file, the file on disk may be invalid (partial data) or completely blank. Blank files at least prevented the server from starting up, but otherwise incomplete files could lead to data corruption in cached data and/or all other sorts of problems. This relates to the fact that the server only does very minimal checks on its internal cache during runtime for performance reasons. The original persistance file was just a quick hack to dump/restore the cache between runs and did not account for system crashes or the process being killed while writing to disk.
    This new version of Net::Clacks::Server tackles this in in a multi-stage approach:
    1.) The persistance file now includes the ENDBYTE string as a third line. This is used to check if the file is complete.
    2.) Before overwriting the current persistance file, it is COPIED to a file with '_bck' added to the configured name.
    3.) The file is written under a new name (with '_' added at the end) and then MOVED over the correct file name. File move (rename) within the same directory should be an atomic operation of the operating system, so it either works or doesn't (no stopping half-way inbetween).
    4.) An invalid persistance file doesn't prevent the clacks server startup. If it detects an invalid file, it first tries to load the previous version ('_bck'), then as a last desperate measure to prevent data loss, it tries to load the temporary file ('_'). If that also fails, it starts 'blankety-blank'.
    Clacks caching was always designed as a CACHE, not as the final storage for important data. This upgrade to Version 18 changes the file format of the persistance file slighty. The older format is now detected as invalid, resulting in a "blankety-blank" startup. If you really want or need (?!?!?!) to preserve the cached data for some reason, there are two ways to accomplish this:
    1.) Stop the clacks server and upgrade the Net::Clacks package. Edit the persistance file and add a third line with the word "ENDBYTES" without quotes as its only content.
    2.) If you are running a master/slave setup with interclacks, you can stop ONLY the server that has the persistance file. Then upgrade Net::Clacks and start the server. It should start "blankety-blank" and automatically resyncronize cached data from the interclacks network. It works the same if all your clacks servers use persistance files for some weird reason, just restart them one-by-one, waiting inbetween for the interclacks sync to finish. You can use the example Connect to the server you keep running and start the MONITOR command. While interclacks sync is in progress, you will see KEYSYNC commands flying between the servers. If you stop seeing them for a few seconds, KEYSYNC is finished.

    perl -e 'use Crypt::Digest::SHA256 qw[sha256_hex]; print substr(sha256_hex("the Answer To Life, The Universe And Everything"), 6, 2), "\n";'
New TPF Finding a shared vision of Perl post
No replies — Read more | Post response
by eyepopslikeamosquito
on Jul 05, 2021 at 21:11
The Perl and Raku Conference 2021 online
No replies — Read more | Post response
by Discipulus
on Jun 08, 2021 at 02:55
    Hello folks!

    today starts the The Perl and Raku Conference, Conference in the Cloud, at 11:30 New York time (16:30 GMT).

    You can see how-to-attend-this-conference and the whole scheduling.

    Profit it!


    There are no rules, there are no thumbs..
    Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.
Perl questionaire by Gobby
7 direct replies — Read more / Contribute
by Tux
on Jun 02, 2021 at 03:54

    A shared Vision of Perl


    Welcome to the survey on a shared vision of Perl!

    Gobby is an innovative, Perl-based, survey tool. We're committed to the future of the Perl ecosystem and people that make up these communities.

    We're looking for support in the development of Gobby as a Perl product. Please drop us a line to if you like our approach to surveys and would like to be part of Gobby's future.

    Best wishes,

    Gary Beckwith
    Founder of Gobby

    Enjoy, Have FUN! H.Merijn
#perl irc channel moved from freenode to
No replies — Read more | Post response
by Discipulus
on May 27, 2021 at 03:30
    Hello folks!

    other news (thuesday of past week) for the no|one|many perl community: the #perl irc channel moved from freenode to

    > May we live in less interesting times

    The above quote from (one of?) the announcement

    Infact there was a massive migration from freenode to libera.

    If you connect to the #perl old channel on freenode you will be automatically redirected to the ##perl channel not owned by previous people.

    Relevant articles: freenode_staff_resigns and freenode_the_mainstream_irc_network_is_collapsing

    There is also a youtube resume of the mass migration


    There are no rules, there are no thumbs..
    Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.
SO Developer Survey time
4 direct replies — Read more / Contribute
by 1nickt
on May 26, 2021 at 10:43
berrybrew version 1.34 released!
2 direct replies — Read more / Contribute
by stevieb
on May 25, 2021 at 22:31

    I've released version 1.34 of berrybrew.

    Notable changes:

    • UI elements now update on the fly, so all changes are reflected immediately
    • You can 'use' any version of Perl you've got installed from the UI, which'll open a new CLI window set to the selected version
    • You can now fetch the updated list of Strawberry Perls available through the UI
    • Cloning installed Perls as well as a myriad of other operations can now be done through the UI
    • The API has been updated so that internal objects are updated live-time. This makes having long-running processes possible
    • Build/Test infrastructure updates
    • Documentation updates
    • Minor bug fixes

    I've just got a new full time job, programming in Perl... finally, after several years of looking for that perfect work environment. Some of it will be on Windows (which I haven't used except for developing berrybrew), so I'm actually looking forward to using my own software, especially how useful its become thanks to the new UI I've developed.

    Happy Perling!


Perl 5.34 is released
5 direct replies — Read more / Contribute
by 1nickt
on May 21, 2021 at 05:22

    Perl version 5.34 is now available. perldelta.

    The way forward always starts with a minimal test.

Add a piece of Perl News
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":