This is a semi-serious feature request following a brief discussion on #python-dev IRC.

Brett Cannon pointed out on python-checkins list [1] that the names should be alphabetized.  However, given that the names are international, it is not obvious what it means.

I propose to add a comment at the top of Misc/ACKS that the list is maintained in "rough alphabetical order" but not define it any further.

[1] http://mail.python.org/pipermail/python-checkins/2010-May/093650.html

Looks good to me.

LGTM as well.

LGTM :)

Only a few days left for 2.6 ;-)

Committed in release27-maint branch in r83893.  I am not sure this belongs in 2.6 and there is a small practical problem with the merge due to Latin-1 encoding used in the 2.6 version.

I am also not sure whether keeping separate 2.x and 3.x versions serves any useful purpose.

I would like to merge 2.7 and 3.2 lists.   I am about +0.5 on syncing all three versions after that.  If the 2.6 has to stay in Latin-1, I would rather not touch it.

At this point, I am sure that Barry would prefer leaving things alone for 2.6.

I am surprised that there are separate lists. I thought there was just one which distributions grabbed when made.

I suppose that one could claim that someone who only contributes to a branch after it branches off should not be listed for other branches, but in the absence of an automatic addition mechanism and dependence on hand-addition by committers, that does not work so well.

Certainly, Guido's header does not specify 'this release'.

On Mon, Aug 9, 2010 at 2:16 PM, Terry J. Reedy <report@bugs.python.org> wrote:
..
> I am surprised that there are separate lists. I thought there was just one which distributions grabbed when made.

I don't think this is intentional.  More likely committers add
acknowledgments in the same commit as the code changes and they end up
in whatever branch the patch is applied to.   I think this is fine,
but from time to time the list should be merged to avoid svnmerge
annoyances.  Whoever is annoyed by svnmerge (like myself :-) should
resync the lists.

Committed in r83937 (py3k) and r83938 (release31-maint).  The py3k version is now a superset of the lists in the maintenance branches. I don't want to generate any more commit traffic by bringing all branches in sync.  I'll leave it to the next committer who encounters a Misc/ACKS merge conflict which is now unlikely.

I am closing with a link to python-dev discussion that r83893 generated.

http://mail.python.org/pipermail/python-dev/2010-August/102960.html