[Python-Dev] Re: RELEASED Python 2.3.1

[Jason R. Mastaler]

Michael Hudson <mwh at python.net> writes:

> I think in future we should probably do the "2.3.2c1", wait a week,
> do "2.3.2" thing.  It's more work, but there have been enough nits
> that I think it would have been worthwhile (readline vs. no threads,
> fsync and the docs issue spring to mind).

Will there be a 2.3.2 release, or some other sort of bugfix release to
address the problems in 2.3.1?  I think the os.fsync() problem is
serious enough to warrant revoking 2.3.1 and making a new release
to replace it rather quickly.