Hi,
there's another possibility to speed up the Sage release frequency, by
a certain parallelization.
Currently, the Sage releases are done sequentially, and in two phases:
- the "alpha" phase, where tons of tickets are merged, and new
functionality gets in
- the "release cadidate" phase, where
+1 to option (3).
Cheers, Georg
--~--~-~--~~~---~--~~
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.
What I currently miss is the possibility to cross-compile Sage.
I heartily would like to build the MacPPC Sage version on my MacIntel.
The OS infrastructure is well prepared for this, any Xcode brings
everything with it to do that. But I don't know whether (or how) I
could tell Python/Cython to c
> On PPC OS X 10.4, Sage doesn't build at all for multiple reasons.
> Either we fix this or deprecate PPC 10.4 support completely. I think
> deprecation is a fair option, since it's an OS that is 2 versions
> behind:
> #7107 sage does not build on ppc os x 10.4 anymore, failing with
>
On 29 Sep., 14:27, Marshall Hampton wrote:
> Sounds like a good idea. I think you've done a great job on the
> recent releases.
+1
Cheers,
Georg
>
> Thanks,
> Marshall
>
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
> On Mon, Sep 28, 2009 at 7:57 AM, John Cremona wrote:
>
> > Two test failures on 32-bit ubuntu:
>
> > sage -t "devel/sage/sage/crypto/boolean_function.pyx"
>
> > sage -t "devel/sage/sage/rings/polynomial/pbori.pyx"
The former already has a positive review at trac #7020, and latt
Well,
hopefully my review comments are helpful!
Cheers,
Georg
--~--~-~--~~~---~--~~
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, visi
Hi William,
on Cygwin.org (see "http://cygwin.com/cygwin-ug-net/ov-ex-win.html";),
they recommend to search for "UNIX basics" and "UNIX tutorial".
Doing so yields e.g.:
http://www.ee.surrey.ac.uk/Teaching/Unix/
where you can find a browser- or offline-readable "UNIX Tutorial for
Beginners", whi
Hi,
concerning the libsingular/readline problem, I think that we "just"
should have added the Singular spkg as a new dependency for the
upgrade (because the Python extensions in the Sage library using it
depend on the readline library, see "module_list.py").
Simply rebuilding the Singular spkg (
Hi Minh,
obviously (look at your own trace output), you are talking about
"singular-3-1-0-4-20090818.spkg", not
"singular-3-1-0-4-20090723.spkg".
Just looking at the top entries of the "SPKG.txt" file of the old
(Sage-4.1.1) "singular-3-1-0-2-20090620.p0.spkg", and of the current
Sage-4.1.2-alph
Hmmm,
intriguing. Unfortunately, I have currently no time whatsoever to
spend on this issue, but let me know, what the outcome is, thanks!
Cheers,
Georg
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from t
Hi David,
looking at the $SAGE_ROOT/makefile and $SAGE_ROOT/spkg/install
scripts, and a newly unzipped Sage source distribution, one sees that
"prereq" does not lie in the directory $SAGE_ROOT/spkg/standard/ but
in $SAGE_ROOT/spkg/base/. The latter directory does not exist in Sage
binary distribu
Hi guys,
hopefully we're getting closer to the root of the misunderstanding(s)
here. Under Mac OS X, things might not be as you expect them to be,
given that "gcc" (or some version of it) is used. I've tried to help a
bit with libSingular in the past, from there my experience stems from.
Let's s
> and it bugs me that I have to type
>
> :math:`\eta`
>
> instead of just $\eta$. So how about submitting a patch to sphinx fixing it?
+1
Cheers,
Georg
>
> Ondrej
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubs
Yes,
I do agree that "uintptr_t" is a better choice.
It's also part of the ISO C99's "Stdint.h". Note that we only would
need this latter header (or rather the type(def)s contained therein),
and possibly the corresponding "printf formatting magic". ISO C99 is a
standard for a decade now.
Even if
Hi Dave,
I'd propose to use ISO C99 notation from "Stdint.h", e.g. "uint64_t",
and do the count in bytes.
This standard notation is even usable on Windows.
(See also http://en.wikipedia.org/wiki/Stdint.h)
Cheers,
Georg
--~--~-~--~~~---~--~~
To post to this group,
Hi John,
I don't remember the thread(s), but there have been problems with the
"readline" library on Suse systems in the past. Michael Abshoff would
know instantly what the problem was, and what the measures taken were
back then. There was talk about delivering a "readline" with Sage, but
I don't
Hi David,
concerning your original question:
In Debian sid (==unstable currently), there are Maxima version 5.17.1,
and ECL version 9.6.1.
These versions are more recent than what currently comes with Sage.
But if we grade up to Maxima version 5.19.0 and ECL version 9.8.3,
these versions were mor
> 7. I have no problem with summer-of-code high school or college or ...
> students writing programs. Relying on this code as part of the core of
> a system is however not such a great plan.
>
> RJF
I allowed myself to answer to this point ("7.") on sage-flame.
Cheers,
Georg
--~--~-~--
Hi,
#6717 just got a quick review, and a positive one (thanks, Burcin!).
As for the "twisted.py" failure: I did immediately retry it after the
full Sage testlong suite, and it had failed again. But on fifteen more
runs right now, I saw only two failures, and thirteen successes. The
system load w
Hi,
on Mac(Intel) OS X 10.4.11 (XCode 2.5 / gcc 4.0.1 build "5370"), Sage
4.1.1.rc2 builds fine.
However, there are two (reproducible) doctest failures, one known one
and one I never saw before. The known one is:
sage -t -long "devel/sage/sage/symbolic/expression.pyx"
***
On 8 Aug., 18:54, William Stein wrote:
> David,
>
> See below for some data related to allowed GCC versions. Basically, on OS
> X, "build 5465" is too old.
>
> This is the version I have on bsd.math.washington.edu, so I'll probably see
> the same problem as soon as I upgrade. I'll thus upgra
On 5 Aug., 19:15, VictorMiller wrote:
> Ok, I think I've found the problem. Perhaps this should point to the
> need for making clear and complete instructions about creating your
> own copy.
>
> I found that in my local copy there was a sage script that pointed to
> the systemwide sage. When I
Hi,
On 5 Aug., 11:59, David Kirkby wrote:
> I want to change the file prereq-0.3/configure.ac to make a new
> prereq-0.4/configure script, as currently the configure script does a
> few things I think are wrong.
>
> 1) If CC is set to a non-GNU compiler, the configure scripts tests the
> version
Guess 2:
You need to "run" this new copy of Sage at least once, i.e. type just
"mysage" to start the Sage interpreter.
Sage recognizes that "itself" has been moved, and re-generates certain
hard-linked paths.
Have a look at (with probably $SAGE_ROOT == ~/mysage in your case)
the contents of the
Hi,
at least these lines (and there are others):
**
File "/home/mvngu/usr/bin/sage/devel/sage-main/sage/interfaces/
sage0.py",
line 320:
sage: sage0.eval('2+2')
Expected:
'4'
Got:
'\x1b[0m'
**
On 29 Jul., 16:06, William Stein wrote:
> On Wed, Jul 29, 2009 at 7:02 AM, mirko wrote:
>
> > Hi,
>
> > I tried downloading the source for sage-4.1 and simply running a
> > 'make' from the directory. I was told it would just work. Well, it did
> > not. I got the following message.
>
> > sage: A
>
> Um... no. Can you please create a ticket for this?
>
This is now http://trac.sagemath.org/sage_trac/ticket/6649 :
"[with patch, needs review] doctest failure in decorate.py (on OS X
only)".
Cheers,
Georg
> --
> Regards
> Minh Van Nguyen
--~--~-~--~~~---~--~~
Aha,
On 28 Jul., 09:05, Minh Nguyen wrote:
> Hi Georg,
>
>
>
> On Tue, Jul 28, 2009 at 3:58 PM, gsw wrote:
>
> > Hi,
>
> > builds fine on MacIntel (32bit) OS X 10.4, but there are
Hi William,
On 28 Jul., 05:01, William Stein wrote:
> Hi,
>
> I took the sage-4.1.1.alpha1 release build I had, then did "./sage
> -bdist", took the result, extracted it, and did "make test".
>
> 1) It sits there and builds the documentation again, which takes a
> *long* time. It shouldn't do
Hi,
builds fine on MacIntel (32bit) OS X 10.4, but there are four (long)
doctest failures:
--
The following tests failed:
sage -t -long "devel/sage/sage/misc/abstract_method.py"
sage -t -long "devel/sage/sage/mi
> > sage -t -long "devel/sage/sage/interfaces/r.py"
> > **
> > File "/Applications/sage_builds/sage-4.1.1.alpha0/devel/sage/sage/
> > interfaces/r.py", line 838:
> > sage: r.completions('tes')
> > Expected:
> > ['testPla
On 21 Jul., 22:13, Robert Bradshaw
wrote:
> On Jul 21, 2009, at 11:25 AM, kcrisman wrote:
>
>
>
> > On Jul 21, 1:14 pm, Žiga Lenarčič wrote:
> >> Hi!
>
> >> After downloading sage I read readme.txt.
>
> >> If there is interest in getting Sage into an .app, it can be done via
> >> a free Platyp
On 21 Jul., 17:14, John H Palmieri wrote:
> On Jul 20, 8:04 pm, Minh Nguyen wrote:
>
> > Hi folks,
>
> > This is the first release of the Sage 4.1.1 release cycle. William and
> > I are co-chairing this release cycle. The source tarball and the
> > sage.math only binary are available at
>
> >h
On 17 Jul., 00:36, William Stein wrote:
>
> That said, I *do* think it is a good idea to considering getting
> Frobby into standard Sage, simply because it provides much new
> optimized functionality. That said -- I want to ask a question of
> people who are voting +1 to this proposal: have
On 20 Jul., 19:42, William Stein wrote:
> On Mon, Jul 20, 2009 at 10:33 AM, gsw wrote:
>
> > Hi,
>
> > I'm downloading these sources (the file name is "sage-4.1.comb.tar"
> > BTW, i.e. without "inat") and will build a Mac OS X 10.4 32bit Int
Hi,
I'm downloading these sources (the file name is "sage-4.1.comb.tar"
BTW, i.e. without "inat") and will build a Mac OS X 10.4 32bit Intel
version (I can't build 64bit versions for the time being), which
should work fine on OS X 10.5 (on a MacIntel), too. I'll post a note
with the link to the r
Hi Carlo,
strange indeed. I looked at log you posted, several spkg's install
fine, e.g.:
libgpg_error-1.6.p1
Machine:
Linux snehurka 2.6.18 #6 SMP Mon Nov 27 17:53:06 CET 2006 x86_64 GNU/
Linux
Deleting directories from past builds of previous/current versions of
libgpg_error-1.6.p1
Extracting p
On 16 Jul., 15:20, Bjarke Hammersholt Roune
wrote:
> Frobby is currently an optional component of Sage, which performs
> computations related to monomial ideals. In particular, it can compute
>
> * Multigraded Hilbert series
> * Alexander dual of monomial ideals
> * Maximal standard monomial
Hi Martin,
On 15 Jul., 13:25, Martin Albrecht
wrote:
> Hi there,
>
> next week I'll visit the Singular group in Kaiserslautern. As a part of my
> visit I will give a talk on Sage. The talk will be focused on topics I assume
> to be relevant to the Singular team.
>
> I have uploaded a draft of my
Hi Max,
On 11 Jul., 17:56, Maximilian Nickel wrote:
> Hi,
> i've just created a simple script that creates an OS X application
> bundle for Sage. The usage is pretty simple, just copy the sage
> directory from the .dmg into the directory of the script and run 'make
> release'.
> I thought it mig
On 11 Jul., 11:53, Ralf Hemmecke wrote:
> > from the tone of your message, it seems to me, that I somehow must
> > have "stepped onto your toes" --- sorry, that was not at all my
> > intention! And I couldn't imagine that someone would be offended by me
> > signing my messages with my nickname
On 10 Jul., 23:07, Ralf Hemmecke wrote:
> Hi GSW, -- don't you have a real name?
>
> On 07/10/2009 10:37 PM, gsw wrote:
>
> > Hi Ralf,
>
> > On 9 Jul., 12:00, Ralf Hemmecke wrote:
> >> I seem to be out of luck. But maybe I did something wrong.
>
uot;spkg/
build/") were deleted. Look in "spkg/build" during compilation time,
or use e.g. "./sage -f -s atlas-3.8.3.p3" instead of "./sage -f
atlas-3.8.3.p3" (i.e. with an additional "-s") to prevent the deletion
of the intermediate files there.
> Any hint is
Hi,
we're a atep further with regard to the OS X / Singular 3.1.0.4
problem; see my comments at
http://sagetrac.org/sage_trac/ticket/6362#comment:29.
There does seem to remain one more issue, but let's see.
Cheers,
gsw
--~--~-~--~~~---~--~~
To po
On 5 Jul., 23:06, Simon King wrote:
> Hi Georg,
>
> On 5 Jul., 22:13, gsw wrote:
>
> > first of all, "sage-check" is something specific to Sage.
>
> Do you mean spkg-check? But sure, this is Sage specific as well, since
> AFAIK spkg stands for Sage packa
On Mac OS X 10.4, too, singular fails to build (see the message from
John H Palmieri above).
It seems that (see trac #6362) the update from Singular 3.1.0.2 to
Singular 3.1.0.4 did have an unwanted side-effect ... thoughts?
Cheers,
gsw
--~--~-~--~~~---~--~~
To
On 5 Jul., 19:04, Bjarke Hammersholt Roune
wrote:
> Hi gsw,
>
> Thank you for looking at the Frobby-Cython ticket. According to the
> Cython FAQ, pxd files are preferred over pxi files, unless the file
> has to contain code rather than just declarations. The file in
> ques
atform dependencies, and the like.
So the spkg-check scripts in general are not at all called by the
users. But they are very helpful for integrators, should any problems
arise. So the output should be reproducible, and a kind of "test.log"
is always a good idea.
If this doe
files (that is, if someone volunteers to do it)
Is there something I am missing here / am I wrong?
Cheers,
gsw
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsub
For #6448, I just uploaded a patch, that now needs review.
Could someone please also have a look at the doctest patch at #6379
and review it (very easy one)? Thanks!
Cheers,
gsw
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel
nd of course, I'm happy not only to answer a question
or two, but to try to improve the documentation in such a way, that
others will find these answers, too, should they have the same
questions.
Or do you have a better idea/name for the above than
"sage.libs.playground"?
Cheers,
gsw
to any details --- who of you would like to discuss with
me any next steps, and/or the general direction to go?
Cheers,
gsw
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-dev
..
I'm currently downloading Sage-4.1.alpha1.tar.
Cheers,
gsw
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit t
avior that '+' gives (limit the number of
> invocations of grep) and stay portable.
>
>
>
> > Bingo!
>
> > find Desktop/sage-4.1.alpha1/devel/sage/sage// \( -name *.py \) -exec
> > grep -i -H Palmieri {} \;
>
This one works on both boxes, too, but behaves
On 26 Jun., 18:23, rjf wrote:
> On Jun 25, 1:10 pm, gsw wrote:
>
> > Hi,
>
> > I suspect you're just running out of RAM.
> > Not necessarily physically, but the construction Sage --> expect
> > interface --> Maxima --> Lisp implementation i
ersion (maybe the clisp ---> ecl switch does
heal your problem, or the pynac switch, or ...)
Good luck!
Cheers,
gsw
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-deve
t to "needs work".
It's clearly is the reason for this brokenness, and wasn't tested on
Mac OS X 10.4 at all. As it is stated in its comments.
Cheers,
gsw
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsu
e where the message(s) given back by R
are parsed. Now this (hopefully) is done locale-independent, at least
it works for english and german locale alike (and should for any
locale).
In the end, the patch at #2513 definitely was one in the right
direction.
If not necessary, we should not rule out
the
(greater) precision of the other part.
c) If so, I would consider this behaviour a bug in pari, to be fixed
in pari.
d) In the meantime, you propose as a workaround to alter the
conversion behaviour from pari to Sage for complex numbers in general.
If I got right --- I vote +1 for your p
On 21 Jun., 15:37, William Stein wrote:
> 2009/6/21 gsw :
>
>
>
>
>
> > On 21 Jun., 08:28, Simon King wrote:
> >> Dear all,
>
> >> athttp://groups.google.com/group/sage-support/browse_thread/thread/5343...
> >> I was asking about the
me of the libraries present in Sage-4.0.2 will switch to GPLv3+. On
the other hand, currently "all is fine". My proposal therefore is the
following:
Let's set up a regular time frame to publicly revisit the Sage
licensing, say in yearly intervals.
For this year, I'd vote to
On 19 Jun., 08:28, gsw wrote:
> > I checked back for the my Sage-4.0.1 Intel Mac OS X 10.4 build and
> > unfortunately yes, this problem is there, too --- so the currently
> > bdist'ed version is flawed :-/
> > I don't seem to have my Sage-4.0 logs anymore, bu
is...
>
> On 20 Jun., 22:10, gsw wrote:
>
> > On 20 Jun., 08:15, Simon King wrote:
> > > Apparently the difference lies in Sage and not in my tests. I just
> > > tried again the exact setting in which testing my extension modules
> > > used to work -- no
several releases until I get anywhere, however. I never looked at
"parallel building" or the r.spkg / rpy.spkg before.
Cheers,
gsw
>
> -cc
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from th
On 19 Jun., 08:21, gsw wrote:
> Hi,
>
> r/rpy does not build reliably for me anymore using " export MAKE='make
> -j2' " on my MacIntel Core2Duo / Mac OS X 10.4.11. I reported this
> already for Sage-4.0.2.rc0 (in a one-message thread :-) ) thinking
> that
as which recent changes between 3.4.2 and 4.0.1 could
have triggered this "make -j2" regression?
(Apart from that, Sage-4.0.2.rc3 did build and "make testong" fine,
with one other exception: /interfaces/ecm.py did timeout after 1800
seconds, but this was not reproducible
e (and means to automate its usage, and really use it, ...),
before changing the directory structure that the users currently are
acquainted to.
Cheers,
gsw
P.S.:
And I didn't even tell you yet about all the Sage "Mac App" variants
of the Sage versions above :-)
--~--~-~--~-
code yourself, correct it
grammatically and mathematically, add the missing doctests, write some
documentation, appease/bribe/whatever the release manager(s) to get it
finally in, ...)
Craig, you're certainly not the only one liking this idea!
Cheers,
gsw
--~--~-~--~~
pecially, if you're going to rotate fast through the half dozen guys
you mentioned.
Cheers,
gsw
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@google
when I had tested Sage-4.0.rc2 with "MAKE
testlong". John was using a Mac with OS X 10.5, I saw it on a MacIntel
with OS X 10.4, so this might be OS X specific. Or a timing issue/race
condition (I was using MAKE='make -j2'; both for Sage-4.0.rc2 and
Sage-4.0). Or whatsoever.
A
gt; and should simply be reimported. It would also be good if someone
> could deal with trac accounts since I am not likely to be around much
> in the next four weeks.
>
Hi Michael,
standing ovations, and thanks a lot for your good work!
C
;to build sage, simply type:
make", on a lot of systems at the same time. And something like a "no
custom C...Flags" patch might have problems on its own ...
Cheers,
gsw
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegro
include"
CPPFLAGS="-I/sw/include"
CXX="g++"
CXXFLAGS="-I/sw/include"
MPN_PATH=" powerpc32/vmx powerpc32 powerpc32 generic"
So there is some misconfiguration happening --- the mpir maintainers
probably will find a solution quickly.
uot;with patch enhancement trac ticket". At least from my point of view,
I do see advantages in eclib keeping its mercurial repo.
Cheers,
gsw
>
> John
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe fro
't wait for other issues in #4857 to get resolved. Sorry if I'm
> stepping on any toes here.)
I fully agree (and just gave #5990 a "positive review minus epsilon"),
and I definitely am being happy that you stepped forward!
Cheers,
gsw
>
> John
--~--~-~--~
76 matches
Mail list logo
