Should there be an announcement that 2.3.2 is forthcoming and hold off on further downloads or distribution of 2.3.1?
-----Original Message----- From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Guido van Rossum Sent: Friday, September 26, 2003 12:40 PM To: Charles Cazabon Cc: email@example.com Subject: Re: [Python-Dev] Re: RELEASED Python 2.3.1
Too late: 2.3.1 is in at least some versions of Debian already -- I'm getting reports on the os.fsync() issue already from my users (it breaks getmail). Could 2.3.1 be revoked or replaced ASAP? "2.3.1b" or similar with only this change would suit me.
That doesn't fit in the numbering scheme, it would have to be 2.3.2. Given the amount of traffic about this I'm tempted to agree that we need to move quickly and issue a fix for this issue (only).
--Guido van Rossum (home page: http://www.python.org/%7Eguido/)
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev