<div class="gmail_quote">On Tue, Jan 27, 2009 at 3:22 PM, Benjamin Peterson <span dir="ltr"><<a href="mailto:benjamin@python.org">benjamin@python.org</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
At the moment, there are 4 release blockers for 3.0.1. I'd like to see<br>
3.0.1 released soon (within the next month.) It would fix the hugest<br>
mistakes in the initial release most of which have been done committed<br>
since December. I'm sure it would be attractive enough with the nasty<br>
bugs fixed in it! Let's not completely open the flood gates.<br>
<br>
Releasing 3.1 in March or April also sounds good. I will be at least<br>
at the first day of sprints.<br></blockquote></div><br><div><br></div><div>As an interested observer, but not yet user of the 3.x series, I was wondering about progress on restoring io performance and what release those improvements were slated for. This is the major blocker for me to begin porting my non-numpy/scipy dependent code. Much of my current work is in bioinformatics, often dealing with multi-gigabyte datasets, so file io fast is critical. Otherwise, I'll have to live with 2.x for the indefinite future.</div>
<div><br></div><div>Thanks,</div><div>~Kevin</div><div><br></div>