On Tuesday, March 27, 2012 10:34:12 AM UTC-7, leif wrote:
On 27 Mrz., 19:19, Jason Grout jason-s...@creativetrax.com wrote:
On 3/27/12 12:10 PM, John H Palmieri wrote:
This topic has been brought up here before as side notes in various
threads, but I'd like to discuss it more
On Monday, March 26, 2012 9:32:45 AM UTC-7, Keshav Kini wrote:
Simon King writes:
sage: is_Integer(int(5))
False
sage: is_Integer(5/1)
False
sage: int(5) in ZZ
True
sage: 5/1 in ZZ
True
Huh. It seems like this is the opposite of what you'd expect, doesn't
it?
On Friday, March 23, 2012 2:04:32 PM UTC-7, Starx wrote:
So I'm trying to upgrade my beta7 to beta9.
Upgrading from one beta release to another is not supported, so this is not
likely to work. (If you are curious about why, then search through
sage-devel for other threads on upgrading.)
On Friday, March 23, 2012 2:07:21 PM UTC-7, Snark wrote:
Le jeudi 22 mars, Julien Puydt a écrit:
Le jeudi 22 mars, William Stein a écrit:
On Wed, Mar 21, 2012 at 7:34 PM, Julien Puydt wrote:
Hi,
yesterday I noticed that there are many places in sage's sources
(I only
On Friday, March 23, 2012 4:39:02 PM UTC-7, leif wrote:
On 24 Mrz., 00:25, leif not.rea...@online.de wrote:
On 23 Mrz., 23:18, Jeroen Demeyer jdeme...@cage.ugent.be wrote:
On 2012-03-23 22:58, leif wrote: P.S.: What makes *me* wonder since
years btw. is the bizarre python
Does anyone use the files in the directory SAGE_ROOT/ipython? Would you
object if they were moved elsewhere in the Sage distribution, and if some
of the files were modified or deleted? (In particular, ipythonrc-scipy
might not be long for this world, if I have anything to do with it.) Newer
On Wednesday, March 21, 2012 12:33:39 PM UTC-7, Snark wrote:
Le mercredi 21 mars, William Stein a écrit:
On Wed, Mar 21, 2012 at 2:16 PM, Julien Puydt wrote:
Hi,
how can I know which spkg provided a file in sage?
Let's say for example (from sage-4.8) :
I have no idea if this is a new issue, but the attachments for
http://trac.sagemath.org/sage_trac/ticket/12684 don't view quite correctly:
there are some lines at the end of the patch which move files around, and
those are not visible when you view the attachment.
(This may be just the same as
On Thursday, March 15, 2012 2:28:02 PM UTC-7, Nicolas M. Thiéry wrote:
Dear Sage doc compilation fans,
Currently, make doc calls sage -docbuild with the option
--no-pdf-links. I don't have an opinion about this specific option,
but a very anoying consequence is that if you do a
On Tuesday, March 13, 2012 5:11:00 PM UTC-7, Dima Pasechnik wrote:
On Monday, 12 March 2012 06:15:35 UTC+8, Jeroen Demeyer wrote:
I have made a spkg for GCC (GNU compiler collection) version 4.6.3 with
compilers for C, C++ and Fortran, see Trac #12369.
The GCC spkg depends on an MPC
On Sunday, March 11, 2012 3:15:35 PM UTC-7, Jeroen Demeyer wrote:
What are your +1/-1 to making GCC and MPC standard packages?
+1 (especially since it allows us to build Sage on Lion without making
other compromises)
--
John
--
To post to this group, send an email to
On Sunday, March 11, 2012 8:46:55 PM UTC-7, Starx wrote:
The patchbot is reporting a doctest failure in a patch of mine:
http://trac.sagemath.org/sage_trac/ticket/12630#comment:10
The failure itself is completely benign, a + b is being returned
when b + a is expected, but the addition is
On Thursday, March 8, 2012 4:49:12 PM UTC-8, Dima Pasechnik wrote:
It turns out that here Apple is not doing anything wrong.
(after having a discussion here:
https://discussions.apple.com/message/17795537)
It's improper use of BLAS by CVXOPT people that triggers errors.
The C code in
On Tuesday, March 6, 2012 4:35:45 PM UTC-8, R. Andrew Ohana wrote:
It seems odd to me that the extcode and sage_scripts spkgs have their
version bumped with every sage release. sage_scripts contains the
version info for sage (in sage-banner), but IMO this is something that
should be stored
On Wednesday, February 29, 2012 3:01:46 PM UTC-8, Snark wrote:
Le mercredi 29 février, William Stein a écrit:
(1) when you want to apply a theorem, do you just check for the
hypotheses then go on, or do you re-do the proof down from the
axioms?
Neither. This is a false analogy.
On Tuesday, February 28, 2012 12:45:08 PM UTC-8, Keshav Kini wrote:
William Stein writes:
On Tue, Feb 28, 2012 at 8:43 AM, Keshav Kini wrote:
It's not actually a fallback for b), though. If a file does exist with
the same name as a subcommand, b) makes it impossible to use that
On Tuesday, February 21, 2012 2:00:01 PM UTC-8, entropy wrote:
John,
Just to confirm, did this build work for you on Lion 10.7.2, with
Xcode 4.3, and gcc version 4.2.1 (LLVM build 2336.9.00)?
I'm using Lion 10.7.3, not 10.7.2. I agree with the gcc version:
$ gcc --version
On Sunday, February 19, 2012 11:49:23 PM UTC-8, Jeroen Demeyer wrote:
On 2012-02-19 06:53, John H Palmieri wrote:
On the plus side, on the laptop where I had problems before, Sage built
and passed all doctests using the default compiler:
You mean 5.0.beta4 worked or do you mean my 5.0
On Monday, February 20, 2012 7:53:05 AM UTC-8, John H Palmieri wrote:
On Sunday, February 19, 2012 11:49:23 PM UTC-8, Jeroen Demeyer wrote:
On 2012-02-19 06:53, John H Palmieri wrote:
On the plus side, on the laptop where I had problems before, Sage built
and passed all doctests using
On Monday, February 20, 2012 2:43:29 PM UTC-8, Benjamin Jones wrote:
On Mon, Feb 20, 2012 at 2:39 PM, François Bissey wrote:
snip
There are efforts to parallelize the building of the doc and I would say
that
if it gets merged we may very well put the doc back into sage and just
build
We have another small problem with Lion. I just wiped my hard drive and
reinstalled Lion (because of some non-Sage related issues). Then I
reinstalled Xcode: the newly released version 4.3. Two issues:
command-line tools are no longer installed by default, so you have to
install gcc, clang,
On Saturday, February 18, 2012 3:12:19 PM UTC-8, John H Palmieri wrote:
We have another small problem with Lion. I just wiped my hard drive and
reinstalled Lion (because of some non-Sage related issues). Then I
reinstalled Xcode: the newly released version 4.3. Two issues:
command-line
On Wednesday, February 15, 2012 10:21:40 PM UTC-8, John H Palmieri wrote:
On Wednesday, February 15, 2012 7:59:16 AM UTC-8, John H Palmieri wrote:
On Tuesday, February 14, 2012 10:50:52 AM UTC-8, Jeroen Demeyer wrote:
John, entropy, Could you try the following:
$ rm spkg/logs/gcc
On Tuesday, February 14, 2012 10:50:52 AM UTC-8, Jeroen Demeyer wrote:
John, entropy, Could you try the following:
$ rm spkg/logs/gcc-4.6.2.log
$ MAKE=make -j1 SAGE_CHECK=yes CFLAGS=-O0 ./sage -f
spkg/standard/gcc-4.6.2.spkg
If it fails, send me spkg/logs/gcc-4.6.2.log
It failed. Log:
On Wednesday, February 15, 2012 7:59:16 AM UTC-8, John H Palmieri wrote:
On Tuesday, February 14, 2012 10:50:52 AM UTC-8, Jeroen Demeyer wrote:
John, entropy, Could you try the following:
$ rm spkg/logs/gcc-4.6.2.log
$ MAKE=make -j1 SAGE_CHECK=yes CFLAGS=-O0 ./sage -f
spkg/standard/gcc
On Monday, February 13, 2012 11:51:50 PM UTC-8, Jeroen Demeyer wrote:
On 2012-02-13 19:05, John H Palmieri wrote:
I posted the same failure two days ago to the relevant trac ticket,
http://trac.sagemath.org/sage_trac/ticket/12369.
Not the same failure, your failure on #12369
On Tuesday, February 14, 2012 5:14:13 PM UTC-8, R. Andrew Ohana wrote:
On Tue, Feb 14, 2012 at 14:57, entropy wrote:
Darn, flopped again. The mpir package could not find a working
compiler. Kind of ironic, since this whole thread has been about
building gcc-4.6.2. :) From the log, it
On Monday, February 13, 2012 9:55:43 AM UTC-8, William wrote:
On Mon, Feb 13, 2012 at 8:51 AM, entropy wrote:
Hi all,
This is wonderful news. So great, that I tried to compile
sage-5.0beta3 on my OS X 10.7.2 laptop. Sadly, it threw an error while
attempting to compile gcc4.6.2.
On Monday, February 13, 2012 11:16:54 AM UTC-8, William wrote:
On Mon, Feb 13, 2012 at 11:10 AM, Michael Orlitzky wrote:
On 02/13/12 13:51, Ryan wrote:
#this test case will pass
def TestCase1():
r'''
Examples::
sage: ascii()
On Monday, February 13, 2012 11:49:29 AM UTC-8, Volker Braun wrote:
On Monday, February 13, 2012 10:05:56 AM UTC-8, John H Palmieri wrote:
Or is there something about the laptop architecture which is causing the
problem?
It would be useful if people would post the output of uname
On Saturday, February 11, 2012 11:34:21 AM UTC-8, jason wrote:
On 2/11/12 1:27 PM, Justin C. Walker wrote:
Hi, Jason,
On Feb 11, 2012, at 06:08 , Jason Grout wrote:
I'm upgrading sagenb.org to sage 4.8 and I get some errors when trying
to install the p_group_cohomology package. If
On Saturday, February 11, 2012 8:39:32 PM UTC-8, Michael Orlitzky wrote:
I've started this:
http://wiki.sagemath.org/PiecewiseSymbolicSEP
It's basically a brain dump at this point, but I can go back and clean
up specific ideas now with less overhead.
I've also added a link and a few
On Tuesday, February 7, 2012 2:49:36 AM UTC-8, Jeroen Demeyer wrote:
What is the correct way to fix the following doctest failure? Here, G
is the result of a gram_schmidt() computation, hence the sign shouldn't
matter mathematically.
sage -t -force_lib devel/sage/sage/matrix/matrix2.pyx
On Tuesday, February 7, 2012 3:06:14 PM UTC-8, Jeroen Demeyer wrote:
I came across the following in the Sage Developer guide:
- If your package depends on another package, say boehmgc, then you
should check that this other package has been installed. Your
``spkg-install``
Various aspects of building Sage might be cleaner if we used autoconf:
./configure OPTIONS
make
OPTIONS could include a location to install Sage, various flags for
building ATLAS, and other options which we currently control by setting
environment variables. For typical users, we should
Are these workshops all going to be in Seattle?
--
John
--
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
On Friday, February 3, 2012 8:33:53 AM UTC-8, William wrote:
Just to clarify, does gcc-4.2 *not* come with the latex XCode 4.x, but
it came with earlier XCode 4.x's?I have gcc-4.2 on my laptop, and
I've never installed anything but XCode 4.x on it.
Just curious.
I think that it came
On Tuesday, January 31, 2012 1:01:41 PM UTC-8, R. Andrew Ohana wrote:
On Mon, Jan 30, 2012 at 10:04, John H Palmieri jhpalm...@gmail.com
wrote:
On Tuesday, January 17, 2012 1:59:45 PM UTC-8, William wrote:
On Tue, Jan 17, 2012 at 1:39 PM, William Stein wst...@gmail.com
wrote
On Tuesday, January 17, 2012 1:59:45 PM UTC-8, William wrote:
On Tue, Jan 17, 2012 at 1:39 PM, William Stein wst...@gmail.com wrote:
On Mon, Jan 16, 2012 at 3:43 PM, William Stein wst...@gmail.com wrote:
On Mon, Jan 16, 2012 at 9:26 AM, John H Palmieri jhpalm...@gmail.com
wrote
On Friday, January 27, 2012 2:19:59 AM UTC-8, Jeroen Demeyer wrote:
On 2012-01-27 11:17, David Roe wrote:
Why? So that things like sage -i can work without python?
Exactly.
And also for speed issues, as William brought up a year or two ago when we
discussed this sort of thing. If you
On Sunday, January 22, 2012 8:10:17 AM UTC-8, William wrote:
Hi,
I wanted to try out #3052, which is Kini's code for converting .hg
repos to JSON and back. So I took a Sage-4.8 binary, and started
looking for his code. I just wanted to run the script on a sample .hg
repo, etc. The
On Saturday, January 21, 2012 8:28:35 AM UTC-8, jason wrote:
I'm trying to track down this error:
/Users/grout/sage-trees/sage-5.0.prealpha1/devel/sagenb-git/sagenb/notebook/cell.py:docstring
of sagenb.notebook.cell.Cell:4: WARNING: Block quote ends without a
blank line; unexpected
On Saturday, January 21, 2012 12:01:07 PM UTC-8, jason wrote:
It turns out that the error is indeed in a completely different
function. One of the functions has a docstring that has this line:
sage:
W.edit_save('foo\n{{{\n2+3\n///\n5\n}}}bar\n{{{\n2+8\n///\n10\n}}}')
On Thursday, January 19, 2012 9:37:00 AM UTC-8, William wrote:
Hi,
Regarding jsmath and mathjax... It seems like we have the issues
worked out for the Sage notebook. Yeah, and thanks to Jason, David,
etc., for their persistence.
I was just browsing mathoverflow, e.g., [1], and noticed
On Tuesday, January 17, 2012 10:06:18 AM UTC-8, kcrisman wrote:
Here is a probably dumb question.
Currently (as far as I am aware), most spkgs should pass with
SAGE_CHECK set, though it does depend on the platform and specific
machine. Python is somewhat notorious for not doing so.
On Tuesday, January 17, 2012 10:19:03 AM UTC-8, Volker Braun wrote:
I consider it a bug that Python's testsuite fails on many systems even
though the resulting python install is perfectly usable for our purposes.
The Python spkg-check should be changed to not call the whole python
On Tuesday, January 17, 2012 10:45:37 AM UTC-8, kcrisman wrote:
On Jan 17, 1:15 pm, John H Palmieri jhpalm...@gmail.com wrote:
On Tuesday, January 17, 2012 10:06:18 AM UTC-8, kcrisman wrote:
Here is a probably dumb question.
Currently (as far as I am aware), most spkgs
On Monday, January 16, 2012 7:42:49 AM UTC-8, William wrote:
Hi,
A major blocker for Sage-5.0 is supporting OS X (version 10.7 -- the
version that has been out for months now).
Fortunately, it is now relatively easy to build sage-5.0.beta1 on OS
X 10.7 with XCode 4.x, and have it start
On Saturday, January 14, 2012 9:07:08 AM UTC-8, William wrote:
On Jan 14, 2012 9:00 AM, Dr David Kirkby drki...@gmail.com wrote:
On Jan 9, 4:39 pm, William Stein wst...@gmail.com wrote:
Very few people actually use the notebook in secure=True mode. For
those that do, I think
On Friday, January 13, 2012 2:07:00 PM UTC-8, Raymond N. Greenwell wrote:
Hello! I posted this on sage-support, but I should have posted it
here.
I tried using the HasseDiagram and rank features of Sage as described
on
On Thursday, January 5, 2012 2:21:37 PM UTC-8, john.hoebing wrote:
On Jan 5, 10:22 am, John Cremona john.c...@gmail.com wrote:
Will this procedure work? Surely ./sage -i will not work with a
half-built system? Well, I am trying...
No that won't work, as some others have already
On Sunday, January 1, 2012 7:18:20 AM UTC-8, daveloeffler wrote:
I get an error when doing a parallel build with SAGE_CHECK set. See
below for the relevant part of the output. The problem seems to be
that the M4RIE test suite requires NTL and Givaro to have already been
built, but that
On Sunday, January 1, 2012 8:52:24 AM UTC-8, daveloeffler wrote:
Here's *yet another* SAGE_CHECK issue. The sagetex package doesn't
work:
[snip]
Output written on example.dvi (7 pages, 23380 bytes).
Transcript written on example.log.
Traceback (most recent call last):
File
On Friday, December 23, 2011 4:54:53 PM UTC-8, Travis Scrimshaw wrote:
I copied the latest version of TikZ / PGF (using a shared folder)
to the VM and installed it. I was able to compile the .tex file using
the VM's latex compiler and view the output .pdf from my host OS
(Windows
On Saturday, December 24, 2011 8:08:19 AM UTC-8, John Cremona wrote:
This is similar to the situation with the optional elliptic curve
database, since the default database is changed as of 4.8 (uses a
different database engine) so the optional spkg has also been updated,
so we have one
On Tuesday, December 20, 2011 12:48:00 AM UTC-8, Nicolas M. Thiery wrote:
On Tue, Dec 20, 2011 at 12:55:11AM +, Sagan, Bruce wrote:
Formidable! This installed dot2tex. Thanks so much!! One last
question. When I went back to the notebook and ran a view command (I just
copied the
On Saturday, December 17, 2011 3:00:15 PM UTC-8, Burcin Erocal wrote:
Hi Maarten,
On Sat, 17 Dec 2011 14:28:47 -0800 (PST)
Maarten Derickx m.derick...@gmail.com wrote:
I was merging my new ipython spkg wich needed review for some time
already at
On Tuesday, December 13, 2011 3:51:19 PM UTC-8, Nathann Cohen wrote:
Hello everybody !!!
I have been contacted by an enlightened colleague who planned to teach a
bit of Sage at the local university, instead of Magma and Mathematica as it
was formerly done. Now, enthusiasm is a wonderful
On Tuesday, December 13, 2011 3:51:19 PM UTC-8, Nathann Cohen wrote:
Hello everybody !!!
I have been contacted by an enlightened colleague who planned to teach a
bit of Sage at the local university, instead of Magma and Mathematica as it
was formerly done. Now, enthusiasm is a wonderful
On Monday, December 12, 2011 5:13:00 PM UTC-8, Michael Orlitzky wrote:
Is there an easy way to print a symbolic expression so that it's valid
python code? E.g.
2*x^2 -- QQ(2) * x**QQ(2)
How about
sage: preparse('2*x^2')
'Integer(2)*x**Integer(2)'
--
John
--
To post to
On Saturday, December 3, 2011 10:45:10 AM UTC-8, Snark wrote:
Le 03/12/2011 19:27, William Stein a �crit :
Thanks for the updated ticket. I will probably just use the ubuntu
atlas binary instead of building atlas, to avoid trouble with that.
How does one do that for atlas? For other
On Friday, December 2, 2011 4:43:06 PM UTC-8, Jeroen Demeyer wrote:
On 2011-12-03 01:27, Francois Bissey wrote:
Apart from the python upgrade which will require re-compilation of
everything
python with the exception of scons (because it doesn't install anything
under
libpython2{6,7})
Try searching the group sage-devel (and possibly sage-release) for
readline configuring R. The following thread might be useful, for
example:
https://groups.google.com/forum/#!searchin/sage-devel/readline$20configuring$20r/sage-devel/B7y-ntx13Os/m2kJoygRxMYJ
--
John
--
To post to this
On Saturday, November 26, 2011 2:30:06 AM UTC-8, Jeroen Demeyer wrote:
Proposal:
1) In sage-env, do not add $SAGE_ROOT to the $PATH.
2) Rename local/bin/sage-sage to local/bin/sage
Reason:
The python 2.7.2 package checks whether hg is available and runs hg
during the build process.
On Tuesday, November 22, 2011 11:31:29 AM UTC-8, Christian Stump wrote:
Building Sage on OS X Lion is not yet supported; nobody has yet built
one that 100% works and passes all tests, though we're close. Seehttp://
trac.sagemath.org/sage_trac/ticket/11881
I see, thanks for the reply!
On Tuesday, November 22, 2011 12:42:41 PM UTC-8, Bill Janssen wrote:
You should build your new spkg by starting with the old one
Except that the old one doesn't exist -- this is pil-1.1.7.p0, not
pil-1.1.6.p5.
Still not sure how to go about this -- an example (perhaps it's in the
docs)
On Tuesday, November 22, 2011 3:45:28 PM UTC-8, Bill Janssen wrote:
On Nov 22, 12:53 pm, John H Palmieri jhpalm...@gmail.com wrote:
So pil-1.1.6.p5 *is* the old one.
pil-1.1.6.p4 is the old one.
Remove the src directory from that
one, replacing it with the new source. Modify any
On Thursday, November 17, 2011 1:17:45 PM UTC-8, Bill Janssen wrote:
I've put up my first try at a PIL 1.1.7 spkg at http://uplib.parc.com/
misc/pil-1.1.7.p0.spkg http://uplib.parc.com/misc/pil-1.1.7.p0.spkg.
Please tell me what I did wrong :-).
I would open up a ticket, making sure to
On Thursday, November 17, 2011 1:49:39 PM UTC-8, Bill Janssen wrote:
Some issues with this spkg:
- The mercurial repository is completely missing.
Yes, it's not a patch to the Sage sources, so there's no Mercurial
stuff as there would be if it were.
Every spkg should contain a
On Wednesday, November 16, 2011 6:07:15 AM UTC-8, Jan Groenewald wrote:
Hi
0 jan@muizenberg:/var/autofs/misc/home/jan$grep example.sage
/usr/local/src/sage-4.7.2/local/share/texmf/tex/generic/sagetex/example.tex
% (pdf)latex example.tex; sage example.sage; pdflatex example.tex
when
On Tuesday, November 15, 2011 2:15:39 AM UTC-8, Jeroen Demeyer wrote:
On 2011-11-15 11:06, Jeroen Demeyer wrote:
To somebody with access to a OS X 10.7 machine: please test whether the
spkg
http://boxen.math.washington.edu/home/jdemeyer/spkg/ecl-11.1.2.cvs2007.p0.spkg
Doesn't
On Friday, November 11, 2011 10:16:16 AM UTC-8, Jeroen Demeyer wrote:
Is there a requirement that all Sage .py files should be ASCII or is
UTF8 also accepted?
It seems that Sphinx 1.1.2 (#10620) cares more about this: at #10112
there is a patch with a 0xd0 byte (which is neither ASCII
On Saturday, November 12, 2011 9:29:29 PM UTC-8, François wrote:
On Saturday, November 12, 2011 5:21:07 PM UTC-8, François wrote:
Hi,
I spotted those two files and I am wondering what they are
used for.
sage-sage.py looks like a rewrite of sage-sage in python, is it ever
On Friday, November 11, 2011 2:45:08 PM UTC-8, Jeroen Demeyer wrote:
I am considering removing the doc dependency from the test targets
(like ptestlong). I am regularly annoyed by the long time it takes to
rebuild the docs
How about reviewing #6495 instead? It cuts down the time to
On Wednesday, November 9, 2011 10:44:45 AM UTC-8, fhivert wrote:
Hi there,
I've a problem with interact together with a request:
I'd like to write a function which return some interact, for example:
def make_interact(i):
def _(choice=[x%i%u for u in range(i)]):
print
Well, as I mentioned above, the current plan in #11790 is, among other
things, to source a file ~/.sage/.sagerc (if it exists), so maybe you can
add code to set your prompt there.
--
John
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group,
On Friday, October 28, 2011 3:22:04 PM UTC-7, Dr. David Kirkby wrote:
My Opensolaris box hawk is back up. Those who have accounts, and the
buildbot,
can use it again.
Hi Dave,
Thanks; it's great to have a (fast) OpenSolaris machine to test on.
--
John
--
To post to this group, send
On Wednesday, November 2, 2011 5:33:15 AM UTC-7, Jeroen Demeyer wrote:
Important question: If I set
MAKE=make -j6
could it be that I get 36 processes in a parallel build? 6 packages in
parallel and 6 jobs per package? Or has this been taken care of?
The GNU make man page says that it
On Tuesday, November 1, 2011 5:07:47 PM UTC-7, Keshav Kini wrote:
That's what I thought too, but upon testing it seems that PS1 is somehow
special in this regard:
That's what I discovered, too. The current idea (at #11790) is that you
can set a new environment variable, SAGE_SHPROMPT,
A quick survey for people who use sage -sh:
- Do you find the current multiline shell prompt useful?
- Would you prefer that the prompt is shorter, and in particular, a single
line?
At the moment, when you run sage -sh, it says
Starting subshell with Sage environment variables set.
Be
On Friday, October 28, 2011 1:42:25 PM UTC-7, kcrisman wrote:
On Oct 28, 3:40 pm, Jason Grout jason...@creativetrax.com wrote:
For the last few years, we've had a Sage Days following the AMS/MAA
Joint Meetings. Are we planning on that again this January? The Joint
Meetings are Jan
The option to build spkg's in Sage in parallel has been available for quite
a while now, but it has to be enabled by setting the shell variable
SAGE_PARALLEL_SPKG_BUILD equal to yes. Should we change the default,
building in parallel unless this variable is explicitly set to no (or
n)? I
On Thursday, October 27, 2011 10:29:37 AM UTC-7, kcrisman wrote:
On Oct 27, 1:14 pm, John H Palmieri jhpalm...@gmail.com wrote:
The option to build spkg's in Sage in parallel has been available for
quite
a while now, but it has to be enabled by setting the shell variable
On Thursday, October 27, 2011 11:43:56 AM UTC-7, Jeroen Demeyer wrote:
On 2011-10-27 19:14, John H Palmieri wrote:
The option to build spkg's in Sage in parallel has been available for
quite a while now, but it has to be enabled by setting the shell
variable SAGE_PARALLEL_SPKG_BUILD
On Thursday, October 27, 2011 12:28:00 PM UTC-7, kcrisman wrote:
As it turns out, trying the wrong behavior (make -j2 with parallel
spkgs) on one of my one processor machines does lead to unusual build
failures which seem to have to do with waiting for jobs. And then it
finishes the next
On Thursday, October 27, 2011 2:15:34 PM UTC-7, leif wrote:
P.S.: Incidentally I also posted about parallel make on sage-support
today:
http://groups.google.com/group/sage-support/msg/a17f6e561583e1a5
http://groups.google.com/group/sage-support/msg/f4d0c2e3815f1157
Yes, hence my
Okay, a patch is up. See
http://trac.sagemath.org/sage_trac/ticket/11959
If people have objections to the whole plan, please keep them here. If you
have issues with the particular implementation, let's discuss that on the
ticket.
--
John
--
To post to this group, send an email to
On Wednesday, October 26, 2011 1:01:46 PM UTC-7, leif wrote:
On 26 Okt., 17:15, William Stein wst...@gmail.com wrote:
I just tried to upgrade from sage-4.7 to sage-4.7.1 on
I don't recall where and when, but we already had some discussion on
that, e.g. that files unknown to
On Wednesday, October 26, 2011 4:47:03 PM UTC-7, leif wrote:
I'll perhaps tweak sage-sage and sage-update a little; changing all
sage*.spkg's spkg-install files is another story.
Feel free to modify the spkg-install file for the root repo, also, to deal
with the specific hg issue
On Tuesday, October 25, 2011 3:52:24 PM UTC-7, Andrew Mathas wrote:
Hi All,
Is there an educated guess as to when/if sage will be ported to lion?
I foolishly upgraded when it came out and have been unable to use sage
since...
There is a trac ticket about this on which there has been
Are there *any* tickets dealing with building Sage on Lion? Don't we need
to get working on this pretty seriously? I've heard rumors of possible fixes
lurking, but it's frustrating that nothing is publicly available.
I just opened http://trac.sagemath.org/sage_trac/ticket/11881, a
meta-ticket
On Tuesday, September 20, 2011 12:55:32 PM UTC-7, John H Palmieri wrote:
Should sage-preparse name the preparsed file something safer, in order to
prevent name clashes like this? For example, turn FILE.sage into
FILE_preparsed.py?
Following up to myself: the script sage-sage, which
On Monday, September 26, 2011 9:28:24 AM UTC-7, Rob Gross wrote:
Thanks for any more ideas. This is a busy week for me, but I'll try
to test any suggestions as soon as they come in.
Have you tried Dima's suggestion? Just to be safe, I would start with a
fresh download of the Sage
On Wednesday, September 21, 2011 11:26:39 AM UTC-7, Felix Salfelder wrote:
On Wed, Sep 21, 2011 at 09:11:57AM -0700, Tom Boothby wrote:
I capitulate on the hidden file idea, in favor of putting 'em in
~/.sage/ though one might note that we're exchanging one hidden file
for another ;)
i
If I create a simple Sage script and call it script.sage, then running
sage script.sage works fine. But if I call it new.sage, it doesn't.
Why?
Script:
def f(i):
return i
f(10)
Error:
Traceback (most recent call last):
File new.py, line 2, in module
from
On Tuesday, September 20, 2011 11:07:10 AM UTC-7, John H Palmieri wrote:
If I create a simple Sage script and call it script.sage, then running
sage script.sage works fine. But if I call it new.sage, it doesn't.
Why?
[snip]
from twisted.python import util, context, reflect
By the way, Volker, this is not fixed by
http://trac.sagemath.org/sage_trac/ticket/11819, since 'new' is imported by
twisted, not just by the Sage library.
--
John
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
Salfelder fe...@salfelder.org
wrote:
On Tue, Sep 20, 2011 at 12:55:32PM -0700, John H Palmieri wrote:
Should sage-preparse name the preparsed file something safer, in order
to
prevent name clashes like this? For example, turn FILE.sage into
FILE_preparsed.py?
Hi.
while You
On Friday, September 16, 2011 2:17:17 PM UTC-7, daveloeffler wrote:
Right, so now I have a skynet account, and I tried to grab a copy of
Sage and build it on the |Skynet SunOS machine mark. It got as far
as gnutls and then died:
serv.o: In function `peer_print_info':
On Friday, September 16, 2011 2:17:17 PM UTC-7, daveloeffler wrote:
Right, so now I have a skynet account, and I tried to grab a copy of
Sage
By the way, you can find tar files for several versions of Sage in
/home/buildbot/build/sage/src/
on the skynet machines.
--
John
--
To post
801 - 900 of 1458 matches
Mail list logo
