Well, the authors of frameworks and libraries still on Python 2 and without having concrete upgrade plans will have to either do something soon or others will take their space.
> the authors of frameworks and libraries still on Python 2 and without having concrete upgrade plans will have to either do something soon or others will take their space.
Pillow (https://github.com/python-imaging/Pillow) is a fork of PIL. If you look at recent commits, you'll see one that claims to make it more Python 3 friendly, but not quite Python 3 compatible because of differences in the C code. So maybe a good opportunity for someone to jump in and fix that.
There is also Wand (http://dahlia.kr/wand/index.html), which, while still alpha, is a very nice ctypes-based, MagickWand API binding. It is also available in pypi, so is easy to install. Support for Python 3 is near-term goal of the project.
There's what claims to be a Python 3 version of the codebase on Christoph Gohlke's Python packages for Windows page (http://www.lfd.uci.edu/~gohlke/pythonlibs/#pil). I haven't tested it.
Until Numpy and Scipy are on Python 3, I'm going to reserve judgement. Python 3 might be here, now, for some things, but there are enough essential libraries out there that aren't, that it's not for most.
Almost all the Python code I've written in the past year has been in Python 3. The libraries you mention have been ported already, as have many other important ones, such as sqlalchemy, lxml, httplib2, and imminently, Django.
Very early on I had plenty of headaches where some library I needed was Python 2.X only, but that's becoming increasingly rare.
Do you know of anything new on PIL (http://www.pythonware.com/products/pil/) ? Or any similar library that might replace it for Python 3?