On 10/6/2011 9:33 PM, Robert Kern wrote:
> On Thu, Oct 6, 2011 at 17:25, Paul Ivanov wrote:
>> Hi Andrea,
>>
>> On Tue, Oct 4, 2011 at 3:04 AM, Andrea Gavana
>> wrote:
>>> Hi All,
>>> I was fiddling here and there with some code doing dynamic import of
>>> stuff, and I noticed that this c
> Still, it shouldn't segfault, and it's worth figuring out why it does.
> gdb has been mostly unenlightening for me since gdb won't let me
> navigate the traceback.
You could try faulthandler, it prints the (python) traceback after a crash:
http://pypi.python.org/pypi/faulthandler/
__
On Thu, Oct 6, 2011 at 17:25, Paul Ivanov wrote:
> Hi Andrea,
>
> On Tue, Oct 4, 2011 at 3:04 AM, Andrea Gavana wrote:
>> Hi All,
>> I was fiddling here and there with some code doing dynamic import of
>> stuff, and I noticed that this code:
>> import os
>> import sys
>> init_name = r"C:\Pyth
Hi Andrea,
On Tue, Oct 4, 2011 at 3:04 AM, Andrea Gavana wrote:
> Hi All,
> I was fiddling here and there with some code doing dynamic import of
> stuff, and I noticed that this code:
> import os
> import sys
> init_name = r"C:\Python27\Lib\site-packages\numpy\__init__.py"
> directory, module
Hi All,
I was fiddling here and there with some code doing dynamic import of
stuff, and I noticed that this code:
import os
import sys
init_name = r"C:\Python27\Lib\site-packages\numpy\__init__.py"
directory, module_name = os.path.split(init_name)
main = os.path.splitext(module_name)[0]
sy
