blogs.perl.org

June 30 is the deadline to submit a talk to this year's YAPC::EU in Granada.

A Perl module to handle roles (users and groups) in PostgreSQL, Role::Pg::Roles

This year's edition of the SPW will be amazing.
We are proud and happy that we have been able to attract so many Perl hackers (32 so far). A whole team of Perl 6 people will give us some more insights in the newest area of the Perl 6 development. And there is still plenty of room for more Perl 5 and Perl 6 topics. The CFP is not closed yet, so please bring in yourself and Submit your talk. Or consider to hold a workshop on Saturday. Just let us know.

Hey, Perl 6 hackers, if you like to join our Perl 6 hackathon which runs in parallel to the workshop, please sign up. It is starting already Thursday, 27. August.

Did I tell you already about our kitchen team? Their creations have been delicious! Attendees of 2014 know what I am talking about. So, give yourself a chance and join us on Friday, 28. August and Saturday, 29. August 2015.
Buy your ticket soon.

See you there...

There is more than one way to make perl5 twice as fast, but this is what I did today. I fixed it on one machine.

My Macbook Air gives constantly better results in my hash function benchmarks than my big Linux Desktop PC, because it has a newer i7 Haswell, and the linux has only an older i5 CPU. Both have fast SSD's and enough RAM.

But when I run the perl5 testsuite the linux machine is twice as fast. Typically 530s vs 1200s. Which is odd and very annoying.

And then I fixed it with one little change.

I was lucky enough to be able to attend YAPC::NA 2015 in Salt Lake City, this year. First and foremost I have to applaud the organizers, the event was so well coordinated it looks positively effortless, which I’m sure masked the huge amount of effort that it takes to appear so.

After not being able to attend the last two YAPC::NAs, it was such a joy to be back. As my new friend VM Brasseur has been saying in #yapc lately, “these are my people.” The community feeling at all Perl meetings, and especially at YAPC::NA, is overwhelming and I loved meeting and reconnecting with so many fellow Perlers.

Hi all,

just to report there is an issue building Perl (v5.20.2) on Suse

# cat /etc/SuSE-release
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 3

It seems it is an issue open since 2011, how it is possible that Suse devs do not report it and fix it? They build Perl on Suse, right? Why they did not contribute back?

I found here the solution: by the way, I do not know how to write an XS, but, I could solve it as the comment?showComment=1360600273455#c3636290794182954084 say: by opening the file ODBM_File.xs at line 128 and adding "db" to the dbmclose function.

A quick 'n useful git tip:

$ git config --global alias.stashed "stash list --pretty=format:'%gd: %Cred%h%Creset %Cgreen[%ar]%Creset %s'"
$ git stashed
stash@{0}: 2d7f38b [19 minutes ago] On variable-travel-times-207: variable station travel times
stash@{1}: 1e4207e [6 weeks ago] WIP on custom-mission-actions-30-2: a00a646 Don't show intelligence since we're not using it.

Typically, git stash just shows you the items in your stash. Now, git stashed shows you how long ago an items was stashed (I had no idea I had a 6 week old stash item) and colorizes the relevant bits to make it easy to read (admittedly not visible in the bit above).

I uploaded File::Finder to the CPAN more than a decade ago. I was using it for a project today, and found a bug that has been in there in the beginning. I forgot to localize $_ in ->contains, which clobbered File::Find's $_, used by just about everything else.

I couldn't even remember where I had put the git repo for the distro source, and once I found that, I couldn't remember how to build and test modules.

I'm getting old.

If you're having trouble logging in here, try this link rather than the one above.

See also github issue #294

I just released 0.30_1 of Net::Amazon::EC2 to CPAN. This test release contains support for AWS4 signatures. It is based on a pseudonymous patch on this RT ticket but I reworked it to support both v2 and v4 signatures because I know some of the people who use this module connect with Eucalyptus or other AWS-compatible-ish APIs which may not fully support v4 yet.

So if you've been itching to get stuff done with EC2 in the eu-central-1 region (which AFAIK only accepts v4 requests), please give this test release a spin. I plan to release it as 0.31 after a couple of weeks if no show stopper(s) pop up.

Right between YAPC::Asia (Tokio, 20-22 Aug) and YAPC::EU (Granada, 2-4 Sept) you have the opportunity to attend another Perl event, the Swiss Perl Workshop 2015.

Day One
Thursday, 27 August
Perl 6 Hackathon
(Plus Dinner for Hackers)

Day Two
Friday, 28 August
Keynotes and Talks, Perl 6 Hackathon
(Plus Attendees' Dinner)

Day Three
Saturday, 29 August 2015
Workshops, Perl 6 Hackathon
(Plus "Cleaning the House Party")

Buy your ticket soon.

Also attending: Larry and some celebrities from the Perl6 core team. More to be announced soon.

Thank you, sponsors (and yeah, we urgently need more!):

This year I attended my fourth YAPC.  As always, here are my thoughts.  This time around, let’s start with ...

THINGS I LEARNED AT YAPC:

Ever seince I started using a Chromebook I have been interested in the concept of cloud-based IDEs for development. I am disappointed with Codenvy.com's lack of Perl support in their runtime containers and IDE, but it's technically possible to develop Perl apps on their platform.

I recently heard about Koding.com. I signed up and was delighted to discover native Perl support in both their default runtime container and IDE; with support for syntax highlighting and code completion. I cloned an existing Git repository, and I felt almost like I was working in a normal linux environment (albeit, in the cloud from a web browser).

If you don't mind using my referral (free RAM upgrades for me)...
https://koding.com/R/zjtzjt

If you're familiar with Dancer2 (my favorite Perl web framework to date), you know how amazingly easy it is to develop self-describing routes for your web application.

Let's say you have a Dancer2 app that allows your users to manage their phone numbers in a 1:X relationship. You might want to expose a route like...

post '/user/:user_id/phone_numbers/new' => sub {
    my $user_id = param 'user_id';
    # Do some stuff
};

... to add a new number to their profile. Let's also assume you have a route upstream that prohibits users from accessing routes associated with other users:

I attended Perl MiniConf last saturday and learned a great deal. I have had a pause account since the NYC Perl Hackathon 2015 event ( May 2nd 2015 ) and because of this I decided to take brian d foy's "Become a CPAN author in 3 hours" training. It was a very smooth and eye opening experience ( I was expecting a CPAN Module upload to be a bit more complicated).

Here's a list of things I took from brian's training:

Hi everyone,

I recently attended Miniconf in New York at which I decided to host a hackathon for my current hobby project, Mojo::Snoo - a Mojo wrapper for the reddit API.

Some hackathon attendees were nice enough to contribute code and give me some great ideas for future development. So, I’d like to briefly mention some changes introduced in the v0.10 release.

Firstly, let’s get one thing out of the way:

What the #$%! is Snoo?

Snoo is the name of reddit’s alien mascot. You know, the white alien at the top of reddit.com:

Not to be confused with “snu-snu” from Futurama.

According to reddit’s most recent license changes, reddit API wrappers cannot contain the word “reddit”.

Thus, Mojo::Snoo was born.

New features and changes

Moving on - I’d like to summarize some changes made recently and share some quick examples:

• ojo::Snoo

The web conference software that the Perl community uses mostly (Act) has a nice feature that lets registered users to mark their favourite talks. You just have to choose a talk from the list and then add it to your favourites.

This feature has several benefits that may seem obvious but are important anyway:

• It helps you build your personal schedule.
• It helps speakers see the expectation that their talks raise (see The Intersection of Code and Art and Great Tools Heavily Used In Japan, You Don't Know, for instance).
• It helps organizers build the schedule and allocate the right room for each talk.
• And finally it buils a list of the top favourited talks for everyone to see.

Thus, please help make YAPC Europe in Granada a big success and choose your favourite talks. Thanks!

The after-story about the Perl Golf contest, which took place during the two-day YAPC::Russia conferece in Moscow

Perl Golf is a contest, where participants solve the task with the shortest Perl programme possible. This year's Golf rules were announced by Vadim Pushtaev right after the conference start.

You can find a formal desciption and all the received solutions in the YAPC_Russia_2015_perl_golf GitHub repository.

So I just went to investigate switching from perlbrew to plenv.

This has failed before, because I run an old and grungy installation of Perl where I didn’t set up a local lib and just installed whatever without keeping records of which installed modules I need and which are just junk I tried for a few minutes. Unless I carry forward all that junk, I can’t switch perls without breaking all my local scripts – and I have better things to do.

Eventually I want to fix this situation, but no today on which it comes up has been the day for it so far.

Still, I do want to upgrade to 5.22 now that it’s out, and I’ve been wanting to switch to plenv for a while. What to do?

Uhm… *looks around*
ln -s ~/perl5/perlbrew/perls/perl-5.16.1 .plenv/versions/5.16.1
La la la… *walks away*

Yup, plenv global 5.16.1 is fine with that and a plenv rehash later, it works.

I threw out the rest of perlbrew, just kept the directory tree for the linked perl installation, and now I happily run this bastard/cuckoo setup. Teehee.

Now for installing 5.22 and making all my stuff work with it…

Here’s a little trick I’ve been using for a while to help ensure that a large sprawling Catalyst application always generates valid HTML. The idea is to unit test all your templates: the trick is to make it really easy with a helper class: