You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2007 |
Jan
(4) |
Feb
(7) |
Mar
(1) |
Apr
|
May
(5) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2008 |
Jan
(3) |
Feb
|
Mar
(6) |
Apr
(3) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(11) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
2010 |
Jan
(4) |
Feb
(7) |
Mar
(4) |
Apr
(6) |
May
|
Jun
(5) |
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
2012 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(1) |
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
(3) |
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(1) |
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
2017 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
(1) |
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Roman G. <rom...@gm...> - 2010-03-01 17:21:31
|
Hi Daniel On 01.03.2010, at 15:46, Daniel Wheeler <dan...@gm...> wrote: > On Sun, Feb 28, 2010 at 4:30 PM, Roman Geus <rom...@gm...> > wrote: >> Hello Daniel >> >> I have tested the new Windows installer on a Windows 7 Enterprise >> 32-bit >> system (fresh install) and had no particular problems with it. Did >> you test >> using a 64-bit edition? > > No, it was 32. I haven't tried since you gave me the advice about the > dlls. Maybe put it up on the sourceforge site and see if anyone else > complains. There are still problems in the superlu module in my installer. Those have to probably be sorted out before it can be released. > I seem to recall you built the installer from the latest > version of trunk. We really need a python 2.6 installer for version > 1.1 rather than trunk. Anyway, as you see fit. There were some modifications necessary to make the source compatible with MSVC compilers - since there is no 1.1 branch, I had to work in the trunk. We can look into that when the rest works. > >> However there seems to be an issue with the superlu module: The >> tests fail >> on Windows 7 and also on Windows XP. I'll look into that. > > If I get another chance, I'll give it a shot, but I never seem to make > time to do these sorts of things these days. I know... Regards Roman > > Cheers > > -- > Daniel Wheeler > > --- > --- > --- > --------------------------------------------------------------------- > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Pysparse-developers mailing list > Pys...@li... > https://lists.sourceforge.net/lists/listinfo/pysparse-developers |
From: Daniel W. <dan...@gm...> - 2010-03-01 14:46:15
|
On Sun, Feb 28, 2010 at 4:30 PM, Roman Geus <rom...@gm...> wrote: > Hello Daniel > > I have tested the new Windows installer on a Windows 7 Enterprise 32-bit > system (fresh install) and had no particular problems with it. Did you test > using a 64-bit edition? No, it was 32. I haven't tried since you gave me the advice about the dlls. Maybe put it up on the sourceforge site and see if anyone else complains. I seem to recall you built the installer from the latest version of trunk. We really need a python 2.6 installer for version 1.1 rather than trunk. Anyway, as you see fit. > However there seems to be an issue with the superlu module: The tests fail > on Windows 7 and also on Windows XP. I'll look into that. If I get another chance, I'll give it a shot, but I never seem to make time to do these sorts of things these days. Cheers -- Daniel Wheeler |
From: Roman G. <rom...@gm...> - 2010-02-28 21:30:22
|
Hello Daniel I have tested the new Windows installer on a Windows 7 Enterprise 32-bit system (fresh install) and had no particular problems with it. Did you test using a 64-bit edition? However there seems to be an issue with the superlu module: The tests fail on Windows 7 and also on Windows XP. I'll look into that. Regards, Roman On 11.02.2010 17:25, Daniel Wheeler wrote: > I installed this on Windows 7 virtual machine. When I run "import > pysparse" in the python command prompt, I get the following error > message in a dialogue box "python.exe has stopped working". No idea > what is going on here or why a dialogue box pops up when it's > importing a python script. Any ideas? > > On Sun, Feb 7, 2010 at 12:47 PM, Roman Geus<rom...@gm...> wrote: > >> Hi again >> >> If you are interested in downloading the new Windows installer please >> use the following URL: >> http://hamsel.users.sourceforge.net/pysparse-1.2a1.win32-py2.6.exe >> >> I will delete the installer from the list of public files, so the old >> URL becomes invalid. >> >> Cheers, >> Roman >> >> On 07.02.2010 18:04, Roman Geus wrote: >> >>> Hello Daniel and Dominique >>> >>> Finally I managed to create a Windows installer for Python 2.6 and >>> Numpy 1.4 based on the current svn trunk available at >>> http://ovh.dl.sourceforge.net/project/pysparse/devel/pysparse-1.2a1.win32-py2.6.exe >>> >>> >>> (BTW: there must be a better way to share files between developers...) >>> >>> It was built using VC++ 2008 and ACML. >>> >>> I have commit the necessary code changes and some install documentation. >>> >>> Is anybody willing to test it? >>> >>> Best regards, >>> Roman >>> >>> On 04.02.2010 16:22, Daniel Wheeler wrote: >>> >>>> Good luck Roman. I'm trying to build it on Windows 7 running as a >>>> virtual machine. It took me a day to figure out that I needed to run >>>> the "command line application" as an administrator before it does >>>> anything! >>>> >>>> On Wed, Feb 3, 2010 at 6:01 PM, Roman Geus<rom...@gm...> wrote: >>>> >>>>> Hi >>>>> >>>>> Just an update... >>>>> >>>>> I'm still trying to build pysparse in Windows using VC++ and ACML for >>>>> Python 2.6. Basically it seems to be working now, but only if I link >>>>> ACML dynamically (as DLL), which not suitable for creating an >>>>> installer. >>>>> >>>>> If I link the static ACML I still get dependencies to >>>>> Fortran-related DLLs. >>>>> >>>>> I hope I find a solution soon. >>>>> >>>>> Regards, >>>>> Roman >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> >>>>> The Planet: dedicated and managed hosting, cloud storage, colocation >>>>> Stay online with enterprise data centers and the best network in the >>>>> business >>>>> Choose flexible plans and management services without long-term >>>>> contracts >>>>> Personal 24x7 support from experience hosting pros just a phone call >>>>> away. >>>>> http://p.sf.net/sfu/theplanet-com >>>>> _______________________________________________ >>>>> Pysparse-developers mailing list >>>>> Pys...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/pysparse-developers >>>>> >>>>> >>>> >>>> >>> >> >> ------------------------------------------------------------------------------ >> The Planet: dedicated and managed hosting, cloud storage, colocation >> Stay online with enterprise data centers and the best network in the business >> Choose flexible plans and management services without long-term contracts >> Personal 24x7 support from experience hosting pros just a phone call away. >> http://p.sf.net/sfu/theplanet-com >> _______________________________________________ >> Pysparse-developers mailing list >> Pys...@li... >> https://lists.sourceforge.net/lists/listinfo/pysparse-developers >> >> > > > |
From: Roman G. <rom...@gm...> - 2010-02-11 20:39:30
|
Hi Daniel Thanks for trying. I have only tested it on two Windows XP machines. It could be missing DLLs: The following need to be available: python26.dll (from the Python installation) msvcr90.dll (from the OS) kernel32.dll (from the OS) imagehlp.dll (from the OS) libifcoremd.dll (from pysparse) libmmd.dll (from pysparse) Unfortunately I'm not a Windows expert and I have no Windows7 available for testing. So it could something entirely different. Hopefully the Python modules compiled with mingw will work better. Regards, Roman On 11.02.2010 17:25, Daniel Wheeler wrote: > I installed this on Windows 7 virtual machine. When I run "import > pysparse" in the python command prompt, I get the following error > message in a dialogue box "python.exe has stopped working". No idea > what is going on here or why a dialogue box pops up when it's > importing a python script. Any ideas? > > On Sun, Feb 7, 2010 at 12:47 PM, Roman Geus<rom...@gm...> wrote: > >> Hi again >> >> If you are interested in downloading the new Windows installer please >> use the following URL: >> http://hamsel.users.sourceforge.net/pysparse-1.2a1.win32-py2.6.exe >> >> I will delete the installer from the list of public files, so the old >> URL becomes invalid. >> >> Cheers, >> Roman >> >> On 07.02.2010 18:04, Roman Geus wrote: >> >>> Hello Daniel and Dominique >>> >>> Finally I managed to create a Windows installer for Python 2.6 and >>> Numpy 1.4 based on the current svn trunk available at >>> http://ovh.dl.sourceforge.net/project/pysparse/devel/pysparse-1.2a1.win32-py2.6.exe >>> >>> >>> (BTW: there must be a better way to share files between developers...) >>> >>> It was built using VC++ 2008 and ACML. >>> >>> I have commit the necessary code changes and some install documentation. >>> >>> Is anybody willing to test it? >>> >>> Best regards, >>> Roman >>> >>> On 04.02.2010 16:22, Daniel Wheeler wrote: >>> >>>> Good luck Roman. I'm trying to build it on Windows 7 running as a >>>> virtual machine. It took me a day to figure out that I needed to run >>>> the "command line application" as an administrator before it does >>>> anything! >>>> >>>> On Wed, Feb 3, 2010 at 6:01 PM, Roman Geus<rom...@gm...> wrote: >>>> >>>>> Hi >>>>> >>>>> Just an update... >>>>> >>>>> I'm still trying to build pysparse in Windows using VC++ and ACML for >>>>> Python 2.6. Basically it seems to be working now, but only if I link >>>>> ACML dynamically (as DLL), which not suitable for creating an >>>>> installer. >>>>> >>>>> If I link the static ACML I still get dependencies to >>>>> Fortran-related DLLs. >>>>> >>>>> I hope I find a solution soon. >>>>> >>>>> Regards, >>>>> Roman >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> >>>>> The Planet: dedicated and managed hosting, cloud storage, colocation >>>>> Stay online with enterprise data centers and the best network in the >>>>> business >>>>> Choose flexible plans and management services without long-term >>>>> contracts >>>>> Personal 24x7 support from experience hosting pros just a phone call >>>>> away. >>>>> http://p.sf.net/sfu/theplanet-com >>>>> _______________________________________________ >>>>> Pysparse-developers mailing list >>>>> Pys...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/pysparse-developers >>>>> >>>>> >>>> >>>> >>> >> >> ------------------------------------------------------------------------------ >> The Planet: dedicated and managed hosting, cloud storage, colocation >> Stay online with enterprise data centers and the best network in the business >> Choose flexible plans and management services without long-term contracts >> Personal 24x7 support from experience hosting pros just a phone call away. >> http://p.sf.net/sfu/theplanet-com >> _______________________________________________ >> Pysparse-developers mailing list >> Pys...@li... >> https://lists.sourceforge.net/lists/listinfo/pysparse-developers >> >> > > > |
From: Daniel W. <dan...@gm...> - 2010-02-11 16:25:42
|
I installed this on Windows 7 virtual machine. When I run "import pysparse" in the python command prompt, I get the following error message in a dialogue box "python.exe has stopped working". No idea what is going on here or why a dialogue box pops up when it's importing a python script. Any ideas? On Sun, Feb 7, 2010 at 12:47 PM, Roman Geus <rom...@gm...> wrote: > Hi again > > If you are interested in downloading the new Windows installer please > use the following URL: > http://hamsel.users.sourceforge.net/pysparse-1.2a1.win32-py2.6.exe > > I will delete the installer from the list of public files, so the old > URL becomes invalid. > > Cheers, > Roman > > On 07.02.2010 18:04, Roman Geus wrote: >> Hello Daniel and Dominique >> >> Finally I managed to create a Windows installer for Python 2.6 and >> Numpy 1.4 based on the current svn trunk available at >> http://ovh.dl.sourceforge.net/project/pysparse/devel/pysparse-1.2a1.win32-py2.6.exe >> >> >> (BTW: there must be a better way to share files between developers...) >> >> It was built using VC++ 2008 and ACML. >> >> I have commit the necessary code changes and some install documentation. >> >> Is anybody willing to test it? >> >> Best regards, >> Roman >> >> On 04.02.2010 16:22, Daniel Wheeler wrote: >>> Good luck Roman. I'm trying to build it on Windows 7 running as a >>> virtual machine. It took me a day to figure out that I needed to run >>> the "command line application" as an administrator before it does >>> anything! >>> >>> On Wed, Feb 3, 2010 at 6:01 PM, Roman Geus<rom...@gm...> wrote: >>>> Hi >>>> >>>> Just an update... >>>> >>>> I'm still trying to build pysparse in Windows using VC++ and ACML for >>>> Python 2.6. Basically it seems to be working now, but only if I link >>>> ACML dynamically (as DLL), which not suitable for creating an >>>> installer. >>>> >>>> If I link the static ACML I still get dependencies to >>>> Fortran-related DLLs. >>>> >>>> I hope I find a solution soon. >>>> >>>> Regards, >>>> Roman >>>> >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> >>>> The Planet: dedicated and managed hosting, cloud storage, colocation >>>> Stay online with enterprise data centers and the best network in the >>>> business >>>> Choose flexible plans and management services without long-term >>>> contracts >>>> Personal 24x7 support from experience hosting pros just a phone call >>>> away. >>>> http://p.sf.net/sfu/theplanet-com >>>> _______________________________________________ >>>> Pysparse-developers mailing list >>>> Pys...@li... >>>> https://lists.sourceforge.net/lists/listinfo/pysparse-developers >>>> >>> >>> >> > > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _______________________________________________ > Pysparse-developers mailing list > Pys...@li... > https://lists.sourceforge.net/lists/listinfo/pysparse-developers > -- Daniel Wheeler |
From: Roman G. <rom...@gm...> - 2010-02-07 17:48:04
|
Hi again If you are interested in downloading the new Windows installer please use the following URL: http://hamsel.users.sourceforge.net/pysparse-1.2a1.win32-py2.6.exe I will delete the installer from the list of public files, so the old URL becomes invalid. Cheers, Roman On 07.02.2010 18:04, Roman Geus wrote: > Hello Daniel and Dominique > > Finally I managed to create a Windows installer for Python 2.6 and > Numpy 1.4 based on the current svn trunk available at > http://ovh.dl.sourceforge.net/project/pysparse/devel/pysparse-1.2a1.win32-py2.6.exe > > > (BTW: there must be a better way to share files between developers...) > > It was built using VC++ 2008 and ACML. > > I have commit the necessary code changes and some install documentation. > > Is anybody willing to test it? > > Best regards, > Roman > > On 04.02.2010 16:22, Daniel Wheeler wrote: >> Good luck Roman. I'm trying to build it on Windows 7 running as a >> virtual machine. It took me a day to figure out that I needed to run >> the "command line application" as an administrator before it does >> anything! >> >> On Wed, Feb 3, 2010 at 6:01 PM, Roman Geus<rom...@gm...> wrote: >>> Hi >>> >>> Just an update... >>> >>> I'm still trying to build pysparse in Windows using VC++ and ACML for >>> Python 2.6. Basically it seems to be working now, but only if I link >>> ACML dynamically (as DLL), which not suitable for creating an >>> installer. >>> >>> If I link the static ACML I still get dependencies to >>> Fortran-related DLLs. >>> >>> I hope I find a solution soon. >>> >>> Regards, >>> Roman >>> >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> The Planet: dedicated and managed hosting, cloud storage, colocation >>> Stay online with enterprise data centers and the best network in the >>> business >>> Choose flexible plans and management services without long-term >>> contracts >>> Personal 24x7 support from experience hosting pros just a phone call >>> away. >>> http://p.sf.net/sfu/theplanet-com >>> _______________________________________________ >>> Pysparse-developers mailing list >>> Pys...@li... >>> https://lists.sourceforge.net/lists/listinfo/pysparse-developers >>> >> >> > |
From: Roman G. <rom...@gm...> - 2010-02-07 17:04:32
|
Hello Daniel and Dominique Finally I managed to create a Windows installer for Python 2.6 and Numpy 1.4 based on the current svn trunk available at http://ovh.dl.sourceforge.net/project/pysparse/devel/pysparse-1.2a1.win32-py2.6.exe (BTW: there must be a better way to share files between developers...) It was built using VC++ 2008 and ACML. I have commit the necessary code changes and some install documentation. Is anybody willing to test it? Best regards, Roman On 04.02.2010 16:22, Daniel Wheeler wrote: > Good luck Roman. I'm trying to build it on Windows 7 running as a > virtual machine. It took me a day to figure out that I needed to run > the "command line application" as an administrator before it does > anything! > > On Wed, Feb 3, 2010 at 6:01 PM, Roman Geus<rom...@gm...> wrote: > >> Hi >> >> Just an update... >> >> I'm still trying to build pysparse in Windows using VC++ and ACML for >> Python 2.6. Basically it seems to be working now, but only if I link >> ACML dynamically (as DLL), which not suitable for creating an installer. >> >> If I link the static ACML I still get dependencies to Fortran-related DLLs. >> >> I hope I find a solution soon. >> >> Regards, >> Roman >> >> >> >> >> >> ------------------------------------------------------------------------------ >> The Planet: dedicated and managed hosting, cloud storage, colocation >> Stay online with enterprise data centers and the best network in the business >> Choose flexible plans and management services without long-term contracts >> Personal 24x7 support from experience hosting pros just a phone call away. >> http://p.sf.net/sfu/theplanet-com >> _______________________________________________ >> Pysparse-developers mailing list >> Pys...@li... >> https://lists.sourceforge.net/lists/listinfo/pysparse-developers >> >> > > > |
From: Daniel W. <dan...@gm...> - 2010-02-04 15:22:51
|
Good luck Roman. I'm trying to build it on Windows 7 running as a virtual machine. It took me a day to figure out that I needed to run the "command line application" as an administrator before it does anything! On Wed, Feb 3, 2010 at 6:01 PM, Roman Geus <rom...@gm...> wrote: > Hi > > Just an update... > > I'm still trying to build pysparse in Windows using VC++ and ACML for > Python 2.6. Basically it seems to be working now, but only if I link > ACML dynamically (as DLL), which not suitable for creating an installer. > > If I link the static ACML I still get dependencies to Fortran-related DLLs. > > I hope I find a solution soon. > > Regards, > Roman > > > > > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _______________________________________________ > Pysparse-developers mailing list > Pys...@li... > https://lists.sourceforge.net/lists/listinfo/pysparse-developers > -- Daniel Wheeler |
From: Roman G. <rom...@gm...> - 2010-02-03 23:01:14
|
Hi Just an update... I'm still trying to build pysparse in Windows using VC++ and ACML for Python 2.6. Basically it seems to be working now, but only if I link ACML dynamically (as DLL), which not suitable for creating an installer. If I link the static ACML I still get dependencies to Fortran-related DLLs. I hope I find a solution soon. Regards, Roman |
From: Roman G. <rom...@gm...> - 2010-01-27 22:15:01
|
Hi Daniel Yes, by all means go ahead with pythonxy. I'll try to get a robust Win32 build using Visual C++. I'll let you know if I succeed. Regards, Roman On 27.01.2010 15:59, Daniel Wheeler wrote: > Hi Roman, I have been using pythonxy as the basis for building > pysparse on windows (switched from enthought, which now has a weird > license). I have also been using some very old compiled versions of > blas and artlas that I really should update. I ran into some problems > upgrading pythonxy to the python 2.6 version so haven't been able to > make a release as yet. I recently installed windows 7 in virtualbox > and I hope to do a clean install of the lastest pythonxy ASAP. As far > as visual c++ is concerned, I have never tried it. I suppose it > doesn't matter what the build process is as long as it works, but I > would rather use the open source tools were available. If you would > like to do it, by all means, but I'll try with pythonxy in the mean > time. Cheers. > > On Tue, Jan 26, 2010 at 4:28 PM, Roman Geus<rom...@gm...> wrote: > >> Hello >> >> Triggered by a recent email on the pysparse-users list I tried to >> compile pysparse 1.1 for Windows and Python 2.6. >> >> I used Visual C++ (Express Edition) and the latest ACML for BLAS and >> LAPACK (both are available for free). >> >> Except for the superlu package (which I skipped) only a few changes to >> the source code were necessary (mostly due to the lack of C99 support in >> the MS C compiler) to build the modules. >> >> Unfortunately one of the unit tests in spmatrix_test failed, but >> basically it seemed to work. (Later I saw that the same unit test also >> fails on Linux, so it might be a general problem.) >> >> I have two questions: >> >> Do you know of anybody who has successfully built pysparse using Visual >> C++ recently? >> >> Do you think it would be desirable to be able to build using Visual C++ >> or is build process using MinGW straight-forward and sufficient? >> >> Best regards, >> Roman >> >> ------------------------------------------------------------------------------ >> The Planet: dedicated and managed hosting, cloud storage, colocation >> Stay online with enterprise data centers and the best network in the business >> Choose flexible plans and management services without long-term contracts >> Personal 24x7 support from experience hosting pros just a phone call away. >> http://p.sf.net/sfu/theplanet-com >> _______________________________________________ >> Pysparse-developers mailing list >> Pys...@li... >> https://lists.sourceforge.net/lists/listinfo/pysparse-developers >> >> > > > |
From: Roman G. <rom...@gm...> - 2010-01-27 22:09:33
|
Hi Dominique Thanks for the explanation. Maybe it would be feasible to store off-diagonal elements twice (above and below the diagonal) when extracting a submatrix from a symmetric matrix. Regards, Roman On 27.01.2010 00:42, Dominique Orban wrote: > On Tue, Jan 26, 2010 at 9:28 PM, Roman Geus<rom...@gm...> wrote: > >> Hello >> >> Triggered by a recent email on the pysparse-users list I tried to >> compile pysparse 1.1 for Windows and Python 2.6. >> >> I used Visual C++ (Express Edition) and the latest ACML for BLAS and >> LAPACK (both are available for free). >> >> Except for the superlu package (which I skipped) only a few changes to >> the source code were necessary (mostly due to the lack of C99 support in >> the MS C compiler) to build the modules. >> >> Unfortunately one of the unit tests in spmatrix_test failed, but >> basically it seemed to work. (Later I saw that the same unit test also >> fails on Linux, so it might be a general problem.) >> >> I have two questions: >> >> Do you know of anybody who has successfully built pysparse using Visual >> C++ recently? >> >> Do you think it would be desirable to be able to build using Visual C++ >> or is build process using MinGW straight-forward and sufficient? >> >> Best regards, >> Roman >> > I will let Windows users comment on what would best suit their needs. > In the meantime I commented out the test that fails. The reason is > that when I implemented fancy indexing (which includes slicing), I > decided that taking a slice on a matrix would result by default in a > non-symmetric matrix, even if the original matrix was symmetric. > Clearly, only symmetric slices would yield a symmetric submatrix > (although special cases may occur but would be costly to check for). > Currently, Pysparse doesn't check for symmetric slices. > > |
From: Dominique O. <dom...@gm...> - 2010-01-26 23:42:32
|
On Tue, Jan 26, 2010 at 9:28 PM, Roman Geus <rom...@gm...> wrote: > Hello > > Triggered by a recent email on the pysparse-users list I tried to > compile pysparse 1.1 for Windows and Python 2.6. > > I used Visual C++ (Express Edition) and the latest ACML for BLAS and > LAPACK (both are available for free). > > Except for the superlu package (which I skipped) only a few changes to > the source code were necessary (mostly due to the lack of C99 support in > the MS C compiler) to build the modules. > > Unfortunately one of the unit tests in spmatrix_test failed, but > basically it seemed to work. (Later I saw that the same unit test also > fails on Linux, so it might be a general problem.) > > I have two questions: > > Do you know of anybody who has successfully built pysparse using Visual > C++ recently? > > Do you think it would be desirable to be able to build using Visual C++ > or is build process using MinGW straight-forward and sufficient? > > Best regards, > Roman I will let Windows users comment on what would best suit their needs. In the meantime I commented out the test that fails. The reason is that when I implemented fancy indexing (which includes slicing), I decided that taking a slice on a matrix would result by default in a non-symmetric matrix, even if the original matrix was symmetric. Clearly, only symmetric slices would yield a symmetric submatrix (although special cases may occur but would be costly to check for). Currently, Pysparse doesn't check for symmetric slices. -- Dominique |
From: Roman G. <rom...@gm...> - 2010-01-26 21:28:55
|
Hello Triggered by a recent email on the pysparse-users list I tried to compile pysparse 1.1 for Windows and Python 2.6. I used Visual C++ (Express Edition) and the latest ACML for BLAS and LAPACK (both are available for free). Except for the superlu package (which I skipped) only a few changes to the source code were necessary (mostly due to the lack of C99 support in the MS C compiler) to build the modules. Unfortunately one of the unit tests in spmatrix_test failed, but basically it seemed to work. (Later I saw that the same unit test also fails on Linux, so it might be a general problem.) I have two questions: Do you know of anybody who has successfully built pysparse using Visual C++ recently? Do you think it would be desirable to be able to build using Visual C++ or is build process using MinGW straight-forward and sufficient? Best regards, Roman |
From: <ann...@gm...> - 2009-10-24 02:36:00
|
Look what I found at http://thesearch-imiplc.com. I thought this might help you with your job searching. http://www.thesearch-imiplc.com Comments: Would you like to earn an extra Earn $200 - $500 Every Day? for just 45 minutes work? Data Entry Workers Needed Worldwide! FOR MORE INFO PLEASE GO TO: vur.me/annafaith55/Global_Data_Entry_here/ I would personally like to invite you to become part of our team doing work-at-home data entry. We have guided thousands of team members to success using our new type of data-entry job called Global Data Entry. Some members are currently making $300 - $2000 and more per day, we have been dealing with online data entry for over 7 years. Once you become a via member, you will have exclusive access to legitimate data entry opportunities life time. Forms are just 1-3 pages and take only a few minutes to complete You will be in control and they will pay you directly via direct deposit, paypal or check. Earnings are paid every 2 weeks. Once you have signed up with our via team member, we will provide you with complete guidance and tutorials on exactly how to do these different job tasks and to make this work for you, especially the downloadables files of GLOBAL DATA ENTRY to send you in your email account. It is possible to quit your job for the first used 3 days, how much more if you work hardly 8 hours a day. This is what you have been waiting for! don't hesitate to grab this big opportunities, just try it and I can guarantee you 100% you'll enjoy it. Anna Faith White Home-Data Entry Affiliate Marketer ann...@gm... FOR MORE INFO PLEASE GO TO: vur.me/annafaith55/Global_Data_Entry_here/ God Bless from a very satisfied member one time only registration fee because we only want serious job If we allowed for free we would have "curiosity" applicants filling applications that were not really serious This is a one time adv. email only and you won't received further mailings about this. If you would like to opt-out just send an e-mail with "Opt Out in the subject line to the address ---------------------------------------------------------------------- |
From: Adam C P. IV <haz...@de...> - 2009-08-31 23:49:37
|
Thanks very much Dan! I'll package it soon. -Adam On Mon, 2009-08-31 at 18:47 -0400, Daniel Wheeler wrote: > Hi, > > I did a release of version 1.1 of pysparse, which involved: > > - bumping version number to 1.1 > - creating tags/version-1_1 branch > - releasing using the tags/version-1_1 branch > - bumping version number to 1.2a1 (just a way to say that you don't > have version 1,1 but a later revision on trunk) > > Future bug fixes should be done on "branches/version-1_1". > "tags/version-1_1" is just a place holder to remember which revision > version 1.1 was, it shouldn't be touched. > > There are a lot of changes from 1.0 and I don't know what all of them > are.I think the main difference between 1.1 and 1,0 is the vastly > superior indexing capabilities thanks to Dominque's wonderful effort > to get fancy type indexing working in pysparse. > > Cheers > > On Wed, Aug 5, 2009 at 3:29 PM, Adam C Powell IV<haz...@de...> wrote: > > On Wed, 2009-08-05 at 15:09 -0400, Daniel Wheeler wrote: > >> On Wed, Aug 5, 2009 at 2:02 PM, Adam C Powell IV<haz...@de...> wrote: > >> > Hi Dan, > >> > > >> > Yes, an official release would be helpful. Using SVN is generally a > >> > temporary thing, e.g. Elmer is hoping to release 6.0 this Fall, and is a > >> > complex package, so I wanted to use SVN to iron out the bugs before > >> > release. > >> > >> I see. You just need to iron out dependencies and stuff like that > > > > Yeah, that's not a problem. > > > >> > So if there's a 1.1.0 pysparse soon, I'll go ahead and package that. > >> > >> I'll do it soon and give you a heads up when it is done. This is going > >> into the Debian repositories correct? What about Ubuntu? > > > > Yes, into Debian. Ubuntu slurps Debian packages into their "universe" > > soon after release. So the Karmic universe is already well-established > > by now, and they'll only update packages if they are core to their > > release plans -- which pysparse almost certainly is not. > > > >> One other thing. Now that pysparse will be in the repositories (and > >> also trilinos in lenny and karmic), I don't think there is anything > >> stopping us going ahead with getting fipy in there. How should I > >> proceed with that? > > > > Indeed, that was my original motivation for packaging PySparse. :-) > > > > I'll revisit that after packaging the new PySparse release. > > > > -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ |
From: Daniel W. <dan...@gm...> - 2009-08-31 22:47:39
|
Hi, I did a release of version 1.1 of pysparse, which involved: - bumping version number to 1.1 - creating tags/version-1_1 branch - releasing using the tags/version-1_1 branch - bumping version number to 1.2a1 (just a way to say that you don't have version 1,1 but a later revision on trunk) Future bug fixes should be done on "branches/version-1_1". "tags/version-1_1" is just a place holder to remember which revision version 1.1 was, it shouldn't be touched. There are a lot of changes from 1.0 and I don't know what all of them are.I think the main difference between 1.1 and 1,0 is the vastly superior indexing capabilities thanks to Dominque's wonderful effort to get fancy type indexing working in pysparse. Cheers On Wed, Aug 5, 2009 at 3:29 PM, Adam C Powell IV<haz...@de...> wrote: > On Wed, 2009-08-05 at 15:09 -0400, Daniel Wheeler wrote: >> On Wed, Aug 5, 2009 at 2:02 PM, Adam C Powell IV<haz...@de...> wrote: >> > Hi Dan, >> > >> > Yes, an official release would be helpful. Using SVN is generally a >> > temporary thing, e.g. Elmer is hoping to release 6.0 this Fall, and is a >> > complex package, so I wanted to use SVN to iron out the bugs before >> > release. >> >> I see. You just need to iron out dependencies and stuff like that > > Yeah, that's not a problem. > >> > So if there's a 1.1.0 pysparse soon, I'll go ahead and package that. >> >> I'll do it soon and give you a heads up when it is done. This is going >> into the Debian repositories correct? What about Ubuntu? > > Yes, into Debian. Ubuntu slurps Debian packages into their "universe" > soon after release. So the Karmic universe is already well-established > by now, and they'll only update packages if they are core to their > release plans -- which pysparse almost certainly is not. > >> One other thing. Now that pysparse will be in the repositories (and >> also trilinos in lenny and karmic), I don't think there is anything >> stopping us going ahead with getting fipy in there. How should I >> proceed with that? > > Indeed, that was my original motivation for packaging PySparse. :-) > > I'll revisit that after packaging the new PySparse release. > > -Adam > -- > GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 > > Engineering consulting with open source tools > http://www.opennovation.com/ > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Pysparse-developers mailing list > Pys...@li... > https://lists.sourceforge.net/lists/listinfo/pysparse-developers > > -- Daniel Wheeler |
From: Adam C P. IV <haz...@de...> - 2009-08-05 19:30:17
|
On Wed, 2009-08-05 at 15:09 -0400, Daniel Wheeler wrote: > On Wed, Aug 5, 2009 at 2:02 PM, Adam C Powell IV<haz...@de...> wrote: > > Hi Dan, > > > > Yes, an official release would be helpful. Using SVN is generally a > > temporary thing, e.g. Elmer is hoping to release 6.0 this Fall, and is a > > complex package, so I wanted to use SVN to iron out the bugs before > > release. > > I see. You just need to iron out dependencies and stuff like that Yeah, that's not a problem. > > So if there's a 1.1.0 pysparse soon, I'll go ahead and package that. > > I'll do it soon and give you a heads up when it is done. This is going > into the Debian repositories correct? What about Ubuntu? Yes, into Debian. Ubuntu slurps Debian packages into their "universe" soon after release. So the Karmic universe is already well-established by now, and they'll only update packages if they are core to their release plans -- which pysparse almost certainly is not. > One other thing. Now that pysparse will be in the repositories (and > also trilinos in lenny and karmic), I don't think there is anything > stopping us going ahead with getting fipy in there. How should I > proceed with that? Indeed, that was my original motivation for packaging PySparse. :-) I'll revisit that after packaging the new PySparse release. -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ |
From: Daniel W. <dan...@gm...> - 2009-08-05 19:09:54
|
On Wed, Aug 5, 2009 at 2:02 PM, Adam C Powell IV<haz...@de...> wrote: > Hi Dan, > > Yes, an official release would be helpful. Using SVN is generally a > temporary thing, e.g. Elmer is hoping to release 6.0 this Fall, and is a > complex package, so I wanted to use SVN to iron out the bugs before > release. I see. You just need to iron out dependencies and stuff like that > So if there's a 1.1.0 pysparse soon, I'll go ahead and package that. I'll do it soon and give you a heads up when it is done. This is going into the Debian repositories correct? What about Ubuntu? One other thing. Now that pysparse will be in the repositories (and also trilinos in lenny and karmic), I don't think there is anything stopping us going ahead with getting fipy in there. How should I proceed with that? -- Daniel Wheeler |
From: Adam C P. IV <haz...@de...> - 2009-08-05 18:16:26
|
Hi Dan, Yes, an official release would be helpful. Using SVN is generally a temporary thing, e.g. Elmer is hoping to release 6.0 this Fall, and is a complex package, so I wanted to use SVN to iron out the bugs before release. So if there's a 1.1.0 pysparse soon, I'll go ahead and package that. Thanks, Adam On Wed, 2009-08-05 at 10:13 -0400, Daniel Wheeler wrote: > Hi Adam, Hope all is well. Isn't it probably best to the deb release > from an official pysparse release? The latest release is 1.0.1, which > at this stage is a little old. So, maybe we should do a pysparse > release and then do the deb. > > Dominque, Shall I go ahead and do that? The version number probably > needs bumping to 1.1 as there are a lot of extra features that you've > added, but a script that uses 1.0 will probably still work with 1.1. > Right? -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ |
From: Dominique O. <dom...@gm...> - 2009-08-05 14:18:39
|
On Wed, Aug 5, 2009 at 10:13 AM, Daniel Wheeler <dan...@gm...>wrote: > Hi Adam, Hope all is well. Isn't it probably best to the deb release > from an official pysparse release? The latest release is 1.0.1, which > at this stage is a little old. So, maybe we should do a pysparse > release and then do the deb. > > Dominque, Shall I go ahead and do that? The version number probably > needs bumping to 1.1 as there are a lot of extra features that you've > added, but a script that uses 1.0 will probably still work with 1.1. > Right? Hi Daniel, Yes, please go ahead a issue a new 1.1 release. I'm currently tied up with lots of commitments. And yes, everything is backward compatible. Thanks! -- Dominique |
From: Daniel W. <dan...@gm...> - 2009-08-05 14:13:27
|
Hi Adam, Hope all is well. Isn't it probably best to the deb release from an official pysparse release? The latest release is 1.0.1, which at this stage is a little old. So, maybe we should do a pysparse release and then do the deb. Dominque, Shall I go ahead and do that? The version number probably needs bumping to 1.1 as there are a lot of extra features that you've added, but a script that uses 1.0 will probably still work with 1.1. Right? On Tue, Aug 4, 2009 at 7:47 PM, Adam C Powell IV<haz...@de...> wrote: > On Tue, 2009-08-04 at 19:14 -0400, Dominique Orban wrote: >> On Tue, Aug 4, 2009 at 6:44 PM, Adam C Powell IV <haz...@de...> >> wrote: >> On Tue, 2009-08-04 at 12:12 -0400, Dominique Orban wrote: >> > On Tue, Aug 4, 2009 at 9:37 AM, Adam C Powell IV >> <haz...@de...> >> > wrote: >> > Hi, >> > >> > The following segfault-inducing code came in from a >> user >> > (details at >> > http://bugs.debian.org/535318 ): >> > >> > from numpy import * >> > from pysparse import * >> >> [snip] >> > Segmentation fault >> > >> > Any ideas? Bug in user's code, pysparse, or Debian >> packaging? >> > Hi, >> > >> > >> > Thanks for the report. Lots of bugs in user's code. Still >> Pysparse >> > should not have crashed with a segfault. I have now added >> appropriate >> > argument checking. >> >> >> Thank you. Any idea when a new release might happen? >> >> >> I updated the Pysparse svn repository earlier today (revision 124). >> Oz's code now terminates with appropriate error messages. What is best >> for you? Are you able to grab the svn tree to package the source into >> a deb or would you rather a tar.gz of the source tree? I admit I've >> been relying on svn so far and haven't released the source tree much. > > I'd be happy to package the SVN tree, I do that also for Elmer. But an > occasional release would be nice, whenever is convenient for you. > >> > The user who reported the bug is also the author of the Deb >> package. >> > He says he will fix the package soon. >> >> >> Sorry I wasn't clear: the package author is me, the user who >> reported >> this is Oz Nahum (or Nahum Oz?). >> >> >> Ah I misunderstood that. Oz was trying to package Pysparse into a deb >> at some point, which is why I thought he was still the package author. >> Thank you for your help. I'll mention on the website that a deb is now >> available. > > Great, thanks. My .deb has been in unstable for almost three years now, > and released as part of Lenny (5.0). I think it's also been in Ubuntu > universe since Hardy Heron (8.04), maybe even Gutsy Gibbon (7.10). > > -Adam > -- > GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 > > Engineering consulting with open source tools > http://www.opennovation.com/ > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Pysparse-developers mailing list > Pys...@li... > https://lists.sourceforge.net/lists/listinfo/pysparse-developers > > -- Daniel Wheeler |
From: Adam C P. IV <haz...@de...> - 2009-08-04 23:48:18
|
On Tue, 2009-08-04 at 19:14 -0400, Dominique Orban wrote: > On Tue, Aug 4, 2009 at 6:44 PM, Adam C Powell IV <haz...@de...> > wrote: > On Tue, 2009-08-04 at 12:12 -0400, Dominique Orban wrote: > > On Tue, Aug 4, 2009 at 9:37 AM, Adam C Powell IV > <haz...@de...> > > wrote: > > Hi, > > > > The following segfault-inducing code came in from a > user > > (details at > > http://bugs.debian.org/535318 ): > > > > from numpy import * > > from pysparse import * > > [snip] > > Segmentation fault > > > > Any ideas? Bug in user's code, pysparse, or Debian > packaging? > > Hi, > > > > > > Thanks for the report. Lots of bugs in user's code. Still > Pysparse > > should not have crashed with a segfault. I have now added > appropriate > > argument checking. > > > Thank you. Any idea when a new release might happen? > > > I updated the Pysparse svn repository earlier today (revision 124). > Oz's code now terminates with appropriate error messages. What is best > for you? Are you able to grab the svn tree to package the source into > a deb or would you rather a tar.gz of the source tree? I admit I've > been relying on svn so far and haven't released the source tree much. I'd be happy to package the SVN tree, I do that also for Elmer. But an occasional release would be nice, whenever is convenient for you. > > The user who reported the bug is also the author of the Deb > package. > > He says he will fix the package soon. > > > Sorry I wasn't clear: the package author is me, the user who > reported > this is Oz Nahum (or Nahum Oz?). > > > Ah I misunderstood that. Oz was trying to package Pysparse into a deb > at some point, which is why I thought he was still the package author. > Thank you for your help. I'll mention on the website that a deb is now > available. Great, thanks. My .deb has been in unstable for almost three years now, and released as part of Lenny (5.0). I think it's also been in Ubuntu universe since Hardy Heron (8.04), maybe even Gutsy Gibbon (7.10). -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ |
From: Dominique O. <dom...@gm...> - 2009-08-04 23:14:47
|
On Tue, Aug 4, 2009 at 6:44 PM, Adam C Powell IV <haz...@de...>wrote: > On Tue, 2009-08-04 at 12:12 -0400, Dominique Orban wrote: > > On Tue, Aug 4, 2009 at 9:37 AM, Adam C Powell IV <haz...@de...> > > wrote: > > Hi, > > > > The following segfault-inducing code came in from a user > > (details at > > http://bugs.debian.org/535318 ): > > > > from numpy import * > > from pysparse import * > [snip] > > Segmentation fault > > > > Any ideas? Bug in user's code, pysparse, or Debian packaging? > > Hi, > > > > > > Thanks for the report. Lots of bugs in user's code. Still Pysparse > > should not have crashed with a segfault. I have now added appropriate > > argument checking. > > Thank you. Any idea when a new release might happen? I updated the Pysparse svn repository earlier today (revision 124). Oz's code now terminates with appropriate error messages. What is best for you? Are you able to grab the svn tree to package the source into a deb or would you rather a tar.gz of the source tree? I admit I've been relying on svn so far and haven't released the source tree much. > > The user who reported the bug is also the author of the Deb package. > > He says he will fix the package soon. > > Sorry I wasn't clear: the package author is me, the user who reported > this is Oz Nahum (or Nahum Oz?). Ah I misunderstood that. Oz was trying to package Pysparse into a deb at some point, which is why I thought he was still the package author. Thank you for your help. I'll mention on the website that a deb is now available. -- Dominique |
From: Adam C P. IV <haz...@de...> - 2009-08-04 22:58:50
|
On Tue, 2009-08-04 at 12:12 -0400, Dominique Orban wrote: > On Tue, Aug 4, 2009 at 9:37 AM, Adam C Powell IV <haz...@de...> > wrote: > Hi, > > The following segfault-inducing code came in from a user > (details at > http://bugs.debian.org/535318 ): > > from numpy import * > from pysparse import * [snip] > Segmentation fault > > Any ideas? Bug in user's code, pysparse, or Debian packaging? > Hi, > > > Thanks for the report. Lots of bugs in user's code. Still Pysparse > should not have crashed with a segfault. I have now added appropriate > argument checking. Thank you. Any idea when a new release might happen? > The user who reported the bug is also the author of the Deb package. > He says he will fix the package soon. Sorry I wasn't clear: the package author is me, the user who reported this is Oz Nahum (or Nahum Oz?). -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ |
From: Adam C P. IV <haz...@de...> - 2009-08-04 13:59:28
|
Hi, The following segfault-inducing code came in from a user (details at http://bugs.debian.org/535318 ): from numpy import * from pysparse import * m = 4 n = 3 nodec=0 A = spmatrix.ll_mat(m*n, m*n) H = 3 V = 2 a = [0,0,0,] #row index b = [0,1,n] #column index val = [H+V, -H, -V] #node value w=m*n nodec=0 w=m*n bottomr=w-n for i in range(w): for j in range(w): if (nodec)<bottomr:#check necessary to make sure we don't #try puting south neighbours for the bottom row of nodes b.append(nodec+n) a.append(nodec-1)#row index, we skipped the first node val.append(-V) nodec=nodec+1 A.put(val,a,b) print A for i in range(w): for j in range(w): if (nodec-n)>=0: #check necessary to make sure we don't #try puting north neighbours for the top row of nodes b.append(nodec-n) a.append(nodec-1)#row index val.append(-V) nodec=nodec+1 A.put(val,a,b) print A Also a log of crash: In [20]: a Out[20]: [1, 3, 5] In [21]: b Out[21]: [2, 3, 5] In [22]: c Out[22]: [4, 5, 9] In [23]: A.take(c,a,b) Segmentation fault Any ideas? Bug in user's code, pysparse, or Debian packaging? Thanks, -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ |