On Oct 28, 2006, at 5:10 PM, René J.V. Bertin wrote:
> I don't want to keep hammering on the possible interest of python in
> this context... but have you seen this?
>
> http://ipython.scipy.org/moin/Parallel_Computing
>
> I know, not exactly the same as multithreading ;)
>
Um - have you seen th
I don't want to keep hammering on the possible interest of python in
this context... but have you seen this?
http://ipython.scipy.org/moin/Parallel_Computing
I know, not exactly the same as multithreading ;)
__
R-devel@r-project.org mailing list
https:
On Fri, Oct 20, 2006 at 04:11:11PM +0200, Ren? J.V. Bertin wrote:
> Since Python has been mentioned in this context: Could not Python's
> threading model and implementation serve as a guideline?
Why would you want to do that? Does that model have some particular
synergy with R's design or curre
On Fri, 20 Oct 2006, René J.V. Bertin wrote:
But it still remains to be seen whether the extra work to introduce
threads is warranted. Will people actually use them in R and will it
have a significant impact on the computations or simply make writing
GUIs within R slightly easier to manage?
I
> But it still remains to be seen whether the extra work to introduce
> threads is warranted. Will people actually use them in R and will it
> have a significant impact on the computations or simply make writing
> GUIs within R slightly easier to manage?
If threads can be set up easily, why not?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luke Tierney wrote:
> There are several sets of notes on threading off
> http://developer.r-project.org page--somewhat old but still relevant.
> The Python approach is discussed there. That approach, which gives
> concurrency but not parallelism, is
There are several sets of notes on threading off
http://developer.r-project.org page--somewhat old but still relevant.
The Python approach is discussed there. That approach, which gives
concurrency but not parallelism, is in principle fleasible for R but
getting from here to there is non-trivial
Since Python has been mentioned in this context: Could not Python's
threading model and implementation serve as a guideline?
>From a few simple benchmarks I've run, it seems as if the Python
interpreter itself is thread-safe but not threadable. That is, when I
run something "pure Python" like a re
Thanks, Duncan,
> It is a mixture of two things. Yes, R is not thread safe so if
> two system threads were to access R concurrently, bad things would
> happen a.s.
That's clear, yes. :-/ And a pity, but so be it.
> It is also an issue when Python is compiled and linked with
> threaded options
