[Numpy-discussion] Thoughts on persistence/object tracking in scientific code

Olivier Grisel olivier.grisel@ensta....
Mon Dec 22 19:10:50 CST 2008

Interesting topic indeed. I think I have been hit with similar problems on
toy experimental scripts. So far the solution was always adhoc FS caches of
numpy arrays with manual filename management. Maybe the first step for
designing a generic solution would be to list some representative yet simple
enough use cases with real sample python code so as to focus on concrete
matters and avoid over engineering a general solution for philosophical


On Dec 23, 2008 1:40 AM, "Gael Varoquaux" <gael.varoquaux@normalesup.org>


This mailing list is full of people spending their time writing
non-trivial numerical code. This is why I would like to share my
interrogations on a code smell that I notice a lot in my numerical code
that revolves around persisting to disk often, and the mess that results.
It is a bit hard to describe and it has been on my mind for a couple of
months. I have finally written a blog post in an attempt to share my
thoughts: http://gael-varoquaux.info/blog/?p=83

Pointing to a blog post on a mailing list seems to me almost rude, and I
hope you'll forgive, but I'd love any feedback. It seems to me I am
missing a pattern, or simply some insight on a recurrent problem.


Numpy-discussion mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://projects.scipy.org/pipermail/numpy-discussion/attachments/20081223/e6f22759/attachment.html 

More information about the Numpy-discussion mailing list