I always am amazed by people suggesting that walking in the rain keeps you dryer than
running. Just saw an answer to this. Check it out, it's nice:

I have also seen it debunked experimentally, by MythBusters. But let's try a different approach: intuitive math.
Intuitive math is tricky because it usually is wrong, but hey, it's fun.

Apparently, we all agree that how wet you get correlates to your speed. Otherwise, the question is pointless
because the answer is "walk or run, but take an umbrella", while true, is cheating, right?

So, for those slower-is-better proponents: go and walk very, very, very slowly. You may notice that you end
completely soaked before you finish walking. If you didn't, you are still walking too fast.

On the other hand, if you were to go at 1000000 km/h we all agree you would only get some drops in your frontside,
right? Which would not soak you. Right? And most importantly, is constant regardless of your speed, because
it's just the average amount of water contained in a man-shaped prism from point A to point B, and you get that water
in your front if you go slow anyway.

Assuming the speed/soakiness curve is roughly monotonous, it's clear that the maximum soakiness is when you go
slowest.

If it's not monotonous, then the question is roughly unanswerable, since it would involve there is an optimal speed
and it's worse to go either faster or slower than that, which means the answer is something like "jog" which
is not what you want.

On my free time, lunch hours, and such I have been tweaking Nikola, my static site generator
to make it python 3 friendly. Well, I somewhat-accidentally-my-dog-made-me-do-it may have committed a lot of that into
master.

So, right now, things may be somewhat broken on python2 and somewhat working a little on python3.

My son finished kinder, so they had a special celebration, a graduation ceremony where they
gave the kids a medal, a diploma, they sang a song, that kind of thing. But this school has
a tradition. Parents always give their kids a surprise present at the end of kinder.

In this case, we did a play. With almost every parent acting, singing, playing music, juggling,
and more. My role? Mad scientist. I had 4 lines, I funbled one, but hey, you can't deny I got the
look nailed, man.

Yes, those are blacklight light-up eyeglasses. Yes they are as annoying to everyone else as you would imagine.

A few days ago my son went to a kid's barbershop where they do things like
play Scooby-Doo in a Playstation while they get a haircut. He liked it so much that
he decided to take matters in his own hands. With scissors.

Daddy, I may have cut some hair.

But you know what? Easy problems have easy solutions. And I have a hair clipper.

I have set for myself a priority list of bugs that bother me in rst2pdf, my tool
to convert restructured text into PDFs in order of decreasing shamefulness.

I have been fixing a few today (early morning + late night hack) so the following is now correct:

Use of included stylesheets

Vertical spacing of indented lineblocks

Use of :target: in figure directives

There are 46 open issues but I am not planning on fixing them all.
My personal hitlist has 10 more bugs in it, but regardless of how many I fix, I intend to release anyway, because:

Last release is broken with latest reportlab

Last release is a bit broken with docutils 0.10 which will be out soon

Last release was over six months ago

And that last one is the critical one. Working at Canonical has shown me that release cadence is good.
Specially in a project where trunk is very rarely broken (like rst2pdf) there is no reason for slow
release cycles. Rst2pdf should release monthly.

I fully intend to take that approach, so the next release will be done on December 21st.