Thomas Wouters wrote:
> It's just too bad that it's an easily overlooked hint, and that you
> can't get that hint when compiling for 32-bit platforms.
That all depends on the compiler, of course. Both MSVC and the Intel
compiler support a /Wp64 flag, which tells you about "questionable"
conversion
Thomas Wouters wrote:
> The webpage should be made, though, if just to refer to in the
> release notes.
the web page does exist:
http://www.python.org/dev/peps/pep-0353/#conversion-guidelines
___
Python-Dev mailing list
Python-Dev@python.org
h
On 4/4/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
Thomas Wouters wrote:> And so I could. test_banana.CananaTestCase.testCrashNegativeLong> crashes, because it calls PyString_AsStringAndSize() with an int-ptr as> second argument (an adjacent ptr variable becomes garbage.) That's
> certainly a
On 4/4/06, Thomas Wouters <[EMAIL PROTECTED]> wrote:
>
>
> On 4/4/06, Jean-Paul Calderone <[EMAIL PROTECTED]> wrote:
> >
> > Of course anyone who is interested can run the Twisted test suite very
> easily and take a look at the failures themselves (if you have Twisted
> installed, "trial twisted" w
Neal Norwitz wrote:
> I don't think so. I think that macro controls Py_BuildValue etc (the
> APIs in modsupport.h) I don't think it controls anything else. So
> what that means is that Py_BuildValue("l") means something different
> depending on ssize_t or not.
Actually, it *only* affects s#, z#
Thomas Wouters wrote:
> And so I could. test_banana.CananaTestCase.testCrashNegativeLong
> crashes, because it calls PyString_AsStringAndSize() with an int-ptr as
> second argument (an adjacent ptr variable becomes garbage.) That's
> certainly a problem with the Py_ssize_t change. Martin, aren't a
On 4/4/06, Thomas Wouters <[EMAIL PROTECTED]> wrote:
>
>
> On 4/4/06, Thomas Wouters <[EMAIL PROTECTED]> wrote:
> >
> >
> > Oh, goodie, a segmentation fault. Let's see if I can reproduce it ;P
>
>
> And so I could.
> test_banana.CananaTestCase.testCrashNegativeLong crashes,
> because it calls PyStr
On 4/4/06, Thomas Wouters <[EMAIL PROTECTED]> wrote:
Oh, goodie, a segmentation fault. Let's see if I can reproduce it ;PAnd so I could. test_banana.CananaTestCase.testCrashNegativeLong crashes, because it calls PyString_AsStringAndSize() with an int-ptr as second argument (an adjacent ptr variabl
On 4/4/06, Jean-Paul Calderone <[EMAIL PROTECTED]> wrote:
Of course anyone who is interested can run the Twisted test suite very easily and take a look at the failures themselves (if you have Twisted installed, "trial twisted" will do it) and can guess which errors/failures are specific to Pyth
On 4/4/06, Jean-Paul Calderone <[EMAIL PROTECTED]> wrote:
This apparently was due to a change in the behavior of __import__: in Python 2.4, __import__('') raises a ValueError; in Python 2.5, it returns None.Oops, that wasn't intended. I seem to recall seeing that before, and I thought I'd fixed it,
Jean-Paul Calderone wrote:
> Once I do have time to track down specifics, I'll file tickets as
> appropriate. For now I just wanted to point out the one detail I
> have tracked down, and give a heads up that there are likely some
> more to come.
>
> Of course anyone who is interested can run the
I tried out Twisted's test suite with a version of Python built from SVN trunk
today and ran into a few problems. First, the test suite hung indefinitely
using all available CPU time. This apparently was due to a change in the
behavior of __import__: in Python 2.4, __import__('') raises a Valu
12 matches
Mail list logo
