I know some OS X systems default to building 32-bit binaries, but will build
64-bit binaries - just like Solaris does. (Also, incidentally HP-UX with PA-RISC
processors).
What versions of OS X do this? On what processor(s)?
John Palmieri is updating the Sage installation guide, and documentin
On Fri, Jun 25, 2010 at 6:48 AM, Minh Nguyen wrote:
> Hi David,
>
> On Fri, Jun 25, 2010 at 11:40 PM, David Kirkby
> wrote:
>
>
>
>> Of course, that could change over time. If you want to know your way
>> around a Solaris system a bit more, here are some semi-useful commands
>
> Thank you for g
On 06/25/10 09:46 PM, Jason B. Hill wrote:
Could it be an option to add the relevant information to
sage_root/install.log and prune from there? Some of the info we're looking
at is already available in that file. For instance... info copied from an
install.log:
uname -a: Linux dirichlet 2.6.31-2
Hi David,
On Thu, Jun 24, 2010 at 8:06 PM, Dr. David Kirkby
wrote:
> A typical spkg-check, which needs to go into the same directory as
> spkg-install and SPKG.txt is below.
See ticket #9340
http://trac.sagemath.org/sage_trac/ticket/9340
to update the Developer's Guide to require spkg-check
This should be fixed with the ast display-hook patch, #7997
- Alex
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/grou
Could it be an option to add the relevant information to
sage_root/install.log and prune from there? Some of the info we're looking
at is already available in that file. For instance... info copied from an
install.log:
uname -a: Linux dirichlet 2.6.31-21-generic #59-Ubuntu SMP Wed Mar 24
07:28:27
On Jun 25, 3:34 pm, Andrey Novoseltsev wrote:
> So I'd prefer to keep the existing name
> "linear_subspace" for the corresponding function.
For once, I totally agree! :-)
Volker
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an emai
One of my students observed that if you type an expression in the
notebook on one line, the resulting value is printed:
{{{
(x+1)
///
x+1
}}}
but if you put a new line inside the paretheses (which in python does
not change the semantics) the resulting value is no longer printed:
{{{
(x+
1)
///
}}}
On 06/25/10 08:11 AM, Adam Webb wrote:
On Jun 24, 11:42 pm, "Dr. David Kirkby"
The problem with Python in Sage is there are so many patches, that is makes it
difficult to update. Many patches are copied over Python files - I don't know
how carefully these changed files have been updated as p
On 25 June 2010 16:15, Minh Nguyen wrote:
> Hi Franco,
>
> On Sat, Jun 26, 2010 at 1:10 AM, Franco Saliola wrote:
>
>
>
>> Anyone interested in turning this thread into a script that spits out
>> the version of sage, together with all the above system
>> hardware/software information?
>
> See ti
Hi Franco,
On Sat, Jun 26, 2010 at 1:10 AM, Franco Saliola wrote:
> Anyone interested in turning this thread into a script that spits out
> the version of sage, together with all the above system
> hardware/software information?
See ticket #8048 for a little-baked idea:
http://trac.sagemath.
On Fri, Jun 25, 2010 at 10:59 AM, Jason Hill wrote:
>
> You can chop it up a bit for readability too. This is tested on Debian and
> Red Hat.
>
> $ uname -a
> $ cat /etc/issue
> $ cat /proc/cpuinfo | grep -m 1 "model name"
> $ cat /proc/cpuinfo | grep -c "processor" # number of cores
> or $ cat /p
You can chop it up a bit for readability too. This is tested on Debian and
Red Hat.
$ uname -a
$ cat /etc/issue
$ cat /proc/cpuinfo | grep -m 1 "model name"
$ cat /proc/cpuinfo | grep -c "processor" # number of cores
or $ cat /proc/cpuinfo | grep -m 1 "cores" # number of cores per processor
$ cat
Hi David,
On Fri, Jun 25, 2010 at 11:40 PM, David Kirkby wrote:
> Of course, that could change over time. If you want to know your way
> around a Solaris system a bit more, here are some semi-useful commands
Thank you for giving such a useful list of commands for getting
information about a S
Whenever I do testing of patches and puts the results on trac, I
usually put quite detailed information about the hardware/software
used.
Typically I write
* Make and model of computer
* CPU(s)
* RAM
* Exact version of the operating system.
* Compiler (usually gcc), with version number.
In the ca
On Fri, Jun 25, 2010 at 2:48 AM, Volker Braun wrote:
> Ewald's book "Combinatorial convexity and algebraic geometry" defines
> the cospan of a (not strictly convex) cone to be its maximal linear
> subspace. I think we should stick to "dual" when it comes to lattices
> since this in the standard no
Hi folks,
I'm trying to update the acknowledgement page [1] on the Sage website.
In particular, I would like to know who and/or which organizations
funded Sage Days 21 and 22. Are there anyone and/or organization that
ought to be acknowledged for those workshops?
[1] http://www.sagemath.org/devel
Hi kcrisman,
On Fri, Jun 25, 2010 at 4:09 AM, kcrisman wrote:
> Just out of curiosity, is that a bug that needs to be reported
> upstream to Sphinx/ReST,
My bug report has gone through to sphinx-dev:
https://groups.google.com/group/sphinx-dev/browse_thread/thread/e357fdef709ef803
--
Regards
M
On Jun 24, 11:42 pm, "Dr. David Kirkby"
wrote:
> On 06/24/10 08:45 PM, Fran ois Bissey wrote:
>
>
>
> >> On 06/24/10 04:14 PM, Adam Webb wrote:
> >>> test_distutils passes if I use a plain python 2.6.5 tarball. This is
> >>> consistent with the problem being in Sage or at least in the
> >>> envi
On Jun 24, 11:42 pm, "Dr. David Kirkby"
wrote:
> On 06/24/10 08:45 PM, Fran ois Bissey wrote:
>
>
>
> >> On 06/24/10 04:14 PM, Adam Webb wrote:
> >>> test_distutils passes if I use a plain python 2.6.5 tarball. This is
> >>> consistent with the problem being in Sage or at least in the
> >>> envi
20 matches
Mail list logo
