The effbot is putting The Standard Python Library online.
This is going to be dead handy, even for those of us who have the dead-tree edition. The latter is best for reading on the tube. Or toilet. (Sorry.) But I can't cart all my books everywhere I go. I can carry a CD easily. I have an 'essentials' CD, containing everything I wouldn't want to do without - utilities, Python, Java, IDEs, packages, tools & documentation. The Standard Python Library is going on that.
With luck, putting the electronic version online might boost sales of the dead-tree version, too. It worked for Bruce Eckel.
jEdit is my text-editor-of-choice, and the new version, 4.1, is out.
I've not come across much new in it, but it's very pretty. ;-)
Not that I use it for coding - for that I use Eclipe (2.1 RC2 out recently), and PythonWin. But there are endless other text files to hack on, and jEdit is just perfect. Its XML handling is particulary good.
Use this website to create a PDF file which can be printed and folded to create a paper CD case. Both cool and useful. Bit of a bugger to get the hang of - I found step 5 particularly troublesome. But worth it in the end.
Via DUTCHBINT.ORG.
Welcome to the world of blogging, Kelvin!
A few things. Firstly, get ieSpell installed ASAP. ;-)
Secondly, you don't seem to have set yourself up a blog title - look at IE's title bar, and you'll see what I mean.
Lastly, since Mike Bruce is one of the nicest people I've had the privilege to work with, I can only assume that there was some lapse in communication somewhere along the line. My theory is that the recruitment consultant saw the, uh, the name of our erstwhile employer on your CV, and sent it off to Mike on this basis despite that fact that the job was wrong for you. Rather than admit to this, the recruitment consultant laid the blame at Mike's door. Recruitment consultants are lying bastards, you know.
The one consolation of the shocking state of the IT job market at the moment is that the recruitment consultants have it worse than we do. ;-)
Good luck with the Milton Kenyes thing, by the way.
A couple of days ago, the Movable Type instance that I'm running this blog on started throwing lots of nasty Perl-type error messages whenever I tried to do anything. I had assumed that something was corrupted somewhere.
But today, it sprang into life again. Perhaps my host, 1&1, were mucking about with their Perl installation, or something.
Any road up, now that SVoC is back up again, I'm in much less of a hurry to move away from Movable Type than I was over the last couple of days, but I still think I will. Why? A couple of reasons. Partly, I've been unable to to donate, and I feel a little guilty about using it without paying for it. Only a little, 'cos I've tried to pay for it, but still.
The other reason is that If I use a Python-written OSS blogger, I'll be able to add any functionality that I want, and perhaps fix it if it goes wrong.
Vellum looks nice.