In 288640098ea8, Jeremy fixed a bug in distutils2.config that prevented d2’s own setup.py script from working. I had to revert that change because it caused tests to fail. The bug needs to be identified exactly, then a test for it is needed, and finally an sdist should be created to check that all files are included. As I want to release 1.0a4 very soon, I’ll work on this today or tomorrow.
I’ve been using the release blocker priority to mark things that need to be solved for the next d2 alpha release, and by extension before the 3.3 release as the plan was to have d2 in 3.3 (see my recent python-dev email about that). If that interferes with CPython release management feel free to demote them to “high” or tell me if you’d like me to do it.
What's the status of this? I want to release Python 3.4a1 in two days, and this issue is still marked as a "release blocker". Given the age of this issue I doubt anything is going to happen in the next two days. Unless I hear a great wailing and gnashing of teeth I'm going to downgrade this to "high" as Eric suggests.