PyModule_Create() is not documented (or at least it isn't showing up in
the C API index). Might be other parts of the new module initialization
API that are not documented either.

What's the policy for marking bug reports as critical? If the
description of the priority (Might block a future release) is normative,
why got this report marked critical? I don't think a documentation bug
can ever block a release.

I'm not suggesting that this should block a release (if that is the
definition of critical). I do however think this is critical for 3.x's
adoption and therefore should be of much importance to us.

I'm a bit worried about committers giving other committers priorities on
how they should work; as a principle, volunteers are free to work on
whatever they please, in whatever order they please.

So unassigning Georg.

On Fri, Jan 2, 2009 at 11:24 AM, Martin v. Löwis <report@bugs.python.org> wrote:
>
> Martin v. Löwis <martin@v.loewis.de> added the comment:
>
> I'm a bit worried about committers giving other committers priorities on
> how they should work; as a principle, volunteers are free to work on
> whatever they please, in whatever order they please.

Of course.

>
> So unassigning Georg.

It would be really nice if there were some notes on use of the tracker.

> It would be really nice if there were some notes on use of the tracker.

I think Brett has a vision here; you might ping him what the status
of that is.

Attaching a doc patch -- Martin, could you please confirm that I didn't
write nonsense?

The patch looks about right.

I believe it is a bug that md_state isn't automatically freed; m_free
should be used to release any resources stored inside md_state (or any
other resources that the module might hold). So please remove the note
on releasing md_state.

OK, fixed up and committed as r68327.