Mercurial > pylearn
comparison doc/v2_planning/architecture.txt @ 1129:40c1461ce9ef
architecture: Minor typo fix
author | Olivier Delalleau <delallea@iro> |
---|---|
date | Wed, 15 Sep 2010 12:09:22 -0400 |
parents | 7ba1854f03e7 |
children | ae5ba6206fd3 |
comparison
equal
deleted
inserted
replaced
1128:03b41a79bd60 | 1129:40c1461ce9ef |
---|---|
129 | 129 |
130 In this approach we would provide a proxy for asynchronous execution | 130 In this approach we would provide a proxy for asynchronous execution |
131 (e.g. "pylearn.call(fn, args, kwargs, backend=default_backend)"), which would | 131 (e.g. "pylearn.call(fn, args, kwargs, backend=default_backend)"), which would |
132 come with constraints on what fn, args, and kwargs can be. Specifically, they | 132 come with constraints on what fn, args, and kwargs can be. Specifically, they |
133 must be picklable, and there are benefits (e.g. automatic function call caching) | 133 must be picklable, and there are benefits (e.g. automatic function call caching) |
134 associated with their being hashable as well. | 134 associated with them being hashable as well. |
135 | 135 |
136 | 136 |
137 | 137 |