We all know that Python, Perl and Ruby (ok, and PHP, and probably other languages) are always stealing ideas from one another. This is a nice thing to do.
After programming a few with Python there is a couple of details I like. I know not all are possible to implement in Perl. Some of them are, and I would love if they were. I know not all people agree with me (that good, too). Nevertheless, I present here a couple of ideas.
Although I do not like relying only in indentation for blocks, I like the fact that conditionals and loops does not need parenthesis. It makes the code much more legible. I imagine that to make this in Perl it would be crazy. Good enough we don't need them when using it as a modifier.
The Spouse’s Program begins tomorrow morning. Those of you participating should come to the opening ceremonies at 9am at the Lowell Center, where I’ll introduce you to our Spouse’s Program organizer, Julia. Dress casually and in comfortable shoes.
Tomorrow you’ll be taking tours of the State Capitol, Camp Randall Stadium, and of Wollersheim Winery. Later in the week you’ll be visiting the Chazen Museum of Art, going sailing, participating in a craft workshop, and taking a guided tour of State Street (a shopping/restaurant district).
To better fit CPAN's naming conventions, Reddit::API has been renamed to Reddit::Client. As there are no dependencies in the reverse lookup graph, Reddit::API is scheduled for deletion.
Reddit::Client begins its life at 0.02 with mostly complete unit tests (thanks for the footnote, Gabor), some refactoring, and a few bug fixes. Enjoy!
Since YAPC::Asia Tokyo 2010, we have been hosting voting on "Best Talk Award" for talks that go on YAPC::Asia Tokyo. We are also giving away prizes for the winners of these awards -- for 2010, we gave a Macbook Pro with all the bells and whistles, and last year we gave a dandy ergonomic chair.
This award was originally created in hopes that giving talks at YAPC::Asia Tokyo will also also be rewarding for the attendees, and also to give them some incentive to learn more, to do more. We believe that giving them a chance to attend these conferences will be an extremely cool opportunity to mingle with people who otherwise they may never meet in person, and to feel what it's like in other conferences.
Of course, we are assuming that a Japanese local would get the award, but if somebody living abroad gets this award, we'll try to arrange something. Do visit us if you're interested!
Because of how Log::Log4perl was built, you don't need to do anything special in your code to support this multi-level priority logging -- each package can just use Log::Log4perl->get_logger() to get the the logging object and it all falls out in the wash.
(In theory, this type of configuration should work for Log4j and Log4net also.)
YAPC::NA isn’t just about the main conference programme - there’s often things that get organised on the fly by attendees because somebody comes up with an idea, or because they want to try somewhere new for lunch. In order to make sure you don’t miss out - and to find out if somebody has found the power cable you accidentally left in the lobby - it’s worth keeping in touch. To do that, there are two key resources - 1) The mailing list: http://mail.pm.org/mailman/listinfo/yapc 2) The IRC channel: #yapc onirc.perl.org(which allowsmibbit.comif you have no client) The mailing list tends to be used for “hey, does anybody fancy doing X later?” ideas, and the IRC channel for “hey, does anybody fancy doing X right now?” but that’s more down to the technology than any enforcement. These will help you get the most out of your YAPC - and to find the people involved inhttp://act.yapcna.org/2012/wiki?node=HallwayPlusPlus if you’re wanting to met new people while you’re here too!
As far as I know, the YEF did receive neither a Letter of Intent nor a proper proposal for hosting YAPC::Europe 2013 yet (and I should know, as I'm on the Venue Committee)
The deadline for submitting a proposal is Thursday, 5 July.
So if you and your group are thinking about hosting next years YAPC, we would very much appreciate it if you'd send a short note (or a full-fledged proposal) to venue@yapceurope.org.
It's really not much work, and all reports from previous organizers stating otherwise are grossly exaggerated!
Here's the whole Call for Venue, and here is a detailed document on what to do to bring YAPC::Europe 2013 to your wonderful hometown. And for even more organizers know-how, check out Perl Jam an upcoming book about "How to organise a conference ... and live to tell the tale." by barbie et.al. (also available on github)
As a part of that work I have updated cpancover and moved it to a new home at http://cpancover.com.
cpancover is my project to provide coverage details for CPAN modules. Whilst useful in its own right, I also tend to use CPAN as my extended test suite for Devel::Cover. I was able to procure a server in the beta phase of http://bigv.io from the nice folk at http://bytemark.co.uk and I decided it was time for cpancover to have its own domain name.
The subway, tram lines and bus
run from 6:00 am through 1:00 am. Connections
are best looked up on the RMV website . The Frankfurt
public transport relies on the "honour system" ).
You are expected to buy the ticket
before you board the train. For buying a simple
ticket
there are "hotkeys" on the machine for "inner city"
and "airport". A single trip within the inner city
costs €2,50 per person. The trip from the
airport into the city costs €4,10.
The "Nachtbus"
(night bus) runs every 30 minutes from midnight to
four in the morning. The central hub for the Nachtbus
is the Konstablerwache where all lines meet up at the same
time to allow for switching. The "n1" and "n2" lines connect the
venue to the Konstablerwache.
Taxi fares
are somewhat expensive, at €1,65/€1,75 per km, plus €2,75/€3,25
fee for day/night. The transfer from the airport
to the venue costs about €20, to the train station about €30.
Cabs are generally safe in Frankfurt except that the driver
may try to drive a longer route if they notice you're not from
around the town.
Well, I’m just about done with my porting project. For $work, we’ve been working on porting a fairly large codebase (the official count is nearly 2 million LOCs, although I think that probably includes whitespace and comments) from Perl 5.8.9 to 5.14.2. Actually, our goal is threefold:
Get our code using the newest Perl. (Although, of course, that’s always a moving target: by this point 5.16 is out, so it’s not the newest any more.)
Get our code using the newest Moose. (We’re currently on 1.21, and want to go to 2.x.)
Switch from using MooseX::Method::Signatures to using Method::Signatures::Modifiers. In fact, this port was the primary impetus for me writing MSM in the first place (although, back then it was Perl 5.12 we were aiming at). Now, in a bizarre sort of paradoxerie, the desire to get away from MXMS is the driving force behind completing the port.
Why anyone would want to spider CPANdeps is beyond me, but a load of idiots in the Ukraine do want to, and their bot, as well as ignoring robots.txt (just like all the other search engines in the entire world, it seems) sends requests as fast as it can. All the timeouts and the errors about CPANdeps running out of database connections must mean they get some really high quality data.
All fixed though:
/sbin/iptables -A INPUT -s 213.186.96.0/19 -j DROP
/sbin/iptables -A INPUT -s 212.113.32.0/19 -j DROP
If this inconveniences any Ukrainian perl hackers, then I apologise. You should address your complaints to the employees of ahrefs.com, preferably attached to baseball bats, knives and guns.
I've been opening quite a few bugs lately for distributions failing these 2 criteria, so, I figured I'd save everyone some effort and unify it cohesively.
Reason
While it may seem a trivial squabble, ABSTRACT and LICENSE components of your meta-data are reasonably important for communicating what your dist is to the world, for both human and automated consumers.
The ABSTRACT field manifests itself in quite a few places:
Do you remember when I stood up in front of the entire audience at YAPC::NA 2011 and told the whole room that I was going to post a blog entry about YAPC every single day between YAPC::NA 2011 and 2012? And the whole crowd broke out into laughter? Heh. Yeah that was funny, but I made it! Now you know that when I tell you I’m going to do something, it gets done! Woot!
Seriously though, thank you for laughing. It strengthened my resolve and pushed me to follow through with the claim. Also, thank you for choosing me and the MadMongers to run YAPC::NA 2012. We’ve had an absolute blast planning it.
In other news, YAPC::NA 2012 starts tomorrow! Holy cow being eaten by a raptor! I can’t believe it’s finally here. Can’t wait to see you all tomorrow. Safe travels.
So I think it was an interesting experience, and I wish more people did this kind of thing.
Because author can't enter the same river twice; once you're familiar with your project's concepts, you tend to lose the perspective on what will confuse a new user.
You don't have to be a good writer or an experienced developer to provide this kind of feedback. On the contrary, seeing the docs for the first time is what's important to make this process work.
And the author probably won't blame you for being unreasonable -- how can he if you're admitting that you don't understand what's going on and you're just dumping your thought process?