On Thu, May 15, 2014 at 5:49 AM, Jeff Allen <email@example.com> wrote:
Goodness, it's simply raining beta releases these days. It's certainly seems that to have a recent beta out there is creating interest and expectation.
Yes, it feels like we have turned a corner for sure!
I have some fixes for "%f" style formatting I think it would be safe to push. (It looks slightly lop-sided as I'm still cooking integer formatting that will allow a consistent approach.) So I will push it if I have no problems integrating it.
Great! I think this is the right approach if it's straightforward to get the initial version of your code. This should stabilize such tests as test_strtod, right?
As long as there'll be another beta along in a few months there's no need to rush in work that would be better not committed yet.
I'm about to send out a proposed roadmap in a separate email re beta 4 and release candidate 1. You should have the time you need, but this time around, I'm proposing actual dates :)
bytearry.__len__: sorry, I wrote that stuff before I properly understood calls to types sub-classed in Python. I predict more problems, and I've been meaning to revisit more generally.
Concrete examples help us understand abstract problems :)
On the stack overflow message, this seems an entirely reasonable extra clue to offer.
Cool, I will apply Michael's suggested wording change.