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
|
<HEAD> <META content="text/html; charset=windows-1252" http-equiv=Content-Type> <META name=GENERATOR content="MSHTML 8.00.7600.16385"></HEAD> <BODY> <P align=center><FONT color=#ff0000 size=2><SPAN style="FONT-FAMILY: Arial; COLOR: red; FONT-SIZE: 16pt; mso-ascii-font-family: Arial; mso-ansi-language: es; mso-default-font-family: Arial; mso-latin-font-family: Arial; mso-greek-font-family: Arial; mso-cyrillic-font-family: Arial; mso-hebrew-font-family: Arial; mso-arabic-font-family: Arial; mso-latinext-font-family: Arial; language: es" lang=es><A href="http://informaticaocasion.eu/search?controller=search&orderby=position&orderway=desc&search_query=2560">Gran oferta</A></SPAN></FONT><SPAN style="FONT-STYLE: normal; FONT-FAMILY: 'Trebuchet MS', sans-serif; COLOR: rgb(28,99,146); FONT-SIZE: 18px; FONT-WEIGHT: normal; TEXT-DECORATION: none" class=text_headline_item_product_overview><FONT color=#000000 size=2><A href="http://informaticaocasion.eu/search?controller=search&orderby=position&orderway=desc&search_query=2560"> </A> </FONT></SPAN></P> <P align=center><SPAN style="FONT-STYLE: normal; FONT-FAMILY: 'Trebuchet MS', sans-serif; COLOR: rgb(28,99,146); FONT-SIZE: 18px; FONT-WEIGHT: normal; TEXT-DECORATION: none" class=text_headline_item_product_overview><FONT color=#000000><FONT size=2><A href="http://informaticaocasion.eu/search?controller=search&orderby=position&orderway=desc&search_query=2560"><STRONG>DELLHP 2560 - i7 -12,5"</STRONG></A></FONT></FONT></SPAN><SPAN style="FONT-STYLE: normal; FONT-FAMILY: 'Trebuchet MS', sans-serif; COLOR: rgb(28,99,146); FONT-SIZE: 18px; FONT-WEIGHT: normal; TEXT-DECORATION: none" class=text_headline_item_product_overview><FONT color=#000000><FONT size=2> -<A href=" color=#0000ff> GB de RAM 320 GB de Disco duro</FONT> </STRONG></A><STRONG> </STRONG></FONT></FONT><A style="TEXT-ALIGN: left; TEXT-TRANSFORM: none; BACKGROUND-COLOR: rgb(198,223,233); TEXT-INDENT: 0px; FONT: 11px 'Trebuchet MS', Tahoma, Verdana, Arial, sans-serif; WHITE-SPACE: normal; LETTER-SPACING: normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px; TEXT-DECORATION: none; webkit-text-stroke-width: 0px" href="http://informaticaocasion.eu/search?controller=search&orderby=position&orderway=desc&search_query=2560" name=http://informaticaocasion.eu/search?controller=search&orderby=position&orderway=desc&search_query=2560"><FONT size=3><STRONG>225,02 EUR</STRONG></FONT> </A> </FONT> </SPAN></FONT></SPAN> <A href="http://informaticaocasion.eu/reciclados/24-dell-gx-520.html"></A> <A href="http://informaticaocasion.eu/12-ordenadores-sobremesa?p=2"></A> <A href="http://informaticaocasion.eu/12-ordenadores-sobremesa"></A> <A href="http://informaticaocasion.eu/portatiles/193-hp-6910p-14.html"></A> <A href=" border=0 hspace=0 alt="" align=baseline src="cid:9188617636-1"></A></P> <P align=center><FONT size=2 face="Verdana, Arial, Helvetica, sans-serif"><A href="http://informaticaocasion.eu/search?controller=search&orderby=position&orderway=desc&search_query=2560">Para acceder a la oferta pinche sobre la foto del portátil</A></FONT></P><A href="http://informaticaocasion.eu/es/portatiles/81-dell-vostro-i3-156-4250401200813.html"></A> <P align=center><STRONG><FONT color=#000080>1 AÑO DE GARANTÍA</FONT></STRONG> <IMG border=0 hspace=0 alt="" align=baseline src="cid:6382300224-2"><STRONG>Comercio electrónico seguro</STRONG> </P> <P align=center> <SPAN style="TEXT-ALIGN: right; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; DISPLAY: inline !important; FONT: 18px 'Trebuchet MS', sans-serif; WHITE-SPACE: nowrap; FLOAT: none; LETTER-SPACING: normal; COLOR: rgb(28,99,146); WORD-SPACING: 0px; webkit-text-stroke-width: 0px"> </SPAN> </P> <P align=center><FONT color=#0000ff face="Arial, Helvetica, sans-serif"><STRONG>Mas ofertas en: </STRONG></FONT><A href="http://www.informaticaocasion.eu"><FONT face="Arial, Helvetica, sans-serif"><STRONG>www.informaticaocasion.eu</STRONG></FONT></A> </P> <P align=center><STRONG><FONT color=#000080 size=5> <DIV style="TEXT-ALIGN: right; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; FONT: 11px 'Trebuchet MS', sans-serif; WHITE-SPACE: normal; LETTER-SPACING: normal; COLOR: rgb(97,97,97); WORD-SPACING: 0px; webkit-text-stroke-width: 0px"> <P align=center><STRONG></STRONG></P></DIV></FONT></STRONG><SPAN style="BACKGROUND-COLOR: #ffffff; FONT-FAMILY: Arial; COLOR: #0000ff; FONT-WEIGHT: 700"><FONT size=2>*Oferta hasta finalizar existencias</FONT></SPAN> <P></P><FONT face=Arial><SPAN style="FONT-SIZE: 9pt"> <P align=left><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 12pt; mso-ansi-language: ES; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-fareast-language: ES; mso-bidi-language: AR-SA"><FONT size=2>Su dirección de email ha sido recopilada de fuentes de público acceso en Internet. Conforme a la Directiva Europea 2002/58/EC y la Ley 32/2003, de 3 de noviembre, General de Telecomunicaciones. Usted tiene el derecho a oponerse a que sus datos personales se utilicen para fines publicitarios y de marketing. Si este es su deseo, le rogamos que responda a este mensaje con la palabra <STRONG>"Baja"</STRONG> en el campo Asunto y automaticamente dejará de recibir comunicaciones publicitarias por nuestra parte.<BR>CONFIDENCIALIDAD: La información contenida en este mensaje y/o archivo(s) adjunto(s) es confidencial/privilegiada y está destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida. Si usted lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida, y puede ser ilegal, cualquier divulgación, distribución o reproducción de esta comunicación.Si no es el destinatario, le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la dirección arriba mencionada.</FONT></SPAN><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 12pt; mso-ansi-language: ES; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-fareast-language: ES; mso-bidi-language: AR-SA"><FONT size=2>Recuerde que para poder atender de inmediato su petición debería notificar su baja, oposición o cancelación desde la cuenta que quiere dar de baja.</FONT></SPAN></P> <P align=left><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 12pt; mso-ansi-language: ES; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-fareast-language: ES; mso-bidi-language: AR-SA"><FONT size=2>Gracias.</FONT></SPAN></SPAN></FONT></P></BODY>
<HEAD> <META content="text/html; charset=windows-1252" http-equiv=Content-Type> <META name=GENERATOR content="MSHTML 8.00.7600.16385"></HEAD> <BODY> <P align=center><FONT color=#ff0000 size=2><SPAN style="FONT-FAMILY: Arial; COLOR: red; FONT-SIZE: 16pt; mso-ascii-font-family: Arial; mso-ansi-language: es; mso-default-font-family: Arial; mso-latin-font-family: Arial; mso-greek-font-family: Arial; mso-cyrillic-font-family: Arial; mso-hebrew-font-family: Arial; mso-arabic-font-family: Arial; mso-latinext-font-family: Arial; language: es" lang=es><A href="http://informaticaocasion.eu/es/apple-mac/200-mac.html">Gran oferta</A></SPAN></FONT><SPAN style="FONT-STYLE: normal; FONT-FAMILY: 'Trebuchet MS', sans-serif; COLOR: rgb(28,99,146); FONT-SIZE: 18px; FONT-WEIGHT: normal; TEXT-DECORATION: none" class=text_headline_item_product_overview><FONT color=#000000 size=2><A href="http://informaticaocasion.eu/es/apple-mac/200-mac.html"> </A> </FONT></SPAN></P> <P align=center><SPAN style="FONT-STYLE: normal; FONT-FAMILY: 'Trebuchet MS', sans-serif; COLOR: rgb(28,99,146); FONT-SIZE: 18px; FONT-WEIGHT: normal; TEXT-DECORATION: none" class=text_headline_item_product_overview><FONT color=#000000><FONT size=2><A href="http://informaticaocasion.eu/es/apple-mac/200-mac.html"><STRONG>APPLE MacBookPro9,2 - i5 -13,3"</STRONG></A></FONT></FONT></SPAN><SPAN style="FONT-STYLE: normal; FONT-FAMILY: 'Trebuchet MS', sans-serif; COLOR: rgb(28,99,146); FONT-SIZE: 18px; FONT-WEIGHT: normal; TEXT-DECORATION: none" class=text_headline_item_product_overview><FONT color=#000000><FONT size=2> -<A href=" color=#0000ff> GB de RAM 500 GB de Disco duro</FONT> </STRONG></A><STRONG> </STRONG></FONT></FONT><A style="TEXT-ALIGN: left; TEXT-TRANSFORM: none; BACKGROUND-COLOR: rgb(198,223,233); TEXT-INDENT: 0px; FONT: 11px 'Trebuchet MS', Tahoma, Verdana, Arial, sans-serif; WHITE-SPACE: normal; LETTER-SPACING: normal; COLOR: rgb(0,0,0); WORD-SPACING: 0px; TEXT-DECORATION: none; webkit-text-stroke-width: 0px" href="http://informaticaocasion.eu/es/apple-mac/200-mac.html" name=http://informaticaocasion.eu/es/apple-mac/200-mac.html"><FONT size=3><STRONG>532,55 EUR</STRONG></FONT> </A> </FONT> </SPAN></FONT></SPAN> <A href="http://informaticaocasion.eu/reciclados/24-dell-gx-520.html"></A> <A href="http://informaticaocasion.eu/12-ordenadores-sobremesa?p=2"></A> <A href="http://informaticaocasion.eu/12-ordenadores-sobremesa"></A> <A href="http://informaticaocasion.eu/portatiles/193-hp-6910p-14.html"></A> <A href=" border=0 hspace=0 alt="" align=baseline src="cid:5924914841-1"></A></P> <P align=center><FONT size=2 face="Verdana, Arial, Helvetica, sans-serif"><A href="http://informaticaocasion.eu/es/apple-mac/200-mac.html">Para acceder a la oferta pinche sobre la foto del portátil</A></FONT></P><A href="http://informaticaocasion.eu/es/portatiles/81-dell-vostro-i3-156-4250401200813.html"></A> <P align=center><STRONG><FONT color=#000080>1 AÑO DE GARANTÍA</FONT></STRONG> <IMG border=0 hspace=0 alt="" align=baseline src="cid:1834629371-2"><STRONG>Comercio electrónico seguro</STRONG> </P> <P align=center> <SPAN style="TEXT-ALIGN: right; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; DISPLAY: inline !important; FONT: 18px 'Trebuchet MS', sans-serif; WHITE-SPACE: nowrap; FLOAT: none; LETTER-SPACING: normal; COLOR: rgb(28,99,146); WORD-SPACING: 0px; webkit-text-stroke-width: 0px"> </SPAN> </P> <P align=center><FONT color=#0000ff face="Arial, Helvetica, sans-serif"><STRONG>Mas ofertas en: </STRONG></FONT><A href="http://www.informaticaocasion.eu"><FONT face="Arial, Helvetica, sans-serif"><STRONG>www.informaticaocasion.eu</STRONG></FONT></A> </P> <P align=center><STRONG><FONT color=#000080 size=5> <DIV style="TEXT-ALIGN: right; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; FONT: 11px 'Trebuchet MS', sans-serif; WHITE-SPACE: normal; LETTER-SPACING: normal; COLOR: rgb(97,97,97); WORD-SPACING: 0px; webkit-text-stroke-width: 0px"> <P align=center><STRONG></STRONG></P></DIV></FONT></STRONG><SPAN style="BACKGROUND-COLOR: #ffffff; FONT-FAMILY: Arial; COLOR: #0000ff; FONT-WEIGHT: 700"><FONT size=2>*Oferta hasta finalizar existencias</FONT></SPAN> <P></P><FONT face=Arial><SPAN style="FONT-SIZE: 9pt"> <P align=left><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 12pt; mso-ansi-language: ES; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-fareast-language: ES; mso-bidi-language: AR-SA"><FONT size=2>Su dirección de email ha sido recopilada de fuentes de público acceso en Internet. Conforme a la Directiva Europea 2002/58/EC y la Ley 32/2003, de 3 de noviembre, General de Telecomunicaciones. Usted tiene el derecho a oponerse a que sus datos personales se utilicen para fines publicitarios y de marketing. Si este es su deseo, le rogamos que responda a este mensaje con la palabra <STRONG>"Baja"</STRONG> en el campo Asunto y automaticamente dejará de recibir comunicaciones publicitarias por nuestra parte.<BR>CONFIDENCIALIDAD: La información contenida en este mensaje y/o archivo(s) adjunto(s) es confidencial/privilegiada y está destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida. Si usted lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida, y puede ser ilegal, cualquier divulgación, distribución o reproducción de esta comunicación.Si no es el destinatario, le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la dirección arriba mencionada.</FONT></SPAN><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 12pt; mso-ansi-language: ES; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-fareast-language: ES; mso-bidi-language: AR-SA"><FONT size=2>Recuerde que para poder atender de inmediato su petición debería notificar su baja, oposición o cancelación desde la cuenta que quiere dar de baja.</FONT></SPAN></P> <P align=left><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 12pt; mso-ansi-language: ES; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-fareast-language: ES; mso-bidi-language: AR-SA"><FONT size=2>Gracias.</FONT></SPAN></SPAN></FONT></P></BODY>
Hallo Ich arbeite mit in der HSBC Bank Malaysia Berhad als einer der Senior Vice President, ich Ihnen dieses Memo schreibe, weil ich habe eine dringende Geschäfts Vorschlag für Sie, die uns beide, und It`s dringend profitieren. Bitte schreiben Sie meine persönliche E-Mail für weitere Details. moi...@ar... <mailto:moi...@ar...> Vielen Dank Frau Chan Yoke Moi E-mail: moi...@ar... <mailto:moi...@ar...>
<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="434" height="326"><param name="movie" value="http://cache.reverbnation.com/widgets/swf/48/pro_widget.swf?id=artist_2782324&posted_by=artist_2782324&skin_id=PWFS5010&background_color=EEEEEE&border_color=000000&auto_play=false&shuffle=false"></param><param name="allowscriptaccess" value="always"></param><param name="allowNetworking" value="all"></param><param name="allowfullscreen" value="true"></param><param name="wmode" value="opaque"></param><param name="quality" value="best"></param><param name="flashvars" value="id=artist_2782324&posted_by=artist_2782324&skin_id=PWFS5010&background_color=EEEEEE&border_color=000000&auto_play=false&shuffle=false"></param><embed src="http://cache.reverbnation.com/widgets/swf/48/pro_widget.swf?id=artist_2782324&posted_by=artist_2782324&skin_id=PWFS5010&background_color=EEEEEE&border_color=000000&auto_play=false&shuffle=false" type="application/x-shockwave-flash" allowscriptaccess="always" allowNetworking="all" allowfullscreen="true" wmode="opaque" flashvars="id=artist_2782324&posted_by=artist_2782324&skin_id=PWFS5010&background_color=EEEEEE&border_color=000000&auto_play=false&shuffle=false" quality="best" width="434" height="326"></embed></object><br/> <img style="visibility:hidden;width:0px;height:0px;" border=0 width=0 height=0 src="http://www.reverbnation.com/widgets/trk/48/artist_2782324/artist_2782324/t.gif" /><img style="visibility:hidden;width:0px;height:0px;" border="0" width="0" height="0" src=" style="visibility:hidden;width:0px;height:0px;" border="0" width="0" height="0" src="// style="visibility:hidden;width:0px;height:0px;" border="0" width="0" height="0" src="http://ib.adnxs.com/seg?add=405193&t=2"/> THANK YOU FOR YOUR TIME...
<img style="visibility:hidden;width:0px;height:0px;" border=0 width=0 height=0 src="http://c.gigcount.com/wildfire/IMP/CXNID=2000002.0NXC/bT*xJmx*PTEzNDU3ODY3MDMwMDEmcHQ9MTM*NTc4NjcyNzkyNCZwPTI3MDgxJmQ9dHVuZVdpZGdldF9maXJzdF9nZW4mZz*xJm89/NTgwYTFmMzliOTlmNDBhZmI4Nzg5ODA3ZDE*MjNhYjAmb2Y9MA==.gif" /><object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="434" height="415"><param name="movie" value="http://cache.reverbnation.com/widgets/swf/19/tuneWidget.swf?twID=artist_2782324&posted_by=artist_2782324&shuffle=&autoPlay=false&blogBuzz=buzz"></param><param name="allowscriptaccess" value="always"></param><param name="allowNetworking" value="all"></param><param name="allowfullscreen" value="true"></param><param name="wmode" value="opaque"></param><param name="quality" value="best"></param><param name="flashvars" value="twID=artist_2782324&posted_by=artist_2782324&shuffle=&autoPlay=false&blogBuzz=buzz"></param><embed src="http://cache.reverbnation.com/widgets/swf/19/tuneWidget.swf?twID=artist_2782324&posted_by=artist_2782324&shuffle=&autoPlay=false&blogBuzz=buzz" type="application/x-shockwave-flash" allowscriptaccess="always" allowNetworking="all" allowfullscreen="true" wmode="opaque" flashvars="twID=artist_2782324&posted_by=artist_2782324&shuffle=&autoPlay=false&blogBuzz=buzz" quality="best" width="434" height="415"></embed></object><br/><a href="http://www.reverbnation.com/main/widgets_overview" onclick="javascript:window.location.href="http://www.reverbnation.com/c./a4/19/2782324/Artist/2782324/Artist/link"; return false;"><img alt="stand alone player" border="0" height="19" src="http://gp1.wac.edgecastcdn.net/802892/production_static/widgets/content/19/footer.png" width="434" /></a><img style="visibility:hidden;width:0px;height:0px;" border=0 width=0 height=0 src="http://www.reverbnation.com/widgets/trk/19/artist_2782324/artist_2782324/t.gif" /><img style="visibility:hidden;width:0px;height:0px;" border="0" width="0" height="0" src="http://www.googleadservices.com/pagead/conversion/1007099629/?label=3apRCPOe5wIQ7b2c4AM&guid=ON&script=0"/> Thank You for your time...
![http://www.reverbnation.com/widgets/trk/48/artist_2782324/artist_2782324/t.gif"](/index.cgi/speech/http://www.reverbnation.com/widgets/trk/48/artist_2782324/artist_2782324/t.gif"){kind=link}
![http://c.gigcount.com/wildfire/IMP/CXNID=2000002.0NXC/bT*xJmx*PTEzNDU3ODY3MDMwMDEmcHQ9MTM*NTc4NjcyNzkyNCZwPTI3MDgxJmQ9dHVuZVdpZGdldF9maXJzdF9nZW4mZz*xJm89/NTgwYTFmMzliOTlmNDBhZmI4Nzg5ODA3ZDE*MjNhYjAmb2Y9MA==.gif"](/index.cgi/speech/http://c.gigcount.com/wildfire/IMP/CXNID=2000002.0NXC/bT*xJmx*PTEzNDU3ODY3MDMwMDEmcHQ9MTM*NTc4NjcyNzkyNCZwPTI3MDgxJmQ9dHVuZVdpZGdldF9maXJzdF9nZW4mZz*xJm89/NTgwYTFmMzliOTlmNDBhZmI4Nzg5ODA3ZDE*MjNhYjAmb2Y9MA==.gif"){kind=link}
![http://gp1.wac.edgecastcdn.net/802892/production_static/widgets/content/19/footer.png"](/index.cgi/speech/http://gp1.wac.edgecastcdn.net/802892/production_static/widgets/content/19/footer.png"){kind=link}
![http://www.reverbnation.com/widgets/trk/19/artist_2782324/artist_2782324/t.gif"](/index.cgi/speech/http://www.reverbnation.com/widgets/trk/19/artist_2782324/artist_2782324/t.gif"){kind=link}
On Thu, May 17, 2012 at 12:33 PM, Dominique Orban
<dom...@gm...> wrote:
> On Thu, May 17, 2012 at 12:18 PM, Daniel Wheeler
> <dan...@gm...> wrote:
>> Is it time for a new release? Dominique has done a lot of work since
>> 1.1.1 if I remember rightly. I believe there was something holding up
>> a release a year or two back, but I can't remember what that was.
>
> The last thing I did is use the version of UMFPACK that comes with
> SuiteSparse. The code is in the suitesparse branch. My hope was to
> pave the way to interfacing other factorizations (CHOLMOD and
> SuiteSparseQR are my two targets), but time is short.
>
> Also I'm wondering if we should phase out SuperLU. I'm not having much
> success with it. Its only advatange is to run in parallel. Just a
> notion.
I assume you mean that you would remove pysparse/direct/superlu and
only have pysparse/direct/umfpack. I'll leave that up to you. The only
requirement that I have right now is that the code snippet at then end
of pysparse/__init__.py still works in some way that doesn't break
everything in fipy. Probably, the best thing to do is to deprecate it
now and remove it sometime in the future (or make it work with UMFPACK
and give a warning that superlu is not using SuperLU but something
else to do LU). The code snippet is this:
{{{
class _superlu:
@Deprecated('Use pysparse.direct.superlu.factorize instead.')
def factorize(self, *args, **kwargs):
import pysparse.direct.superlu
self.factorizeFnc = pysparse.direct.superlu.factorize
return self.factorizeFnc(*args, **kwargs)
superlu = _superlu()
}}}
so that
{{{
from pysparse import superlu
}}}
still works. Actually, I need to switch fipy over to the new import
system of pysparse. I'll do that today or tomorrow while it is on my
mind.
Cheers
--
Daniel Wheeler
On Thu, May 17, 2012 at 12:18 PM, Daniel Wheeler <dan...@gm...> wrote: > Is it time for a new release? Dominique has done a lot of work since > 1.1.1 if I remember rightly. I believe there was something holding up > a release a year or two back, but I can't remember what that was. The last thing I did is use the version of UMFPACK that comes with SuiteSparse. The code is in the suitesparse branch. My hope was to pave the way to interfacing other factorizations (CHOLMOD and SuiteSparseQR are my two targets), but time is short. Also I'm wondering if we should phase out SuperLU. I'm not having much success with it. Its only advatange is to run in parallel. Just a notion. Cheers, -- Dominique
Is it time for a new release? Dominique has done a lot of work since 1.1.1 if I remember rightly. I believe there was something holding up a release a year or two back, but I can't remember what that was. Cheers -- Daniel Wheeler
On Sat, Feb 11, 2012 at 04:30, Oz Nahum Tiram <na...@gm...> wrote: > Hi, > > First, thanks for the great work on this peace of software. I have > been using it for more than 3 years now and I very happy. > I have a few question and I hope this is not > I am still very new to C programming and I was wondering what does the > following statement for expamle do: > > n2b = F77(dnrm2)(&n, b, &ONE);/* Norm of rhs vector, b */ > > Is this some kind of type casting ? This is a macro that adjusts the call to various types of Fortran compilers (this particular call is a call to the BLAS library, which is written in Fortran). Some Fortran compilers add a trailing underscore to symbols, some add two, some add none, etc. > The second question is, now that I have a working application with > pysparse that I'd like to accelerate, > I am thinking of rewriting my code in C. I know there are C solvers > for bicgstab, but I was wondering how > much work is it just to convert the bicgstab.c from pysparse to plain > C without the python dependencies. > Are there any hints here? I wouldn't recommend coding bicgstab all over again. The only costly operations in Bi-CGSTAB (and other Krylov-type methods) are vector operations (most often, addition of vectors) and operator-vector products (e.g., A*x or A.T*x). I would say that to speed things up, you'll want to speed up your operator-vector operations; they are the dominant cost. You can take a look at PyKrylov (https://github.com/dpo/pykrylov) which contains a pure Python implementation of Bi-CGSTAB and allows you to input your operator in different ways (a Pysparse matrix being one of them). For instance, you could implement your operator in C or in Cython and that should speed things up. I believe that is the way to go. Of course, vector operations in PyKrylov could also be speeded up with Cython. That's been on my list for a while. I hope this helps. -- Dominique
Hi, First, thanks for the great work on this peace of software. I have been using it for more than 3 years now and I very happy. I have a few question and I hope this is not I am still very new to C programming and I was wondering what does the following statement for expamle do: n2b = F77(dnrm2)(&n, b, &ONE);/* Norm of rhs vector, b */ Is this some kind of type casting ? The second question is, now that I have a working application with pysparse that I'd like to accelerate, I am thinking of rewriting my code in C. I know there are C solvers for bicgstab, but I was wondering how much work is it just to convert the bicgstab.c from pysparse to plain C without the python dependencies. Are there any hints here? Thanks in advance, Oz
Hi, Thanks for the bug report. This has been fixed in the new-setup-py branch. I encourage users to use that branch as it will become the default as soon as I find the time to make the merge. Cheers, Dominique On Wed, Aug 4, 2010 at 9:42 PM, Roman Geus <rom...@gm...> wrote: > Hi > I got this bug report (with proposed fix) from a pysparse user. It sounds > like it concerns some of the newer code (which I'm unfamiliar with). Could > you please take a look at it? > Thanks, > Roman > > Begin forwarded message: > > From: Andreea Georgiana Gane <and...@gm...> > Date: July 26, 2010 9:17:36 PM GMT+02:00 > To: ro...@ge... > Subject: ll_mat memory leak > > Hi, > I have recently downloaded the latest version of pysparse (pysparse-1.1.1) > and I want to report a memory leak in the ll_mat implementation. > For the following code: > for i in range(nt): > # get max value and index on each row > row = relTT[i,:] > the program crashed with MemoryError at about 13000th iteration (relTT was a > ll_mat matrix of size 63751 x 63751). > It seems the problem was in the getSubMatrix_FromList implementation, since > when "we have a mixture of index sets", some indexes were created (irow, > jcol) and the memory they occupied was never deallocated (lines 850-887 in > the ll_mat.c file). Freeing the allocated index/indexes before each return > of the function solved my problem. > Best regards, > Andreea > > ------------------------------------------------------------------------------ > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of 1ドル Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > _______________________________________________ > Pysparse-developers mailing list > Pys...@li... > https://lists.sourceforge.net/lists/listinfo/pysparse-developers > > -- Dominique
Hi I got this bug report (with proposed fix) from a pysparse user. It sounds like it concerns some of the newer code (which I'm unfamiliar with). Could you please take a look at it? Thanks, Roman Begin forwarded message: > From: Andreea Georgiana Gane <and...@gm...> > Date: July 26, 2010 9:17:36 PM GMT+02:00 > To: ro...@ge... > Subject: ll_mat memory leak > > Hi, > > I have recently downloaded the latest version of pysparse (pysparse-1.1.1) and I want to report a memory leak in the ll_mat implementation. > > For the following code: > for i in range(nt): > # get max value and index on each row > row = relTT[i,:] > the program crashed with MemoryError at about 13000th iteration (relTT was a ll_mat matrix of size 63751 x 63751). > > It seems the problem was in the getSubMatrix_FromList implementation, since when "we have a mixture of index sets", some indexes were created (irow, jcol) and the memory they occupied was never deallocated (lines 850-887 in the ll_mat.c file). Freeing the allocated index/indexes before each return of the function solved my problem. > > Best regards, > Andreea
It's perfect, thank you. (I'll separate it into two patches for the package.) -Adam On Thu, 2010年06月10日 at 23:22 +0200, Dominique Orban wrote: > Hi Adam, > > I attach a patch fixing the string exception issue. This patch also > adds a line in a documentation file (entirely unrelated and remarkably > inconsequential---feel free to ignore). > > Does this work for you? > > Cheers, > Dominique > > On Thu, Jun 10, 2010 at 9:55 PM, Adam C Powell IV <haz...@de...> wrote: > > Hello Dominique, > > > > Debian is supposed to be in freeze soon, so if we can get a fix in > > within the next couple of weeks that would be great. > > > > That said, it might be best for both Debian and PySparse if you can just > > generate a patch to fix this without needing to do a new release. > > > > Thanks, > > Adam > > > > On Thu, 2010年06月10日 at 09:08 +0200, Dominique Orban wrote: > >> Adam, > >> > >> Thank you for pointing this out. That seems to be the only string > >> exception in Pysparse and it has gone unnoticed for a long time. I > >> removed it and updated the source tree. > >> > >> We are in the process of merging major changes into trunk. The > >> directory layout is affected, as is the namespace. What is best for > >> the Deb package? Would you rather wait for the merge to complete and > >> have the new release, or have an updated release that includes this > >> simple fix? > >> > >> Dominique > >> > >> > >> On Thu, Jun 10, 2010 at 12:35 AM, Adam C Powell IV <haz...@de...> wrote: > >> > Hello PySparse group, > >> > > >> > Just received this bug report from the Debian bug tracking system. Are > >> > string exceptions important to pysparse? If so, this will be an issue > >> > for python 2.6 and beyond. > >> > > >> > -Adam > >> > > >> > -------- Forwarded Message -------- > >> >> From: Sandro Tosi <mo...@ra...> > >> >> Reply-to: Sandro Tosi <mo...@ra...>, > >> >> 585...@bu... > >> >> To: mai...@bu... > >> >> Subject: Bug#585330: python-sparse: Python string exceptions no more > >> >> allowed in Python 2.6 > >> >> Date: 2010年6月09日 22:19:39 +0000 > >> >> > >> >> Package: python-sparse > >> >> Version: 1.1-1+b1 > >> >> Severity: minor > >> >> User: deb...@li... > >> >> Usertags: python2.6 > >> >> > >> >> Hello, > >> >> One of the changes brought by Python 2.6 is the removal of string > >> >> exceptions, so they won't work in Python 2.6 (just a side note: they > >> >> were also buggy before, since they were not guaranteed to work > >> >> reliable even in <2.6); as an example: > >> >> > >> >> $ python2.5 -c "raise 'eggs'" > >> >> -c:1: DeprecationWarning: raising a string exception is deprecated > >> >> Traceback (most recent call last): > >> >> File "<string>", line 1, in <module> > >> >> eggs > >> >> > >> >> $ python2.6 -c "raise 'eggs'" > >> >> Traceback (most recent call last): > >> >> File "<string>", line 1, in <module> > >> >> TypeError: exceptions must be old-style classes or derived from BaseException, not str > >> >> > >> >> Since 2.6 is the planned default version for the upcoming new Debian > >> >> stable release, there are chances your package may be affected by this > >> >> change. > >> >> > >> >> We are not sure your package is impacted, since the exception raise > >> >> can be in a dead or very rare branch of the code, and so simply never > >> >> being executed. We would like to leverage your package maintainer > >> >> status and the relationship with upstream authors to inspect more > >> >> deeply the issue and act accordingly (that includes: making this bug > >> >> release critical, closing it as irrelevant, tagging it 'wontfix', or > >> >> whatever is appropriate). > >> >> > >> >> Jakub Wilk made the discovery of the problem and kindly prepared a > >> >> list [1] of all identified packages (downloaded on 2010年06月09日) along > >> >> with files & lines that triggered the pattern search. > >> >> > >> >> [1] http://people.debian.org/~morph/strexp/string-exceptions.lintian > >> >> > >> >> This mass-bug filing was announced at 2010年06月06日 on [2] (see the > >> >> thread and the references there). > >> >> > >> >> [2] http://lists.debian.org/debian-devel/2010/06/msg00097.html > >> >> > >> >> We do not consider the whole situation a stopper for the Python > >> >> transition to 2.6, except (of course) for those single bugs where > >> >> severity will be increased. > >> >> > >> >> Thanks in advance for your attention, > >> >> Sandro on behalf of debian-python -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/
Hi Adam, I attach a patch fixing the string exception issue. This patch also adds a line in a documentation file (entirely unrelated and remarkably inconsequential---feel free to ignore). Does this work for you? Cheers, Dominique On Thu, Jun 10, 2010 at 9:55 PM, Adam C Powell IV <haz...@de...> wrote: > Hello Dominique, > > Debian is supposed to be in freeze soon, so if we can get a fix in > within the next couple of weeks that would be great. > > That said, it might be best for both Debian and PySparse if you can just > generate a patch to fix this without needing to do a new release. > > Thanks, > Adam > > On Thu, 2010年06月10日 at 09:08 +0200, Dominique Orban wrote: >> Adam, >> >> Thank you for pointing this out. That seems to be the only string >> exception in Pysparse and it has gone unnoticed for a long time. I >> removed it and updated the source tree. >> >> We are in the process of merging major changes into trunk. The >> directory layout is affected, as is the namespace. What is best for >> the Deb package? Would you rather wait for the merge to complete and >> have the new release, or have an updated release that includes this >> simple fix? >> >> Dominique >> >> >> On Thu, Jun 10, 2010 at 12:35 AM, Adam C Powell IV <haz...@de...> wrote: >> > Hello PySparse group, >> > >> > Just received this bug report from the Debian bug tracking system. Are >> > string exceptions important to pysparse? If so, this will be an issue >> > for python 2.6 and beyond. >> > >> > -Adam >> > >> > -------- Forwarded Message -------- >> >> From: Sandro Tosi <mo...@ra...> >> >> Reply-to: Sandro Tosi <mo...@ra...>, >> >> 585...@bu... >> >> To: mai...@bu... >> >> Subject: Bug#585330: python-sparse: Python string exceptions no more >> >> allowed in Python 2.6 >> >> Date: 2010年6月09日 22:19:39 +0000 >> >> >> >> Package: python-sparse >> >> Version: 1.1-1+b1 >> >> Severity: minor >> >> User: deb...@li... >> >> Usertags: python2.6 >> >> >> >> Hello, >> >> One of the changes brought by Python 2.6 is the removal of string >> >> exceptions, so they won't work in Python 2.6 (just a side note: they >> >> were also buggy before, since they were not guaranteed to work >> >> reliable even in <2.6); as an example: >> >> >> >> $ python2.5 -c "raise 'eggs'" >> >> -c:1: DeprecationWarning: raising a string exception is deprecated >> >> Traceback (most recent call last): >> >> File "<string>", line 1, in <module> >> >> eggs >> >> >> >> $ python2.6 -c "raise 'eggs'" >> >> Traceback (most recent call last): >> >> File "<string>", line 1, in <module> >> >> TypeError: exceptions must be old-style classes or derived from BaseException, not str >> >> >> >> Since 2.6 is the planned default version for the upcoming new Debian >> >> stable release, there are chances your package may be affected by this >> >> change. >> >> >> >> We are not sure your package is impacted, since the exception raise >> >> can be in a dead or very rare branch of the code, and so simply never >> >> being executed. We would like to leverage your package maintainer >> >> status and the relationship with upstream authors to inspect more >> >> deeply the issue and act accordingly (that includes: making this bug >> >> release critical, closing it as irrelevant, tagging it 'wontfix', or >> >> whatever is appropriate). >> >> >> >> Jakub Wilk made the discovery of the problem and kindly prepared a >> >> list [1] of all identified packages (downloaded on 2010年06月09日) along >> >> with files & lines that triggered the pattern search. >> >> >> >> [1] http://people.debian.org/~morph/strexp/string-exceptions.lintian >> >> >> >> This mass-bug filing was announced at 2010年06月06日 on [2] (see the >> >> thread and the references there). >> >> >> >> [2] http://lists.debian.org/debian-devel/2010/06/msg00097.html >> >> >> >> We do not consider the whole situation a stopper for the Python >> >> transition to 2.6, except (of course) for those single bugs where >> >> severity will be increased. >> >> >> >> Thanks in advance for your attention, >> >> Sandro on behalf of debian-python > -- > GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 > > Engineering consulting with open source tools > http://www.opennovation.com/ > -- Dominique
Hello Dominique, Debian is supposed to be in freeze soon, so if we can get a fix in within the next couple of weeks that would be great. That said, it might be best for both Debian and PySparse if you can just generate a patch to fix this without needing to do a new release. Thanks, Adam On Thu, 2010年06月10日 at 09:08 +0200, Dominique Orban wrote: > Adam, > > Thank you for pointing this out. That seems to be the only string > exception in Pysparse and it has gone unnoticed for a long time. I > removed it and updated the source tree. > > We are in the process of merging major changes into trunk. The > directory layout is affected, as is the namespace. What is best for > the Deb package? Would you rather wait for the merge to complete and > have the new release, or have an updated release that includes this > simple fix? > > Dominique > > > On Thu, Jun 10, 2010 at 12:35 AM, Adam C Powell IV <haz...@de...> wrote: > > Hello PySparse group, > > > > Just received this bug report from the Debian bug tracking system. Are > > string exceptions important to pysparse? If so, this will be an issue > > for python 2.6 and beyond. > > > > -Adam > > > > -------- Forwarded Message -------- > >> From: Sandro Tosi <mo...@ra...> > >> Reply-to: Sandro Tosi <mo...@ra...>, > >> 585...@bu... > >> To: mai...@bu... > >> Subject: Bug#585330: python-sparse: Python string exceptions no more > >> allowed in Python 2.6 > >> Date: 2010年6月09日 22:19:39 +0000 > >> > >> Package: python-sparse > >> Version: 1.1-1+b1 > >> Severity: minor > >> User: deb...@li... > >> Usertags: python2.6 > >> > >> Hello, > >> One of the changes brought by Python 2.6 is the removal of string > >> exceptions, so they won't work in Python 2.6 (just a side note: they > >> were also buggy before, since they were not guaranteed to work > >> reliable even in <2.6); as an example: > >> > >> $ python2.5 -c "raise 'eggs'" > >> -c:1: DeprecationWarning: raising a string exception is deprecated > >> Traceback (most recent call last): > >> File "<string>", line 1, in <module> > >> eggs > >> > >> $ python2.6 -c "raise 'eggs'" > >> Traceback (most recent call last): > >> File "<string>", line 1, in <module> > >> TypeError: exceptions must be old-style classes or derived from BaseException, not str > >> > >> Since 2.6 is the planned default version for the upcoming new Debian > >> stable release, there are chances your package may be affected by this > >> change. > >> > >> We are not sure your package is impacted, since the exception raise > >> can be in a dead or very rare branch of the code, and so simply never > >> being executed. We would like to leverage your package maintainer > >> status and the relationship with upstream authors to inspect more > >> deeply the issue and act accordingly (that includes: making this bug > >> release critical, closing it as irrelevant, tagging it 'wontfix', or > >> whatever is appropriate). > >> > >> Jakub Wilk made the discovery of the problem and kindly prepared a > >> list [1] of all identified packages (downloaded on 2010年06月09日) along > >> with files & lines that triggered the pattern search. > >> > >> [1] http://people.debian.org/~morph/strexp/string-exceptions.lintian > >> > >> This mass-bug filing was announced at 2010年06月06日 on [2] (see the > >> thread and the references there). > >> > >> [2] http://lists.debian.org/debian-devel/2010/06/msg00097.html > >> > >> We do not consider the whole situation a stopper for the Python > >> transition to 2.6, except (of course) for those single bugs where > >> severity will be increased. > >> > >> Thanks in advance for your attention, > >> Sandro on behalf of debian-python -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/
Adam, Thank you for pointing this out. That seems to be the only string exception in Pysparse and it has gone unnoticed for a long time. I removed it and updated the source tree. We are in the process of merging major changes into trunk. The directory layout is affected, as is the namespace. What is best for the Deb package? Would you rather wait for the merge to complete and have the new release, or have an updated release that includes this simple fix? Dominique On Thu, Jun 10, 2010 at 12:35 AM, Adam C Powell IV <haz...@de...> wrote: > Hello PySparse group, > > Just received this bug report from the Debian bug tracking system. Are > string exceptions important to pysparse? If so, this will be an issue > for python 2.6 and beyond. > > -Adam > > -------- Forwarded Message -------- >> From: Sandro Tosi <mo...@ra...> >> Reply-to: Sandro Tosi <mo...@ra...>, >> 585...@bu... >> To: mai...@bu... >> Subject: Bug#585330: python-sparse: Python string exceptions no more >> allowed in Python 2.6 >> Date: 2010年6月09日 22:19:39 +0000 >> >> Package: python-sparse >> Version: 1.1-1+b1 >> Severity: minor >> User: deb...@li... >> Usertags: python2.6 >> >> Hello, >> One of the changes brought by Python 2.6 is the removal of string >> exceptions, so they won't work in Python 2.6 (just a side note: they >> were also buggy before, since they were not guaranteed to work >> reliable even in <2.6); as an example: >> >> $ python2.5 -c "raise 'eggs'" >> -c:1: DeprecationWarning: raising a string exception is deprecated >> Traceback (most recent call last): >> File "<string>", line 1, in <module> >> eggs >> >> $ python2.6 -c "raise 'eggs'" >> Traceback (most recent call last): >> File "<string>", line 1, in <module> >> TypeError: exceptions must be old-style classes or derived from BaseException, not str >> >> Since 2.6 is the planned default version for the upcoming new Debian >> stable release, there are chances your package may be affected by this >> change. >> >> We are not sure your package is impacted, since the exception raise >> can be in a dead or very rare branch of the code, and so simply never >> being executed. We would like to leverage your package maintainer >> status and the relationship with upstream authors to inspect more >> deeply the issue and act accordingly (that includes: making this bug >> release critical, closing it as irrelevant, tagging it 'wontfix', or >> whatever is appropriate). >> >> Jakub Wilk made the discovery of the problem and kindly prepared a >> list [1] of all identified packages (downloaded on 2010年06月09日) along >> with files & lines that triggered the pattern search. >> >> [1] http://people.debian.org/~morph/strexp/string-exceptions.lintian >> >> This mass-bug filing was announced at 2010年06月06日 on [2] (see the >> thread and the references there). >> >> [2] http://lists.debian.org/debian-devel/2010/06/msg00097.html >> >> We do not consider the whole situation a stopper for the Python >> transition to 2.6, except (of course) for those single bugs where >> severity will be increased. >> >> Thanks in advance for your attention, >> Sandro on behalf of debian-python > -- > GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 > > Engineering consulting with open source tools > http://www.opennovation.com/ > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > Pysparse-developers mailing list > Pys...@li... > https://lists.sourceforge.net/lists/listinfo/pysparse-developers > >
Hello PySparse group, Just received this bug report from the Debian bug tracking system. Are string exceptions important to pysparse? If so, this will be an issue for python 2.6 and beyond. -Adam -------- Forwarded Message -------- > From: Sandro Tosi <mo...@ra...> > Reply-to: Sandro Tosi <mo...@ra...>, > 585...@bu... > To: mai...@bu... > Subject: Bug#585330: python-sparse: Python string exceptions no more > allowed in Python 2.6 > Date: 2010年6月09日 22:19:39 +0000 > > Package: python-sparse > Version: 1.1-1+b1 > Severity: minor > User: deb...@li... > Usertags: python2.6 > > Hello, > One of the changes brought by Python 2.6 is the removal of string > exceptions, so they won't work in Python 2.6 (just a side note: they > were also buggy before, since they were not guaranteed to work > reliable even in <2.6); as an example: > > $ python2.5 -c "raise 'eggs'" > -c:1: DeprecationWarning: raising a string exception is deprecated > Traceback (most recent call last): > File "<string>", line 1, in <module> > eggs > > $ python2.6 -c "raise 'eggs'" > Traceback (most recent call last): > File "<string>", line 1, in <module> > TypeError: exceptions must be old-style classes or derived from BaseException, not str > > Since 2.6 is the planned default version for the upcoming new Debian > stable release, there are chances your package may be affected by this > change. > > We are not sure your package is impacted, since the exception raise > can be in a dead or very rare branch of the code, and so simply never > being executed. We would like to leverage your package maintainer > status and the relationship with upstream authors to inspect more > deeply the issue and act accordingly (that includes: making this bug > release critical, closing it as irrelevant, tagging it 'wontfix', or > whatever is appropriate). > > Jakub Wilk made the discovery of the problem and kindly prepared a > list [1] of all identified packages (downloaded on 2010年06月09日) along > with files & lines that triggered the pattern search. > > [1] http://people.debian.org/~morph/strexp/string-exceptions.lintian > > This mass-bug filing was announced at 2010年06月06日 on [2] (see the > thread and the references there). > > [2] http://lists.debian.org/debian-devel/2010/06/msg00097.html > > We do not consider the whole situation a stopper for the Python > transition to 2.6, except (of course) for those single bugs where > severity will be increased. > > Thanks in advance for your attention, > Sandro on behalf of debian-python -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/
Hi all A releases candidate of the pysparse-1.1 Windows installer for Python 2.6 is now available in the SF file download area. Feedback is welcome. -- Roman PS: There is also a new branch "1_1_x" for maintaining this release. On 12.04.2010 23:47, Roman Geus wrote: > Hi all > > FYI: I found a problem in the Windows build of the SuperLU module that > caused the wrong results. The uppercase symbols of the > double-precision BLAS routines (which are used in Windows) were mapped > to single-precision BLAS routines (in Cnames.h). > > Next, I work on the installer for Win32 and pysparse 1.1. Let's hope > that was the last serious Windows-related issue... > > Cheers, > Roman > > On 06.04.2010 23:00, Daniel Wheeler wrote: >> On Tue, Apr 6, 2010 at 4:45 PM, Roman Geus<rom...@gm...> wrote: >>>> Just use tags. If things need to be fixed you can create a branch from >>>> tags/version-1_1 (to branches/version-1_1). Tags should just be place >>>> holders. >>>> >>> Yes, right. But my windows build still produces wrong results in the >>> superlu >>> module. >> Ho-hum, then we are hamstrung at the moment. I'll try and figure out >> how to make pythonxy build statically, probably the most useful thing >> I can do for now. We just released a new version of fipy (version 2.1) >> so I need to deal with this issue. >> >
Hi all FYI: I found a problem in the Windows build of the SuperLU module that caused the wrong results. The uppercase symbols of the double-precision BLAS routines (which are used in Windows) were mapped to single-precision BLAS routines (in Cnames.h). Next, I work on the installer for Win32 and pysparse 1.1. Let's hope that was the last serious Windows-related issue... Cheers, Roman On 06.04.2010 23:00, Daniel Wheeler wrote: > On Tue, Apr 6, 2010 at 4:45 PM, Roman Geus<rom...@gm...> wrote: > >>> Just use tags. If things need to be fixed you can create a branch from >>> tags/version-1_1 (to branches/version-1_1). Tags should just be place >>> holders. >>> >>> >> Yes, right. But my windows build still produces wrong results in the superlu >> module. >> > Ho-hum, then we are hamstrung at the moment. I'll try and figure out > how to make pythonxy build statically, probably the most useful thing > I can do for now. We just released a new version of fipy (version 2.1) > so I need to deal with this issue. > >
Hi Daniel I just gave it another try. All I can say is that this Windows/superlu bug is quite serious: even 4-by-4 matrices produce completely wrong results. (1-by-1 matrices work though ;-) I this requires more time to investigate (and the time I can spare is unfortunately limited). Next I will try to call superlu from C just to check whether the problem is related in any way to Python. Regards, Roman On 06.04.2010 23:00, Daniel Wheeler wrote: > On Tue, Apr 6, 2010 at 4:45 PM, Roman Geus<rom...@gm...> wrote: > >>> Just use tags. If things need to be fixed you can create a branch from >>> tags/version-1_1 (to branches/version-1_1). Tags should just be place >>> holders. >>> >>> >> Yes, right. But my windows build still produces wrong results in the superlu >> module. >> > Ho-hum, then we are hamstrung at the moment. I'll try and figure out > how to make pythonxy build statically, probably the most useful thing > I can do for now. We just released a new version of fipy (version 2.1) > so I need to deal with this issue. > >
On Tue, Apr 6, 2010 at 4:45 PM, Roman Geus <rom...@gm...> wrote: >> Just use tags. If things need to be fixed you can create a branch from >> tags/version-1_1 (to branches/version-1_1). Tags should just be place >> holders. >> > > Yes, right. But my windows build still produces wrong results in the superlu > module. Ho-hum, then we are hamstrung at the moment. I'll try and figure out how to make pythonxy build statically, probably the most useful thing I can do for now. We just released a new version of fipy (version 2.1) so I need to deal with this issue. -- Daniel Wheeler
Hi Daniel On 06.04.2010 16:31, Daniel Wheeler wrote: > Hi, I've been struggling with trying to build pysparse version 1.1 for > python 2.6 on windows, both XP and 7. I'm using the mingw that comes > with pythonxy. I compiled blas and lapack from the source. I had to go > back a few versions of lapack in order for it to work with the gcc > (gfortran) that comes with pythonxy at least that seemed to work. > However, a whole bunch of compile flags get automatically added to the > pysparse compile step by mingw and I have no idea what they do. > Anyway, the long and the short is that I can build pysparse, but I > can't import any of the compiled modules without either getting a DLL > error (if lapack.dll and blas.dll are not in the DLL directory) or a > memory error (if lapack.dll and blas.dll are in the DLL directory). > > The weird thing is that I need both the .lib (or .a) versions as well > as the .dll versions of lapack and blas. > To my knowledge that's normal under Windows: if you link dynamically you need a .lib file (at compile time) and a .dll file. If you link statically you need only .lib files. > I realized that I'd stashed liblapack.a and libblas.a in the > tools/win32 of the pysparse dist for safe keeping. Anyway, I get the > DLL error when I use those because I don't have the dll versions of > those libraries. I need to figure out how to just include the blas and > lapack statically using pythonxy's mingw. This wasn't a problem in > previous releases of pythonxy. Anyway, I need to start asking > questions on the pythonxy list. > > In the mean time, is it possible that someone could get a python 2.6, > version 1.1 installer up (using a clean checkout of tags/version-1_1). > Thanks. > > On Mon, Mar 1, 2010 at 1:21 PM, Roman Geus<rom...@gm...> wrote: > > > >> 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. >> > Just use tags. If things need to be fixed you can create a branch from > tags/version-1_1 (to branches/version-1_1). Tags should just be place > holders. > Yes, right. But my windows build still produces wrong results in the superlu module. -- Roman
Hi, I've been struggling with trying to build pysparse version 1.1 for python 2.6 on windows, both XP and 7. I'm using the mingw that comes with pythonxy. I compiled blas and lapack from the source. I had to go back a few versions of lapack in order for it to work with the gcc (gfortran) that comes with pythonxy at least that seemed to work. However, a whole bunch of compile flags get automatically added to the pysparse compile step by mingw and I have no idea what they do. Anyway, the long and the short is that I can build pysparse, but I can't import any of the compiled modules without either getting a DLL error (if lapack.dll and blas.dll are not in the DLL directory) or a memory error (if lapack.dll and blas.dll are in the DLL directory). The weird thing is that I need both the .lib (or .a) versions as well as the .dll versions of lapack and blas. I realized that I'd stashed liblapack.a and libblas.a in the tools/win32 of the pysparse dist for safe keeping. Anyway, I get the DLL error when I use those because I don't have the dll versions of those libraries. I need to figure out how to just include the blas and lapack statically using pythonxy's mingw. This wasn't a problem in previous releases of pythonxy. Anyway, I need to start asking questions on the pythonxy list. In the mean time, is it possible that someone could get a python 2.6, version 1.1 installer up (using a clean checkout of tags/version-1_1). Thanks. On Mon, Mar 1, 2010 at 1:21 PM, Roman Geus <rom...@gm...> wrote: > 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. Just use tags. If things need to be fixed you can create a branch from tags/version-1_1 (to branches/version-1_1). Tags should just be place holders. -- Daniel Wheeler
On Mon, Mar 8, 2010 at 12:06 AM, David Billinghurst <dbc...@gm...> wrote: > I am trying out pysparse for the first time. I have a few patches to > the documentation for your consideration. Here is a patch against SVN > head for the first one. If you are interested I have a few more. > > The example "Solving a 2D Poisson System with SuperLU" in section 6.1.1 > works if you import poisson. Dear David, Yes by all means, please do send doc patches. I'm sure there is quite a bit of room for improvement. Thanks ! -- Dominique
I am trying out pysparse for the first time. I have a few patches to the documentation for your consideration. Here is a patch against SVN head for the first one. If you are interested I have a few more. The example "Solving a 2D Poisson System with SuperLU" in section 6.1.1 works if you import poisson. Index: Doc/pysparse/source/fact.rst =================================================================== --- Doc/pysparse/source/fact.rst (revision 136) +++ Doc/pysparse/source/fact.rst (working copy) @@ -97,10 +97,10 @@ The Python solution for this task looks as follows:: - from pysparse import spmatrix, superlu + from pysparse import spmatrix, superlu, poisson import numpy n = 100 - A = poisson2d_sym_blk(n) + A = poisson.poisson2d_sym_blk(n) b = numpy.ones(n*n) x = numpy.empty(n*n) LU = superlu.factorize(A.to_csr(), diag_pivot_thresh=0.0)