Mailman 3 September 2002 - SciPy-Dev

Re: [wxPython] RE: [SciPy-dev] Announce: First installable version of Chaco plotting toolkit is now available
by Robin Dunn Sept. 23, 2002

Sept. 23, 2002

Skip Montanaro wrote: > > Skip> I poked around for "__ti7wxEvent". All I found were a couple undefined > Skip> references: > Skip> ./wxPython/build/temp.linux-i686-2.3/helpers.o > Skip> U __ti7wxEvent > Skip> ./wxPython/build/temp.linux-i686-2.3/dynamicsash.o > Skip> U __ti7wxEvent > > Robin> I've just tried exactly what you did above on my Mandrake 8.2 > Robin> system with Python 2.2 and it works fine. > > What file defines wxEvent? You must surely have a .o file which defines it > as an exportable symbol. It should be in wxGTK in src/common/event.cpp (build/event.o). > Robin> One possibility -- since the wxPython build gets its compiler > Robin> flags and etc. from Python's build via distutils -- is that there > Robin> is some flag conflicting with wxGTK's build that has changed with > Robin> Python 2.3. I'd be interested in seeing a copy of a compile > Robin> commandline for one of the sources from the wxGTK build and > Robin> another one from the wxPython build. > > An example from (wxPython's internal) wxGTK with the no_rtti and > no_exceptions flags set: [...] These look okay. > Robin> Another possibility is that it may be fixed simply by disabling > Robin> rtti and/or exceptions in the wxGTK build. You can try adding > Robin> the following flags and then rebuilding all of wxGTK and > Robin> wxPython: > > Robin> --enable-no_rtti > Robin> --enable-no_exceptions > > Just tried that. Running wxPython/demo/demo.py now yields: > > Traceback (most recent call last): > File "demo.py", line 3, in ? > import Main > File "Main.py", line 15, in ? > from wxPython.wx import * > File "/usr/local/lib/python2.3/site-packages/wxPython/__init__.py", line 20, in ? > import wxc > ImportError: /usr/local/lib/python2.3/site-packages/wxPython/wxc.so: > undefined symbol: Eof__C13wxInputStream > > which c++filt reports as > > wxInputStream::Eof(void) const > > The original __ti7wxEvent symbol is no longer to be found anywhere (defined > or referenced). Right, it shouldn't be since you built without RTTI. > Eof__C13wxInputStream is referenced from > ./wxPython/build/temp.linux-i686-2.3/helpers.o. I don't see anyway that a whole method could get lost... > > Ah, wait a minute. I see a likely candidate for the screwup: > > % type c++ > c++ is /usr/local/bin/c++ > % c++ --version > 3.0.4 > % type gcc > gcc is /usr/bin/gcc > % gcc --version > 2.96 > > Does mix-n-match across GCC versions strike you as a plausible reason for > the errors? ...except for this. It's likely that the C++ symbol names are getting mangled differently by the different compiler versions and the one symbol reported by the import exception is just the first one found. -- Robin Dunn Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!

2 1

Announce: First installable version of Chaco plotting toolkit is now available
by David C. Morrill Sept. 23, 2002

Sept. 23, 2002

We are pleased to announce that the first installable version of the Chaco plotting toolkit is now available for download at: http://www.scipy.org/site_content/chaco This package includes both the low-level Kiva drawing API as well as the high-level Chaco plotting toolkit (and demo). Its very early code with lots of features still missing; but it does work and there is a lot of function already available, so we would encourage anyone who has an interest to give it a try. We are now in the process of setting up an issue tracking system for Chaco. Anyone having trouble accessing or using the system should in the meantime feel free to use the scipy-chaco(a)scipy.org mailing list to report problems, make comments, request features, etc. Enjoy!

7 11

refcount strangeness when testing weave
by eric jones Sept. 22, 2002

Sept. 22, 2002

I've made some modifications to the SCXX library to beautify code written in C++ and also to improve speed in some cases. I started adding unit tests that exercised some of this stuff and ran into an issue testing refcounts right off the bat. Testing that refcounts are handled correctly for a list passed into a weave function (that does absolutely nothing) gives me the expected results from the command line in the global namespace. >>> import weave >>> import sys >>> a = [] >>> print sys.getrefcount(a) 2 >>> weave.inline('',['a']) >>> print sys.getrefcount(a) 2 However, when doing the same in a function, I get different behavior: >>> def bub(): ... a=[] ... print sys.getrefcount(a) ... weave.inline('',['a']) ... print sys.getrefcount(a) ... weave.inline('',['a']) ... print sys.getrefcount(a) ... >>> bub() 2 3 3 After the first call to weave, it looks like a reference count that shouldn't be added to 'a' gets added. However, running the weave call again doesn't leak a ref count. Based, on this and the original command line result, I'm pretty sure refcounts are handled correctly. Can someone explain what is happening here that is causing the refcount to rise to 3 on the first call in bub() so that I can right accurate tests for weave and ref counts? Thanks, eric

1 0

Broken link in www.scipy.org
by Roy at SEVENtwentyfour Inc. Sept. 22, 2002

Sept. 22, 2002

There appears to be a problem on this page of your site. On page http://www.scipy.org/site_content/weave/tutorial.html when you click on "here", the link to http://www.scipy.org/weave gives the error: Not found. As recommended by the Robot Guidelines, this email is to explain our robots activities and to let you know about one of the broken links we encountered. LinkWalker does not store or publish the content of your pages, but rather uses the link information to update our map of the World Wide Web. Are these reports helpful? I'd love some feedback. If you prefer not to receive these occasional error notices please let me know. Roy Bryant ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Roy Bryant, roybryant(a)seventwentyfour.com President SEVENtwentyfour Inc. ("Always watching the Web") http://www.seventwentyfour.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

Compare Cons�rcio de Im�veis x SFH
by ademilar＠brturbo.com Sept. 22, 2002

Sept. 22, 2002

1. CONS�RCIO ADEMILAR x SISTEMA FINANCEIRO DE HABITA��O -------------------------------------------------------------------------- | | CONS�RCIO | SFH (1) | CONS�RCIO | SFH (1) | | | ADEMILAR | | ADEMILAR | | -------------------------------------------------------------------------- | Valor do |R$ 50.000,00 | R$ 50.000,00 |R$ 50.000,00 | R$ 50.000,00 | | Cr�dito | | | | | -------------------------------------------------------------------------- | N�mero de | 100 | 100 | 180 | 180 | | Parcelas | Meses | Meses | Meses | Meses | -------------------------------------------------------------------------- | Presta��o | R$ 567,50 | R$ 1.125,00 | R$ 354,25 | R$ 755,86 | | | | | | | -------------------------------------------------------------------------- | Valor Total |R$ 57.650,00 | R$ 112.500,00 |R$ 63.765,00 | R$ 136.054,80 | | Saldo Devedor| | | | | | (2) | | | | | -------------------------------------------------------------------------- | Percentual do| 15,30 % | 125,00 % | 27,53 % | 172,10 % | | saldo devedor| | | | | | sobre cr�dito| | | | | -------------------------------------------------------------------------- | Corre��o | CUB Mensal | TR + | CUB Mensal | TR + | | | (3) | 1% / M�s (4) | (3) | 1% / M�s (4) | -------------------------------------------------------------------------- Observa��o: Os n�meros e valores deste demonstrativo s�o apenas um exemplo. (1) Caixa Econ�mica Federal, (2) Com base no valor da 1a. presta��o, antes da corre��o de cada alternativa (3) Varia��o mensal utilizada pelo cons�rcio, (4) Varia��o utilizada pela CEF 2. CONS�RCIO ADEMILAR a) A Ademilar se destaca no mercado por sua atua��o pioneira no Estado do Paran�, especialista no segmento de cons�rcio imobili�rio com o prop�sito de oferecer a melhor das alternativas ao mercado imobili�rio; b) Foi a primeira no Pa�s a obter autoriza��o junto ao Banco Central do Brasil para desenvolver suas atividades em regime de empresa Sociedade An�nima, com Certificado de Autoriza��o n� 92060028; c) Esta em as cinco maiores administradoras de cons�rcio de im�veis do Brasil e conta com a confian�a de mais de 3.000 fam�lias que receberam seus im�veis, num total de mais de R$ 100.000.000,00 em cr�ditos entregues. 3. VANTAGENS DO CONS�RCIO ADEMILAR a) Aquisi��o de im�veis Residenciais ou Comerciais (novos ou usados), Terrenos, Constru��o, Reforma e Amplia��o (im�vel pr�prio), na Cidade, Praia e Campo; b) Equipar ou modernizar a sua micro-empresa, escrit�rio ou consult�rio (im�vel pr�prio); c) Utilizar o FGTS como lance (Conforme normas da CEF); d) Quitar d�vida junto ao Sistema Financeiro de Habita��o; e) Sem necessidade de comprova��o de renda; f) Liberdade para aquisi��o de um ou mais cr�ditos mesmo possuindo outro im�vel, seja quitado ou financiado; g) As contempla��es s�o mensais, uma por Sorteio pela Loteria Federal e outra por Lance; h) Possu�mos v�rias cartas de Cr�ditos com prazos diversos adequando ao seu or�amento familiar. 4. VANTAGENS DO INVESTIMENTO EM IM�VEIS a) "Dinheiro na m�o � vendaval", j� cantava Paulinho da Viola. O im�vel imp�e excelente disciplina de poupar ao investidor; b) Os alugu�is podem oferecer um bom complemento na aposentadoria. Reinvestir os alugu�is recebidos atrav�s do cons�rcio impulsiona novas aquisi��es e torna-se uma alternativa �s aplica��es financeiras; c) �tima prote��o contra a infla��o no m�dio e longo prazo; d) Viver no que � seu � algo que d� muito prazer; e) Comprar um im�vel proporciona uma sensa��o de vit�ria e tranq�ilidade para voc� e sua fam�lia. 5. CONTATO Marisa Gasparim Rosa Assessora Comercial ademilar(a)brturbo.com www.ademilar.brturbo.com (41) 353-2850 / (41) 9994-6590 Curitiba - Paran�

1 0

zeta domain error?
by Skip Montanaro Sept. 20, 2002

Sept. 20, 2002

I'm trying to narrow down the source of a Python core dump during scipy.test() under Solaris 8. When I import scipy I get /home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/scipy/linalg/lapack.py:24: UserWarning: exceptions.ImportError: No module named clapack warnings.warn(clapack.__doc__) exceptions.ImportError: No module named cblas zeta domain error I assume the cblas bit is due to not having atlas available. What is "zeta domain error"? Should it bother me? Skip

2 1

core dump during weave tests on Solaris
by Skip Montanaro Sept. 20, 2002

Sept. 20, 2002

I'm now getting a Python core dump on Solaris if I run scipy.test(5). Running scipy.test(1) succeeds though still with a failure in test_shapiro. Here's the output of scipy.weave.test(): creating test suite for: weave.ast_tools creating test suite for: weave.standard_array_spec No test suite found for weave.accelerate_tools No test suite found for weave.base_info No test suite found for weave.base_spec No test suite found for weave.blitz_spec creating test suite for: weave.blitz_tools creating test suite for: weave.build_tools No test suite found for weave.bytecodecompiler creating test suite for: weave.c_spec creating test suite for: weave.catalog No test suite found for weave.common_info No test suite found for weave.converters No test suite found for weave.dumb_shelve No test suite found for weave.dumbdbm_patched creating test suite for: weave.ext_tools building extensions here: /home/skip/.python21_compiled/146290 building extensions here: /home/skip/.python21_compiled/146291 creating test suite for: weave.inline_tools creating test suite for: weave.size_check creating test suite for: weave.slice_handler No test suite found for weave.vtk_spec No test suite found for weave.wx_spec ...... Expression: result[1:-1,1:-1] = (b[1:-1,1:-1] + b[2:,1:-1] + b[:-2,1:-1]+ b[1:-1,2:] + b[1:-1,:-2]) / 5. Run: (10, 10) f "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/tinyvec.h", line 488: Error: Unable to parse field declaration in class template: skipping field. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 279: Where: While specializing "blitz::GeneralArrayStorage<1>". "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 279: Where: Specialized in non-template code. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 237: Error: The type "blitz::TinyVector<int, 1>" is incomplete. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 279: Where: While specializing "blitz::GeneralArrayStorage<1>". "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 279: Where: Specialized in non-template code. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/tinyvec.h", line 488: Error: Unable to parse field declaration in class template: skipping field. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 279: Where: While specializing "blitz::GeneralArrayStorage<1>". "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 279: Where: Specialized in non-template code. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 238: Error: The type "blitz::TinyVector<bool, 1>" is incomplete. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 279: Where: While specializing "blitz::GeneralArrayStorage<1>". "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 279: Where: Specialized in non-template code. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/tinyvec.h", line 488: Error: Unable to parse field declaration in class template: skipping field. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 279: Where: While specializing "blitz::GeneralArrayStorage<1>". "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 279: Where: Specialized in non-template code. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 239: Error: The type "blitz::TinyVector<int, 1>" is incomplete. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 279: Where: While specializing "blitz::GeneralArrayStorage<1>". "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 279: Where: Specialized in non-template code. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 254: Error: blitz::GeneralArrayStorage<1>::ordering_ is not accessible from blitz::FortranArray<1>. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 279: Where: While specializing "blitz::FortranArray<1>". "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 279: Where: Specialized in non-template code. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 255: Error: blitz::GeneralArrayStorage<1>::ascendingFlag_ is not accessible from blitz::FortranArray<1>. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 279: Where: While specializing "blitz::FortranArray<1>". "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 279: Where: Specialized in non-template code. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 256: Error: blitz::GeneralArrayStorage<1>::base_ is not accessible from blitz::FortranArray<1>. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 279: Where: While specializing "blitz::FortranArray<1>". "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 279: Where: Specialized in non-template code. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/tinyvec.h", line 488: Error: Unable to parse field declaration in class template: skipping field. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/tinyvec.h", line 488: Error: Unable to parse field declaration in class template: skipping field. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/tinyvec.h", line 488: Error: Unable to parse field declaration in class template: skipping field. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/tinyvec.h", line 488: Error: Unable to parse field declaration in class template: skipping field. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/tinyvec.h", line 488: Error: Unable to parse field declaration in class template: skipping field. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/tinyvec.h", line 488: Error: Unable to parse field declaration in class template: skipping field. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/tinyvec.h", line 488: Error: Unable to parse field declaration in class template: skipping field. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/tinyvec.h", line 488: Error: Unable to parse field declaration in class template: skipping field. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/tinyvec.h", line 488: Error: Unable to parse field declaration in class template: skipping field. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/tinyvec.h", line 488: Error: Unable to parse field declaration in class template: skipping field. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/tinyvec.h", line 488: Error: Unable to parse field declaration in class template: skipping field. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/tinyvec.h", line 488: Error: Unable to parse field declaration in class template: skipping field. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/tinyvec.h", line 488: Error: Unable to parse field declaration in class template: skipping field. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/tinyvec.h", line 488: Error: Unable to parse field declaration in class template: skipping field. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/tinyvec.h", line 488: Error: Unable to parse field declaration in class template: skipping field. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/tinyvec.h", line 488: Error: Unable to parse field declaration in class template: skipping field. "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 282: Where: While specializing "blitz::GeneralArrayStorage<2>". "/home/skip/tmp/sunos5/2.1/lib/python2.1/site-packages/weave/blitz-20001213/blitz/array/storage.h", line 282: Where: Specialized in non-template code. Compilation aborted, too many Error messages. Ewarning: specified build_dir '_bad_path_' does not exist or is not writable. Trying default locations ...warning: specified build_dir '..' does not exist or is not writable. Trying default locations .warning: specified build_dir '_bad_path_' does not exist or is not writable. Trying default locations ...warning: specified build_dir '..' does not exist or is not writable. Trying default locations ...Abort (core dumped) and here's a gdb backtrace (currently without symbols - let me know if you need me to recompile with -g): #0 0xff259b0c in __sigprocmask () from /usr/lib/libthread.so.1 #1 0xff24e544 in _resetsig () from /usr/lib/libthread.so.1 #2 0xff24dc34 in _sigon () from /usr/lib/libthread.so.1 #3 0xff250da8 in _thrp_kill () from /usr/lib/libthread.so.1 #4 0xfef4ae68 in raise () from /usr/lib/libc.so.1 #5 0xfef35644 in abort () from /usr/lib/libc.so.1 #6 0xff1d466c in __1cH__CimplMex_terminate6F_v_ () from /usr/lib/libCrun.so.1 #7 0xff1d59ac in __1cG__CrunIex_throw6Fpvpkn0AQstatic_type_info_pF1_v_v_ () from /usr/lib/libCrun.so.1 #8 0xfd4d2fd0 in __1cLthrow_error6FpnH_object_pkc_v_ () from /home/skip/.python21_compiled/sc_d41d8cd98f00b204e9800998ecf8427e0.so #9 0xfd4d31cc in __1cZhandle_variable_not_found6Fpc_v_ () from /home/skip/.python21_compiled/sc_d41d8cd98f00b204e9800998ecf8427e0.so #10 0xfd4d3214 in __1cMget_variable6FpcpnH_object_2_2_ () from /home/skip/.python21_compiled/sc_d41d8cd98f00b204e9800998ecf8427e0.so #11 0xfd4d32cc in __1cNcompiled_func6FpnH_object_1_1_ () from /home/skip/.python21_compiled/sc_d41d8cd98f00b204e9800998ecf8427e0.so #12 0x23c88 in call_object () #13 0x23a54 in PyEval_CallObjectWithKeywords () #14 0x7b6a4 in builtin_apply () #15 0x21bfc in eval_code2 () #16 0x242bc in fast_function () #17 0x21d4c in eval_code2 () #18 0x242bc in fast_function () #19 0x21d4c in eval_code2 () #20 0x24184 in call_eval_code2 () #21 0x23c58 in call_object () #22 0x2400c in call_method () #23 0x23c28 in call_object () #24 0x23e90 in call_instance () #25 0x23ce8 in call_object () #26 0x24660 in do_call () #27 0x21d68 in eval_code2 () #28 0x24184 in call_eval_code2 () #29 0x23c58 in call_object () #30 0x2400c in call_method () #31 0x23c28 in call_object () #32 0x23e90 in call_instance () #33 0x23ce8 in call_object () #34 0x24660 in do_call () #35 0x21d68 in eval_code2 () #36 0x24184 in call_eval_code2 () #37 0x23c58 in call_object () #38 0x2400c in call_method () #39 0x23c28 in call_object () #40 0x23e90 in call_instance () #41 0x23ce8 in call_object () #42 0x24660 in do_call () #43 0x21d68 in eval_code2 () #44 0x24184 in call_eval_code2 () #45 0x23c58 in call_object () #46 0x2400c in call_method () #47 0x23c28 in call_object () #48 0x23e90 in call_instance () #49 0x23ce8 in call_object () #50 0x24660 in do_call () #51 0x21d68 in eval_code2 () #52 0x242bc in fast_function () #53 0x21d4c in eval_code2 () #54 0x242bc in fast_function () #55 0x21d4c in eval_code2 () #56 0x1db1c in PyEval_EvalCode () #57 0x3d258 in run_node () #58 0x3c120 in PyRun_InteractiveOneFlags () #59 0x3bf14 in PyRun_InteractiveLoopFlags () #60 0x3bde4 in PyRun_AnyFileExFlags () #61 0x19e08 in Py_Main () (I tried setting the language to c++ but it still didn't demangle the C++ names.) Skip

1 0

Installing chaco
by Travis Oliphant Sept. 20, 2002

Sept. 20, 2002

I was trying to install Chaco and I get the error. python setup.py install Traceback (most recent call last): File "setup.py", line 102, in ? scipy_base_config = get_package_config( 'scipy_base' ) File "setup.py", line 37, in get_package_config mod = __import__( 'setup_' + name ) ImportError: No module named setup_scipy_base Am I missing something? -Travis O.

3 2

scipy status
by eric jones Sept. 19, 2002

Sept. 19, 2002

Hey group, I have a few days coming up here to work on getting a SciPy 0.2 out the door. It looks like it is buiding and passing all test on windows, and I think it is doing OK on Linux. Sun is close or finished (Skip?). What I'd like to know is if there are any other known issues that we need to solve before pushing 0.2 out? FFT Pearu, how are things on the fft changes? I never heard back from djb on the license issue. I think we are in the clear to use his code, but he also seems to get quite exserised with people who cross him: http://cr.yp.to/distributors.html We are statically linking his code so the comments here about installing it in the correct places doesn't seem to apply -- they look to be aimed at his executables not library files. My vote is to move ahead with using them and then remove them later if he does not like what we are doing. We can back off again to fftpack with the same functionality and also the fftw wrappers are still around for those wanting to use it and not constrained by the GPL. Does this sound like a reasonable plan for 0.2? LINALG How is linalg? This is by far the biggest build headache, but it does seem to be working against atlas on windows and linux and against LAPACK and BLAS on Sun. Any other specific packages that need mentioning? Thanks, eric

3 4

mingw2.0 (gcc 3.2) troubles with weave
by eric jones Sept. 19, 2002

Sept. 19, 2002

Travis V. saw that the new mingw tool set with gcc 3.2 was out for MS windows, so I tried it out with weave. The results aren't that great. The biggest problem is that exception handling is causing seg faults. Dag. This junk again. Exceptions must be really tricky to get right/compatible-with-other-compilers in C++ because it seems to cause weave the most grief. I'm not sure at the moment if it is because I am using an MSVC compiled version of python and then loading gcc 3.2 compiled modules into it, or if it is a more general problem with mingw2.0's exception handling. I will need to compile a mingw version of python to find out (not done and maybe not worth it since 2.95.3 works). The other thing that might be an issue is the dllwrap linker flags in weave. The good news is that blitz is now compatible with gcc3.2. The bad news is, with the current compiler settings, it compiles slower and produces slower code than 2.95.3. Add that 2.95.3 doesn't have the problem with exceptions, and the picture ain't so purty. Here are the timings for gcc 2.95.3 on a median filter for float32: Compile time (sec) 11.8870 Exec time(sec): 0.0800 And gcc 3.2 Compile time (sec): 18.1960 Exec time: 0.0900 While the exec time is not really long enough to be reliable, it has been consistent across runs. Dog. And the night started out so promising... Oh, I would like to here if anyone gets a chance to test the most recent weave (from CVS) against gcc 3.x on Linux. And for other platforms, it should just require a jiggering of the blitz-20001213/blitz/config.h file to reflect your platform (cut and paste from the config-<your-platform>.h file in the same directory). See ya, eric

1 0