Martin v. Löwis wrote:
> Ralf Schmitt schrieb:
>> I've been trying to port our software to python 2.5.
>> unfortunately I'm getting constantly hit by segfaults.
>
> I understand it's unfortunate for you, but it is fortunate
> for us that you have been trying to port your application
> before 2.5 w
Ralf Schmitt schrieb:
> I've been trying to port our software to python 2.5.
> unfortunately I'm getting constantly hit by segfaults.
I understand it's unfortunate for you, but it is fortunate
for us that you have been trying to port your application
before 2.5 was released, and reported the bug w
Duncan Booth <[EMAIL PROTECTED]> writes:
> Does Coverity recognise objects on Python's internal pools as deallocated?
Coverity doesn't work on that level; it analyzes source code, and
knows about Python's INCREFs and DECREFs.
> The moral is to regard the reference counting rules as law: no matt
Duncan Booth wrote:
>
>
> The moral is to regard the reference counting rules as law: no matter how
> sure you are that you can cheat, don't or you'll regret it.
>
Or someone else will regret it, just like in this case. :)
- Ralf
___
Python-Dev mai
Thomas Heller <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
>> /* if no docstring given and the getter has one, use that one */
>> if ((doc == NULL || doc == Py_None) && get != NULL &&
>> PyObject_HasAttrString(get, "__doc__")) {
>> if (!(get_doc = PyObject_Ge
> /* if no docstring given and the getter has one, use that one */
> if ((doc == NULL || doc == Py_None) && get != NULL &&
> PyObject_HasAttrString(get, "__doc__")) {
> if (!(get_doc = PyObject_GetAttrString(get, "__doc__")))
> return -1;
>
Ralf Schmitt schrieb:
> Hi all,
>
> I've been trying to port our software to python 2.5.
> unfortunately I'm getting constantly hit by segfaults.
>
> I've boiled it down to the following code:
>
> [EMAIL PROTECTED]:~/bug$ cat t.py
> import array
>
> class Indexer(object):
> maximumForwardS
