Comments on: A quick Cython introduction http://www.perrygeo.net/wordpress/?p=116 Matt Perry's random adventures with geospatial technology and other tangentially related topics Thu, 09 Sep 2010 16:08:15 +0000 http://wordpress.org/?v=2.3.3 By: nick http://www.perrygeo.net/wordpress/?p=116#comment-48056 nick Thu, 29 Jul 2010 18:09:51 +0000 http://www.perrygeo.net/wordpress/?p=116#comment-48056 @tom "as long as the python install is 32 bit": ehem, that's not the same as supporting 64bit... sorry, in my opinion requiring users to change their environment to accommodate a specific software makes that software unsuitable in a production environment. @tom
“as long as the python install is 32 bit”:
ehem, that’s not the same as supporting 64bit… sorry, in my opinion requiring users to change their environment to accommodate a specific software makes that software unsuitable in a production environment.

]]> By: Alex Liberzon http://www.perrygeo.net/wordpress/?p=116#comment-47907 Alex Liberzon Mon, 05 Apr 2010 14:01:30 +0000 http://www.perrygeo.net/wordpress/?p=116#comment-47907 I get an error trying to compile the c3.pyx. Both c1.pyx and c2.pyx worked fine, but not c3.pyx. I get an error trying to compile the c3.pyx. Both c1.pyx and c2.pyx worked fine, but not c3.pyx.

]]> By: tim http://www.perrygeo.net/wordpress/?p=116#comment-47379 tim Sun, 24 May 2009 15:24:53 +0000 http://www.perrygeo.net/wordpress/?p=116#comment-47379 @ssam Actually, Psyco has been working on intel/mac since 2007 and works just fine on x86_64 as long as the python install is 32 bit. (Always google before you post.) @ssam

Actually, Psyco has been working on intel/mac since 2007 and works just fine on x86_64 as long as the python install is 32 bit.

(Always google before you post.)

]]> By: navie http://www.perrygeo.net/wordpress/?p=116#comment-47279 navie Thu, 06 Nov 2008 02:52:00 +0000 http://www.perrygeo.net/wordpress/?p=116#comment-47279 Hi , perrygeo. How about your learning of cython? I wanna ask u a question.. I noticed that the type of value that your c function returns to your .pyx def function is basic type(like int,double,etc.),and it works well. However,now my c function returns a pointer p with the type (double *),which points to a list,and the p's memory is allocated by malloc function. If I want to use the data stored in list p in my .pyx def function ,what should i do? Now I've tried to add the data in list p into a python list,but it doesn't work and give the following error information:can't convert to python object.. Anything can i do? Hi , perrygeo. How about your learning of cython? I wanna ask u a question..
I noticed that the type of value that your c function returns to your .pyx def function is basic type(like int,double,etc.),and it works well.
However,now my c function returns a pointer p with the type (double *),which points to a list,and the p’s memory is allocated by malloc function. If I want to use the data stored in list p in my .pyx def function ,what should i do? Now I’ve tried to add the data in list p into a python list,but it doesn’t work and give the following error information:can’t convert to python object.. Anything can i do?

]]> By: Cython: Yet another Python optimizer « Rudimentary Art of Programming & Development http://www.perrygeo.net/wordpress/?p=116#comment-47276 Cython: Yet another Python optimizer « Rudimentary Art of Programming & Development Sun, 02 Nov 2008 22:19:10 +0000 http://www.perrygeo.net/wordpress/?p=116#comment-47276 [...] Using Python to calculate great_circle circumference, then optimize the same function with Cython [...] […] Using Python to calculate great_circle circumference, then optimize the same function with Cython […]

]]> By: Cython: Yet another Python optimizerIns « Rudimentary Art of Programming & Development http://www.perrygeo.net/wordpress/?p=116#comment-47275 Cython: Yet another Python optimizerIns « Rudimentary Art of Programming & Development Sun, 02 Nov 2008 22:18:19 +0000 http://www.perrygeo.net/wordpress/?p=116#comment-47275 [...] Using Python to calculate great_circle circumference, then optimize the same function with Cython [...] […] Using Python to calculate great_circle circumference, then optimize the same function with Cython […]

]]> By: Gabriel http://www.perrygeo.net/wordpress/?p=116#comment-47265 Gabriel Tue, 30 Sep 2008 03:27:29 +0000 http://www.perrygeo.net/wordpress/?p=116#comment-47265 Great writeup would you be willing to have it included in the Cython docs? We can add you as an author :-) Gabriel Great writeup would you be willing to have it included in the Cython docs? We can add you as an author :-)

Gabriel

]]> By: ssam http://www.perrygeo.net/wordpress/?p=116#comment-47216 ssam Mon, 14 Jul 2008 13:17:44 +0000 http://www.perrygeo.net/wordpress/?p=116#comment-47216 @psyco fans but psyco only works on x86, not even x86 64bit. @psyco fans
but psyco only works on x86, not even x86 64bit.

]]> By: perrygeo http://www.perrygeo.net/wordpress/?p=116#comment-47086 perrygeo Sun, 25 May 2008 23:55:43 +0000 http://www.perrygeo.net/wordpress/?p=116#comment-47086 @Shawn I use vim for almost everything these days. Thanks for the heads up on Clojure; i'll have to check that out. @Shawn
I use vim for almost everything these days. Thanks for the heads up on Clojure; i’ll have to check that out.

]]> By: Shawn Fumo http://www.perrygeo.net/wordpress/?p=116#comment-47085 Shawn Fumo Sun, 25 May 2008 23:52:10 +0000 http://www.perrygeo.net/wordpress/?p=116#comment-47085 Thanks a lot for this posting. I'm working on a program involving real-time knot simulation and had just re-implemented part of it in Cython. That produced great results (brought a calculation down from 5 to 0.2), but I was still using Python's sqrt function. Taking your advice, I moved over to C's sqrtf, which brought it down to 0.04! I have to say I'm glad for Cython's existance. I had rewrite a lot of things (much less elegant.. grr) to make it efficient, but it still beats writing in pure C. Knuth's quote is a good reminder, though. I may go back and make a couple of things clearer again now that I have a bit more of a margin to work with. BTW, what editor are you using for your Python/Cython coding? Also, I noticed your post on parallel programming a while back. Another thing you may want to check out is Clojure, a relatively new language built on the JVM. Two of it's strong points is concurrency and interoperability with Java libraries. The creator gave a talk here recently and I was pretty impressed, though I haven't had a chance to fuss with it myself yet. Thanks a lot for this posting. I’m working on a program involving real-time knot simulation and had just re-implemented part of it in Cython. That produced great results (brought a calculation down from 5 to 0.2), but I was still using Python’s sqrt function. Taking your advice, I moved over to C’s sqrtf, which brought it down to 0.04!

I have to say I’m glad for Cython’s existance. I had rewrite a lot of things (much less elegant.. grr) to make it efficient, but it still beats writing in pure C. Knuth’s quote is a good reminder, though. I may go back and make a couple of things clearer again now that I have a bit more of a margin to work with.

BTW, what editor are you using for your Python/Cython coding?

Also, I noticed your post on parallel programming a while back. Another thing you may want to check out is Clojure, a relatively new language built on the JVM. Two of it’s strong points is concurrency and interoperability with Java libraries. The creator gave a talk here recently and I was pretty impressed, though I haven’t had a chance to fuss with it myself yet.

]]>