On Friday, July 4, 2014 4:39:13 PM UTC-4, Nicolas M. Thiéry wrote:
>
> ATA LITEONIT LCT-256. No idea if it's good or not (it's infinitely
> better than on my previous non SSD laptop :-) ). I would indeed have
> expected to most of the sage directory is loaded in memory cache
> anyway (right now,
On Thu, Jul 03, 2014 at 06:54:01PM -0700, Volker Braun wrote:
>I was also talking about my laptop, and it has pretty much identical
>specs except 32GB ram. But then everything should still comfortably fit
>into 8GB, so I don't believe that this is the reason for why your
>system is
Hi,
Le 04/07/2014 09:52, Dima Pasechnik a écrit :
There is one more advantage to building in a different place, although it's
not exploited in Sage - the build directory does not need to be
backupped. E.g. my department does not want people developing in
directories which are automatically back
On 2014-07-04, William Stein wrote:
> On Thu, Jul 3, 2014 at 6:40 PM, Volker Braun wrote:
>> On Thursday, July 3, 2014 3:31:18 PM UTC-4, William wrote:
>>>
>>>1. Building in place saves disk space. It saves a *lot* of disk
>>> space,
>>
>>
>> $ du -sh src/build/lib.linux-x86_64-2.7
>> 344M s
On Thursday, July 3, 2014 9:46:51 PM UTC-4, William wrote:
> installing to local/lib/python/site-packages is utterly confusing
Ok I just edited local/bin/sage to edit the command line handling. Was this
a good idea? Why do my changes not stick?
--
You received this message because you are su
On Thursday, July 3, 2014 5:50:59 PM UTC-4, Nicolas M. Thiéry wrote:
>
> My laptop is 1.5 years old, with SSE disk, Intel I7 @2.60 MHz 8 cores,
> 8Go of RAM; it should still be in the rather high end. Ubuntu, ext4, a
> priori nothing specific configured (except for the make -j8 by
> default). I'
On Thu, Jul 3, 2014 at 6:40 PM, Volker Braun wrote:
> On Thursday, July 3, 2014 3:31:18 PM UTC-4, William wrote:
>>
>>1. Building in place saves disk space. It saves a *lot* of disk
>> space,
>
>
> $ du -sh src/build/lib.linux-x86_64-2.7
> 344M src/build/lib.linux-x86_64-2.7
>
> Here is a nic
On Thursday, July 3, 2014 3:31:18 PM UTC-4, William wrote:
>
>1. Building in place saves disk space. It saves a *lot* of disk
> space,
$ du -sh src/build/lib.linux-x86_64-2.7
344M src/build/lib.linux-x86_64-2.7
Here is a nickel, kid. Go and buy yourself some more disk space ;-)
2. Buildi
On Thu, Jul 03, 2014 at 05:38:42AM -0700, Volker Braun wrote:
>On Thursday, July 3, 2014 6:59:45 AM UTC-4, Nicolas M. Thiéry wrote:
>
> Compiling in place means saving 15s of `sage -b` each time I just
> modify Python code
>
>Hmm can you describe your hardware and filesystem? Af
On Thu, Jul 3, 2014 at 7:21 AM, John H Palmieri wrote:
>
>
> On Thursday, July 3, 2014 3:59:45 AM UTC-7, Nicolas M. Thiéry wrote:
>>
>> Dear Sage developers,
>>
>> I recently noticed some preliminary work in src/setup.py toward
>> compiling the Sage library in place, instead of putting the
On Thursday, July 3, 2014 3:59:45 AM UTC-7, Nicolas M. Thiéry wrote:
>
> Dear Sage developers,
>
> I recently noticed some preliminary work in src/setup.py toward
> compiling the Sage library in place, instead of putting the produced
> .so and copies of the .py files in src/build.
>
>
On Thursday, July 3, 2014 6:59:45 AM UTC-4, Nicolas M. Thiéry wrote:
>
> Compiling in place means saving 15s of `sage -b` each time I just
> modify Python code
>
Hmm can you describe your hardware and filesystem? After editing a Python
file, "echo quit | sage -br" takes me 4.8 seconds. Just runn
On Wed, Jul 02, 2014 at 09:54:17PM -0500, Nicolas M. Thiery wrote:
> I recently noticed some preliminary work in src/setup.py toward
> compiling the Sage library in place, instead of putting the produced
> .so and copies of the .py files in src/build.
>
> Compiling in place means saving 15s of `sa
13 matches
Mail list logo
