On Sunday, March 20, 2016 at 10:40:56 PM UTC+1, William wrote: > > That doesn't work since SMC uses normal Linux users, not lxc or docker > containers, so they do not have a virtual chroot'd filesystem. >
Well that explains why massive parallel compilation can grind everything to a halt; Without cgroups its not possible to limit a user's total RSS, say. Still, you can have a process-private mount namespace even without cgroups (using unshare). > For most development (on the library, not on packaging, which is the > kind you probably do a lot of), a virtualenv (or python setup.py > develop) local setup of the sage library, which overrides a > system-wide install would be much better. But then you still need to cythonize Sage and build the docs (wheels won't work when depending on non-system libraries). -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
