Michael Foord wrote:
> Guido van Rossum wrote:
>> On 7/11/07, Thomas Heller <[EMAIL PROTECTED]> wrote:
>>
>>> Christian Heimes schrieb:
>>>
By the way the ctypes unit tests are causing a segfault on my machine:
test_ctypes
Warning: could not import ctypes.test.test_numbers: u
On 7/11/07, Chris McDonough <[EMAIL PROTECTED]> wrote:
> I have a very remedial question about how to fix test failures due to
> the side effects of string-unicode integration.
>
> The xmlrpc library uses explicit encoding to encode XML tag payloads
> to (almost always) utf8. Tag literals are not
I have a very remedial question about how to fix test failures due to
the side effects of string-unicode integration.
The xmlrpc library uses explicit encoding to encode XML tag payloads
to (almost always) utf8. Tag literals are not encoded.
What would be the best way to mimic this behavior
Guido van Rossum wrote:
> On 7/11/07, Thomas Heller <[EMAIL PROTECTED]> wrote:
>
>> Christian Heimes schrieb:
>>
>>> By the way the ctypes unit tests are causing a segfault on my machine:
>>> test_ctypes
>>> Warning: could not import ctypes.test.test_numbers: unpack requires a
>>> string ar
On 7/11/07, Thomas Heller <[EMAIL PROTECTED]> wrote:
> Christian Heimes schrieb:
> >
> > By the way the ctypes unit tests are causing a segfault on my machine:
> > test_ctypes
> > Warning: could not import ctypes.test.test_numbers: unpack requires a
> > string argument of length 1
> > Segmentation
Christian Heimes schrieb:
>
> By the way the ctypes unit tests are causing a segfault on my machine:
> test_ctypes
> Warning: could not import ctypes.test.test_numbers: unpack requires a
> string argument of length 1
> Segmentation fault
>
> Ubunutu 7.04 on i386 machine with an Intel P3.
I can r
Steven Bethard wrote:
> I'd probably go with something a little more restrictive, maybe:
>
> r'self.assert_\(\S+ == \S+\)'
>
> Something like that ought to have fewer false positives.
Woops! You are right. Even your pattern has caused some false positives
but I've reread the patch and remove
On 7/10/07, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
> > Please help!
>
> I've made a meta patch that makes debugging the bugs a lot easier. It
> replaces assert_(foo == bar) and failUnless(foo == bar) with
> failUnlessEqual(foo, bar). failUnlessEqual shows the value of
Guido van Rossum wrote:
> Please help!
I've made a meta patch that makes debugging the bugs a lot easier. It
replaces assert_(foo == bar) and failUnless(foo == bar) with
failUnlessEqual(foo, bar). failUnlessEqual shows the value of foo and
bar when they are not equal.
http://www.python.org/sf/175
One of the most daunting tasks remaining for Python 3.0a1 (to be
released by the end of August) is fixing the remaining failing unit
tests in the py3k-struni branch
(http://svn.python.org/view/python/branches/py3k-struni/).
This is the branch where I have started the work on the
string/unification
10 matches
Mail list logo
