<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;DE8CSHw7eyp7ImA9WxNVE08.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990</id><updated>2009-10-23T17:41:09.203-02:00</updated><title>Python in Science</title><subtitle type="html">Scientific adventures with Python.</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://pyinsci.blogspot.com/" /><link rel="hub" href="http://pubsubhubbub.appspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>49</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><link rel="self" href="http://feeds.feedburner.com/PythonInScience" type="application/atom+xml" /><feedburner:emailServiceId>PythonInScience</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><entry gd:etag="W/&quot;A0IBRHwyfSp7ImA9WxNVEk0.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-3430892466512580152</id><published>2009-10-22T09:05:00.001-02:00</published><updated>2009-10-22T09:05:55.295-02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-22T09:05:55.295-02:00</app:edited><title>ASCII Histograms</title><summary>I have recently come across an interestng problem while working on my random variable implementation for BIP. Any type in Python is expected to have a __str__(self) method which returns an adequate and expressive string representation of the object. Well, as far as I could think, the most straightforward representation of a random variable is its probability distribution. Probability </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/3430892466512580152/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=3430892466512580152" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/3430892466512580152?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/3430892466512580152?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/xmZNRFfsBtg/ascii-histograms.html" title="ASCII Histograms" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">4</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2009/10/ascii-histograms.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A04FR3kyeyp7ImA9WxNXEk8.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-1275895338508074330</id><published>2009-09-29T10:11:00.001-03:00</published><updated>2009-09-29T10:11:56.793-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-29T10:11:56.793-03:00</app:edited><title>The Internet Manifesto</title><summary>This document is a must read (see link at the end).I want to add my own items to it:1. Net Neutrality is not only protecting Internet content provider corporations' profitsWe need to defend net neutrality in a way which goes beyond what is currently done: We need to establish fixed ip addresss for every private individual so that publishing rights don't have to be gatekeeped by large corporations</summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/1275895338508074330/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=1275895338508074330" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/1275895338508074330?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/1275895338508074330?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/TPwteFiOTvc/internet-manifesto.html" title="The Internet Manifesto" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">3</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2009/09/internet-manifesto.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0QASHk5fSp7ImA9WxNXEU4.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-2487339663708522536</id><published>2009-09-28T06:49:00.001-03:00</published><updated>2009-09-28T06:49:09.725-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-28T06:49:09.725-03:00</app:edited><title>Python(x,y) A Scientific Python Distribution</title><summary>I recently came across, this interesting, opensource Python Scientific Distribution for Windows. I normally don't pay too much attention to windows tools, but it's good to have something to recommend to windows users when you want them to try out some Python code. For Linux users, it's not really relevant, because we all have powerfull package managers to help us get most Python packages </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/2487339663708522536/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=2487339663708522536" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/2487339663708522536?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/2487339663708522536?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/XHLMf9vl800/pythonxy-scientific-python-distribution.html" title="Python(x,y) A Scientific Python Distribution" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2009/09/pythonxy-scientific-python-distribution.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0IFRHY8cSp7ImA9WxNQF0U.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-7432476178969952020</id><published>2009-09-24T07:51:00.001-03:00</published><updated>2009-09-24T07:51:55.879-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-24T07:51:55.879-03:00</app:edited><title>Scientific Python Group at LinkedIn</title><summary>I have just created a Scientific Python Group at LinkedIn. I was actually surprised that there wasn't one already.Python is quickly becoming a major tool in scientific computing and we should all do our best to advertise its capabilities.referente a: Scientific Python Group | LinkedIn (ver no Google Sidewiki)</summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/7432476178969952020/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=7432476178969952020" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/7432476178969952020?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/7432476178969952020?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/3wdmWF4nRqA/scientific-python-group-at-linkedin.html" title="Scientific Python Group at LinkedIn" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2009/09/scientific-python-group-at-linkedin.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0cBRHs7eSp7ImA9WxNQEk0.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-3432521621967114419</id><published>2009-09-17T11:41:00.008-03:00</published><updated>2009-09-17T12:24:15.501-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-17T12:24:15.501-03:00</app:edited><title>Violin Plot with Matplotlib</title><summary>One of the things I sorely missed from matplotlib for a very long time,  was a violin plot implementation. Many a time, I thought about implementing one myself, but never found the time.Today, browsing through Matplotlib's documentation, I found the recently added fill_betweenx function. Finally it seemed to have become a piece of cake to implement a violin plot. I Googled for violin plot and </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/3432521621967114419/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=3432521621967114419" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/3432521621967114419?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/3432521621967114419?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/3eJwjQw5_AM/violin-plot-with-matplotlib.html" title="Violin Plot with Matplotlib" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/_lq_qzMa71Ns/SrJSildeV9I/AAAAAAAAAlw/1z16wN46WZc/s72-c/violin.png" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">4</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2009/09/violin-plot-with-matplotlib.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Ck4AQXw9fyp7ImA9WxNRFkU.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-1939601755298551830</id><published>2009-09-11T11:52:00.002-03:00</published><updated>2009-09-11T11:55:40.267-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-11T11:55:40.267-03:00</app:edited><title>Why Python</title><summary>I recently came across a repository of jewels in the form of the unpublished manuscripts of E.W. Dijkstra. I just finished reading one entitled "Some Meditations on Advanced Programming". It is amazingly well written and still so relevant to present-day computer science, that I recommend anyone with at least a passing interest on the subject to read it. I was pleasantly surprised to find in the </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/1939601755298551830/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=1939601755298551830" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/1939601755298551830?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/1939601755298551830?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/NRAFOg9C_pU/why-python.html" title="Why Python" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2009/09/why-python.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0QDRXY9fCp7ImA9WxNSGEQ.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-3567186964742670572</id><published>2009-09-02T10:27:00.003-03:00</published><updated>2009-09-02T10:49:34.864-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-02T10:49:34.864-03:00</app:edited><title>New-style String Formatting and LaTeX</title><summary>The recommended new way (since 2.6) of doing string formating in Python is to use the format method of string objects instead of the % operator and %s (and variants) placemarks.I decided to check it out to generate some LaTeX tables programatically. Bad Idea. the  method expects placemarks like this: "some string {key}".format(key=123) and that is a big problem when formatting LaTeX strings. </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/3567186964742670572/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=3567186964742670572" title="5 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/3567186964742670572?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/3567186964742670572?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/QngeanAfUdA/new-style-string-formatting-and-latex.html" title="New-style String Formatting and LaTeX" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">5</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2009/09/new-style-string-formatting-and-latex.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D08EQXk9fSp7ImA9WxJUEkg.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-780597518430419776</id><published>2009-07-10T16:28:00.002-03:00</published><updated>2009-07-10T16:56:40.765-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-10T16:56:40.765-03:00</app:edited><title>Chrome OS and Google World Domination</title><summary>The web platform is starting to get annoying in its attempt to re-invent and re-create everything that previously existed in the Desktop space.Finally, Desktop developers are beginning to wake up to this problem.For years, browser-developing companies have tried to turn the Browser into an operating-system-like autonomous system. While the rest of us were trying to figure out how to get our </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/780597518430419776/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=780597518430419776" title="11 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/780597518430419776?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/780597518430419776?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/7ANRMF1u9U0/chrome-os-and-google-world-domination.html" title="Chrome OS and Google World Domination" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">11</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2009/07/chrome-os-and-google-world-domination.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUUBSXk5fCp7ImA9WxVaGUo.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-8315921067162463268</id><published>2009-04-17T09:29:00.003-03:00</published><updated>2009-04-17T10:00:58.724-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-04-17T10:00:58.724-03:00</app:edited><title>Parallel version of the Gillespie solver</title><summary>A few months back I blogged about my implementation of the Gillespie SSA algorithm for solving stochastic differential equations. I have now improved the code allowing for parallel execution on SMP systems. If you don't know what this is all about, please refer the the first post for a quick intro to what a stochastic differential equation is and what it means to numerically solve a system of </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/8315921067162463268/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=8315921067162463268" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/8315921067162463268?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/8315921067162463268?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/nAgdR0qtv98/parallel-version-of-gillespie-solver.html" title="Parallel version of the Gillespie solver" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2009/04/parallel-version-of-gillespie-solver.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0UERnk8fSp7ImA9WxVVEkg.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-8779243871180387187</id><published>2009-03-05T08:46:00.002-03:00</published><updated>2009-03-05T09:13:27.775-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-03-05T09:13:27.775-03:00</app:edited><title>Fixing Rkward startup problems</title><summary>Rkward is a  Nice IDE project for R based on standard KDE components such as Kate, etc.However, most people wanting to try it (version 0.5b) have come across a startup bug, where Rkward says it can't find some plugins, resulting in a useless interface since some plugins are required for proper operation.After spending quite some time looking for the solution to this problem, and finding it, I </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/8779243871180387187/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=8779243871180387187" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/8779243871180387187?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/8779243871180387187?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/wbjRUmTXjcQ/fixing-rkward-startup-problems.html" title="Fixing Rkward startup problems" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2009/03/fixing-rkward-startup-problems.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CU8NQHs_cCp7ImA9WxVWF04.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-7046392107359800788</id><published>2009-02-27T08:00:00.005-03:00</published><updated>2009-02-27T08:24:51.548-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-02-27T08:24:51.548-03:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="simulations" /><category scheme="http://www.blogger.com/atom/ns#" term="Matplotlib" /><category scheme="http://www.blogger.com/atom/ns#" term="python" /><category scheme="http://www.blogger.com/atom/ns#" term="Gnuplot" /><category scheme="http://www.blogger.com/atom/ns#" term="numerical" /><category scheme="http://www.blogger.com/atom/ns#" term="plotting" /><title>Real-time Plotting from Numerical Simulations</title><summary>Complex numerical simulations usually take a long time to run while using full CPU(s). If something goes wrong during such a run, we generally only find out in the end of the run when the traces of what went wrong are no longer available, debugging such codes is also not an easy task, because the code gets even slower running through the debugger, and when we don't know where the code is going to</summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/7046392107359800788/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=7046392107359800788" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/7046392107359800788?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/7046392107359800788?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/AIfhZ_zy68M/real-time-plotting-from-numerical.html" title="Real-time Plotting from Numerical Simulations" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">3</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2009/02/real-time-plotting-from-numerical.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEQMRXo-fCp7ImA9WxVWF04.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-8629503151553509783</id><published>2009-02-27T07:06:00.002-03:00</published><updated>2009-02-27T07:59:44.454-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-02-27T07:59:44.454-03:00</app:edited><title>Usage pattern for multiprocessing</title><summary>I have found myself using multiprocessing more and more these days, especially since it has been backported to Python 2.5.x.I can no longer remember what was the last computer I owned, which had a single core/processor. Multiprocessing make me much happier as I know I can milk my hardware for all it has to offer. I numpy, scipy and related packages find ways to build  parallelization into their </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/8629503151553509783/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=8629503151553509783" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/8629503151553509783?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/8629503151553509783?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/NGIKmxWKHo8/usage-pattern-for-multiprocessing.html" title="Usage pattern for multiprocessing" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">4</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2009/02/usage-pattern-for-multiprocessing.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0IGRnwyfyp7ImA9WxVWEE4.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-2331006322845971006</id><published>2009-02-19T06:45:00.004-03:00</published><updated>2009-02-19T07:32:07.297-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-02-19T07:32:07.297-03:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="collaborative" /><category scheme="http://www.blogger.com/atom/ns#" term="Web2.0" /><category scheme="http://www.blogger.com/atom/ns#" term="science" /><title>Computer Supported Collaborative Science</title><summary>The title of this post is intentionally the same as this one by  Greg Wilson. His post brings up the important issue of the lack of efficient collaborative science tools, and asks for opinions on the subject. Here is my personal view:Though science has invented collaborative open-source development centuries ago, it is currently not the best example of such practices, being surpassed on many </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/2331006322845971006/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=2331006322845971006" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/2331006322845971006?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/2331006322845971006?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/GeBV1rqizJE/computer-supported-collaborative.html" title="Computer Supported Collaborative Science" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">4</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2009/02/computer-supported-collaborative.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0MGQ306eip7ImA9WxRWGE0.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-4257865192136796926</id><published>2008-10-30T15:04:00.020-02:00</published><updated>2008-11-04T12:37:02.312-02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-11-04T12:37:02.312-02:00</app:edited><title>Fast(?) Gillespies Direct Algorithm  in Python</title><summary>Today I took the day off to implement the Gillespie SSA algorithm. For those of you who have never heard of it is a solver for stochastic  equations. There is no implementation of it in Python (to my knowledge) and the only  other easily accessible implementation I found was the one on the GillespieSSA package for R.To help the unfamiliar to understand the application and relevance of this </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/4257865192136796926/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=4257865192136796926" title="9 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/4257865192136796926?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/4257865192136796926?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/iF6TiVSXzHU/fast-gillespies-direct-algorithm-in.html" title="Fast(?) Gillespies Direct Algorithm  in Python" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">9</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2008/10/fast-gillespies-direct-algorithm-in.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkYHQH09eSp7ImA9WxRQEkk.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-7290758227372111857</id><published>2008-10-05T18:47:00.002-03:00</published><updated>2008-10-05T19:02:11.361-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-10-05T19:02:11.361-03:00</app:edited><title>Further Bayesian adventures</title><summary>I am quite busy at the moment. But I recently got some inspiration for pushing forward with the development of my object-oriented Bayesian-inference package. The inspiration came in the form of the recently released R-packages rv By Kerman and Gelman. A technical report by the same authors provided me with the initial idea for starting this package. The rv package implements part of what intend </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/7290758227372111857/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=7290758227372111857" title="6 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/7290758227372111857?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/7290758227372111857?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/yXi6bKEZRUQ/further-bayesian-adventures.html" title="Further Bayesian adventures" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">6</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2008/10/further-bayesian-adventures.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CE4EQ3k8fCp7ImA9WxRRF0o.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-321726219128447464</id><published>2008-09-30T07:15:00.007-03:00</published><updated>2008-09-30T08:08:22.774-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-09-30T08:08:22.774-03:00</app:edited><title>Python Multi-processing</title><summary>In this era of multiple cores everywhere, it kind of makes me nervous to see one of my computer cores siting idle as the other crunches away at some numerical simulation. Running heavy numerical simulations is the bread and butter of my work, so I am always on the lookout for ways to extract as much  computational juice as I can from my CPUs.Over last couple of years I have played different </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/321726219128447464/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=321726219128447464" title="12 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/321726219128447464?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/321726219128447464?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/983Vgaeyqqo/python-processing.html" title="Python Multi-processing" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">12</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2008/09/python-processing.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Ck8HSHY7cSp7ImA9WxdbEEQ.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-2029511468968559415</id><published>2008-08-07T03:33:00.001-03:00</published><updated>2008-08-07T03:33:59.809-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-08-07T03:33:59.809-03:00</app:edited><title>AppEngine and Google Base</title><summary>My experiments with AppEngine keep expanding. One thing they got rightwas the incentive to use other google services through google dataAPIs also known as GData.The first step towards that was forcing us to use Authsub by defaultin appEngine.  Noticing that, I am  thinking about taking advantage ofthat to aleviate the usage of the tiny storage quota offered by Googleat AppEngine.I'll post more </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/2029511468968559415/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=2029511468968559415" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/2029511468968559415?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/2029511468968559415?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/d29a3PxSZDo/appengine-and-google-base.html" title="AppEngine and Google Base" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2008/08/appengine-and-google-base.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkMMQ3Y-fyp7ImA9WxdUGUo.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-9163511536548895626</id><published>2008-08-05T17:46:00.004-03:00</published><updated>2008-08-05T18:08:02.857-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-08-05T18:08:02.857-03:00</app:edited><title>Editra: a Great New Python Editor</title><summary>Editra is a relatively new (at least for me) text editor written in Python/GTK.I have been working extensively with it recently, and although I am not ready to leave behind my currently favorite Python IDE, Eric, Editra doesn't make me miss it too much. One thing that it does that Eric still does not, even though it could, is to provide a code browser for a source file which is not part of a </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/9163511536548895626/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=9163511536548895626" title="6 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/9163511536548895626?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/9163511536548895626?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/y1Juyhjz4Kg/editra-great-new-python-editor.html" title="Editra: a Great New Python Editor" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">6</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2008/08/editra-great-new-python-editor.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEMBQ3Y8cCp7ImA9WxdUGEo.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-8262312084308577064</id><published>2008-08-04T15:46:00.002-03:00</published><updated>2008-08-04T16:00:52.878-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-08-04T16:00:52.878-03:00</app:edited><title>Google AppEngine</title><summary>I have spent quite a lot of time lately developing for google appengine. I must admit that it is really a great package, especially considering that is still in beta.The development cycle is a breeze.  One thing I would add though, would be a decent source code management system. This could take the form of an integration with google code. The appEngine dashboard does a good job keeping track of </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/8262312084308577064/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=8262312084308577064" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/8262312084308577064?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/8262312084308577064?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/pFYkxCSJvvM/google-appengine.html" title="Google AppEngine" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2008/08/google-appengine.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0IEQH45eSp7ImA9WxdVGEk.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-1473946891958487446</id><published>2008-07-23T17:21:00.002-03:00</published><updated>2008-07-23T17:38:21.021-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-07-23T17:38:21.021-03:00</app:edited><title>Metamodellers</title><summary>I am rather busy at the moment pushing my new company forward. Yes, for those of you who don't know yet, I have just started up my own company.It has been very rewarding so far, even considering all the hassle of tasks such as  fund-seeking, registering the company, creating a website, develop the products, and making sure that everything work. Wow!, it's been a great challenge.The focus of this </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/1473946891958487446/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=1473946891958487446" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/1473946891958487446?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/1473946891958487446?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/awuqEW0ZWYQ/metamodellers.html" title="Metamodellers" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2008/07/metamodellers.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkYEQ30zeip7ImA9WxdTFk8.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-8620549465566736024</id><published>2008-05-12T15:45:00.003-03:00</published><updated>2008-05-12T16:21:42.382-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-05-12T16:21:42.382-03:00</app:edited><title>Object-Oriented Bayesian Inference II</title><summary>A while ago, I blogged about a little piece of code I had written as an example for my book.Back then, it was a fun exercise for me, but it was clearly unfinished (and it still is) but worth as an example of how to model a mathematical object, a Bayesian random variate, as a python class.Despite its simplicity and incompleteness, that example, still attracts attention, and people contact me </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/8620549465566736024/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=8620549465566736024" title="6 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/8620549465566736024?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/8620549465566736024?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/9dTfZiFcznY/object-oriented-bayesian-inference-ii.html" title="Object-Oriented Bayesian Inference II" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">6</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2008/05/object-oriented-bayesian-inference-ii.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0YMQHg7fip7ImA9WxZbEU8.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-1995112802870625685</id><published>2008-04-13T19:17:00.000-03:00</published><updated>2008-04-13T19:19:41.606-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-04-13T19:19:41.606-03:00</app:edited><title>New Job</title><summary>It's been a while since i last posted about python in science. I apologize to my readers, but it has been a very busy couple of months. As a matter of fact it still is (i am writing this on my cell phone while I comute), but let's get to the point.The reason for this crazyer than usual months is that I switched jobs.  I have been offered a job in a private research company called Intelekto. It is</summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/1995112802870625685/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=1995112802870625685" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/1995112802870625685?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/1995112802870625685?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/JzisWFqi9Kc/new-job.html" title="New Job" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2008/04/new-job.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUUEQX07eCp7ImA9WxZWFE8.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-6088046317094481665</id><published>2008-03-03T20:27:00.004-03:00</published><updated>2008-03-13T12:46:40.300-03:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-03-13T12:46:40.300-03:00</app:edited><title>Incredible Video of intracellular molecular dynamics</title><summary>I just found this incredible video (animation) depicting what goes on continually within our own cells. Reminds me of why I became a biologist.We should never cease to let ourselves be amazed by the great machine that is the living cell and the organisms they are part of. Enjoy!</summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/6088046317094481665/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=6088046317094481665" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/6088046317094481665?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/6088046317094481665?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/dUPriFewNFQ/incredible-video-of-intracellular.html" title="Incredible Video of intracellular molecular dynamics" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">3</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2008/03/incredible-video-of-intracellular.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0EDRn06eip7ImA9WB9UEkk.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-2433885991328627613</id><published>2007-12-09T22:01:00.000-02:00</published><updated>2007-12-09T22:14:37.312-02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-12-09T22:14:37.312-02:00</app:edited><title>Free ZODB!</title><summary>I am a big fan of ZODB and use it standalone (without Zope) on many projects of mine. One of the things I miss, is a community around it. I don't care much about Zope (though I admire it as a project) and have not being able  to find  a ZODB focused community. Is there one?I think ZODB is a great product, the best Object-Oriented database for Python. It's a shame it does not have an active  and </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/2433885991328627613/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=2433885991328627613" title="7 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/2433885991328627613?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/2433885991328627613?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/C4CPkPAoA00/free-zodb.html" title="Free ZODB!" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">7</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2007/12/free-zodb.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUYDQnk8fSp7ImA9WB9XEkU.&quot;"><id>tag:blogger.com,1999:blog-840127493134277990.post-6287690841379119596</id><published>2007-11-05T13:13:00.000-02:00</published><updated>2007-11-05T15:19:33.775-02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-11-05T15:19:33.775-02:00</app:edited><title>New release of Epigrass coming soon!</title><summary>I have finally found a justification to work on Epigrass again. I am publishing a paper on it and I want to have a fresh version out by the time he paper goes to press. It was a good thing since my wish list for the next release was becoming too long.So here are the the things I have done so far and some I expect to get done before the new release:Port to Qt4: Done. Not as hard as I suspected it </summary><link rel="replies" type="application/atom+xml" href="http://pyinsci.blogspot.com/feeds/6287690841379119596/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=840127493134277990&amp;postID=6287690841379119596" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/6287690841379119596?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/840127493134277990/posts/default/6287690841379119596?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/PythonInScience/~3/D6tWledH7LI/new-release-of-epigrass-coming-soon.html" title="New release of Epigrass coming soon!" /><author><name>Flavio Coelho</name><uri>http://www.blogger.com/profile/02885581033966597420</uri><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="13882759215373973609" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total><feedburner:origLink>http://pyinsci.blogspot.com/2007/11/new-release-of-epigrass-coming-soon.html</feedburner:origLink></entry></feed>
