Eric Smith wrote:
> 2. I'm making the format specifiers as strict as I can. So, I've made
> these ValueError's:
I should have mentioned that I expect there to be criticism of this
decision. I'd like to start with making the specifier parser strict, we
can always loosen it if we find the need
Talin wrote:
> Wow, excellent feedback. I've added your email to the list of reminders
> for the next round of edits.
Here's something else for future edits:
1. When converting a string to an integer, what should the rules be?
Should:
format("0xd", "d")
produce "13", or should it be an error?
On 8/19/07, Brett Cannon <[EMAIL PROTECTED]> wrote:
> On 8/19/07, Neal Norwitz <[EMAIL PROTECTED]> wrote:
> > I just fixed a bug in the new memoryview that used PyObject_DEL which
> > caused a problem in debug mode. I had to change it to a Py_DECREF.
> > It seems we have a lot of spellings of ways
On 8/19/07, Neal Norwitz <[EMAIL PROTECTED]> wrote:
> I just fixed a bug in the new memoryview that used PyObject_DEL which
> caused a problem in debug mode. I had to change it to a Py_DECREF.
> It seems we have a lot of spellings of ways to free an object and I
> wonder if there are more problems
On 8/19/07, Neal Norwitz <[EMAIL PROTECTED]> wrote:
> I just fixed a bug in the new memoryview that used PyObject_DEL which
> caused a problem in debug mode. I had to change it to a Py_DECREF.
> It seems we have a lot of spellings of ways to free an object and I
> wonder if there are more problems
I just fixed a bug in the new memoryview that used PyObject_DEL which
caused a problem in debug mode. I had to change it to a Py_DECREF.
It seems we have a lot of spellings of ways to free an object and I
wonder if there are more problems lurking in there.
$ cat */*.c | grep -c PyObject_Del
103
$
