[Expired for python-numpy (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: python-numpy (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
the script still crashes but differently (in PyArray_Item_INCREF,
numpy/core/src/multiarray/scalarapi.c:332)
This needs to be discussed with the numpy developers, it does not seem
related to the packaging.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Sorry, I don't have the time to test this now. It looks like I attached a
test file and build script long ago, though..
On Sat, Apr 13, 2013 at 6:38 AM, Julian Taylor <
jtaylor.deb...@googlemail.com> wrote:
> can this issue still be reproduced in recent versions of the packaged
> numpy?
>
> ** C
can this issue still be reproduced in recent versions of the packaged
numpy?
** Changed in: python-numpy (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/184
** Changed in: python-numpy (Ubuntu)
Status: Incomplete => Triaged
--
import numpy fails after Py_Finalize in embedded python
https://bugs.launchpad.net/bugs/184920
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
Here's the backtrace again after installing python-numpy-dbg:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffce74876f0 (LWP 12541)]
0x7ffce42f6dbb in PyArray_FromScalar (scalar=, outcode=0x0) at numpy/core/src/scalartypes.inc.src:278
278 numpy/core/src/scal
I've attached two files:
- pythontest.cpp - just initializes python, imports numpy, and
finalizes, then repeats. On my machine (running hardy), the second run
through causes a segfault.
- build - a short script I used to build the executable
Here's the backtrace when I run:
Program received signa
> Unfortunately, the software I'm writing is pretty heavily tied to
> Gutsy right now. If I have time, I'll write a test program and try it
> on Hardy at some point.
We've got ~ a week to get fixes in for Hardy, so please don't wait to
long.
--
import numpy fails after Py_Finalize in embedded p
> is this same behaviour with a recent version in hardy?
Unfortunately, the software I'm writing is pretty heavily tied to
Gutsy right now. If I have time, I'll write a test program and try it
on Hardy at some point.
Q
--
import numpy fails after Py_Finalize in embedded python
https://bugs.lau
The thread is "Dynamic module not initialized properly"
http://projects.scipy.org/pipermail/numpy-discussion/2007-April/026999.html
>From this post:
"...The issue
that I encountered had to do with the "multiarraymodule.c" extension
module. When "numpy" is imported, it imports this module and the
can't find the thread on
http://projects.scipy.org/pipermail/numpy-discussion/2007-April/thread.html
is this same behaviour with a recent version in hardy?
** Changed in: python-numpy (Ubuntu)
Status: New => Incomplete
--
import numpy fails after Py_Finalize in embedded python
https://b
11 matches
Mail list logo
