Eric Smith wrote:
> Eric Smith wrote:
>> Guido van Rossum wrote:
>>> If this is Py3k, perhaps the result should be a PyUnicode instead?
>> Probably so, yes.
>>
>> But I can't reproduce this on a Fedora Core 6 box. I'm compiling under
>> Windows now to see if I can reproduce it there. I'll change
Eric Smith wrote:
> Guido van Rossum wrote:
>> If this is Py3k, perhaps the result should be a PyUnicode instead?
>
> Probably so, yes.
>
> But I can't reproduce this on a Fedora Core 6 box. I'm compiling under
> Windows now to see if I can reproduce it there. I'll change it to
> PyUnicode_Ch
Guido van Rossum wrote:
> If this is Py3k, perhaps the result should be a PyUnicode instead?
Probably so, yes.
But I can't reproduce this on a Fedora Core 6 box. I'm compiling under
Windows now to see if I can reproduce it there. I'll change it to
PyUnicode_Check shortly, even if I can't repr
If this is Py3k, perhaps the result should be a PyUnicode instead?
On Sun, Feb 24, 2008 at 1:19 PM, Eric Smith
<[EMAIL PROTECTED]> wrote:
> Brett Cannon wrote:
> > test_types is triggering an assertion error::
> >
> > Objects/stringlib/string_format.h:497: failed assertion
> > `PyString_Chec
Brett Cannon wrote:
> test_types is triggering an assertion error::
>
> Objects/stringlib/string_format.h:497: failed assertion
> `PyString_Check(result)'
>
> A *really* quick session with gdb would seem to suggest that 'result'
> is actually a str, so I don't know what is going on. Don't have
test_types is triggering an assertion error::
Objects/stringlib/string_format.h:497: failed assertion
`PyString_Check(result)'
A *really* quick session with gdb would seem to suggest that 'result'
is actually a str, so I don't know what is going on. Don't have time
to dig any deeper right now.
