Volker Braun wrote:
On Thursday, May 29, 2014 9:45:52 PM UTC+1, leif wrote:Well, nevertheless, AFAIK it uses Python's multiprocessing even with SAGE_NUM_THREADS=1, just like 'sage -b' does. Whats wrong with that?
As Dima pointed out, it doesn't only (needlessly) require specific resources (such as e.g. /dev/shm on Linux), it also uses more resources (because of forking). I haven't counted how many times people reported to sage-{devel,support} not being able to build Sage (i.e., the Sage library) or the docs because of issues with Python's multiprocessing. When trying to build the Sage library, the error message isn't very helpful either.
You want an extra untested codepath to handle that special value?
Why should it be untested? And it isn't special in any way either; it's rather the default.
-leif -- () The ASCII Ribbon Campaign /\ Help Cure HTML E-Mail -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
