[sage-devel] Making Integer and Rational compatible with Python Fraction

v/peps/pep-3141/#numeric-classes> I would also like to emphasise that although only these six approaches were discussed during the workshop, there may well be others. Therefore others should be encouraged to alternative approaches so that these can all be discussed together. Regards, Mark Bell --

[sage-devel] Re: Compilation error: 'sage/ext/interrupt.pxi' not found

Hello, I'm getting the same "InternalError: Internal compiler error: 'sage/ext/interrupt.pxi' not found" when trying to build sage 8.7 with the command ./sage -b on MacOS Mojave. This happens after I added a new folder in sage-8.7/src/sage. As I understand it's deprecated, I replace include "s

[sage-devel] Re: Missing Sage 8.2 binaries

> > > On Tuesday, May 8, 2018 at 8:54:42 PM UTC+2, Mark Bell wrote: >> >> The main sagemath.org page lists Sage 8.2 as the latest version to >> download and the source and git links appear to be tagged as sage-8.2 as of >> three days ago. However within the main downl

[sage-devel] Missing Sage 8.2 binaries

The main sagemath.org page lists Sage 8.2 as the latest version to download and the source and git links appear to be tagged as sage-8.2 as of three days ago. However within the main download page, there don't appear to be any precompiled versions of 8.2 available. For example here: http://f

[sage-devel] Typo in trac instructions

I think there is a minor typo in the *To get an account* instructions at https://trac.sagemath.org/. It says that: the default username is the first letter of the surname followed by the > name (i.e. mjohnson for Mike Johnson or tlei for Tan Lei). Should this not say: the default username is

[sage-devel] _integer_ for QQbar and QQ raise different errors

The coersion sage: ZZ(1/2) fails and (correctly) raises a TypeError while sage: ZZ(QQbar(sqrt(17))) fails and (incorrectly) raises a ValueError. This has several knock on effects, in particular vector(ZZ, [list of algebraic numbers]) all of whoms try / except blocks are set up to catch a

[sage-devel] Re: Polyhedron.integral_points_count() gives inconsistent answers on slices

Ah, I see. Is it possible that by doing "sage -i latte_int" I have installed a different version of 4ti2 than the one that CoCalc uses? I'm still not sure why (without this option) I see different behaviours on my machine and on CoCalc. If it matters I have Sage 8.0 running on Mac OS Sierra 10.

[sage-devel] Re: Polyhedron.integral_points_count() gives inconsistent answers on slices

Excellent! Adding the option prevents the crash. So on CoCalc (and locally) I can do: print(P.integral_points_count(preprocess=False, triangulation='cddlib')) And it prints out 19958. Without this extra option this example crashes on CoCalc but runs fine locally. What is this this option doin

Re: [sage-devel] Re: Polyhedron.integral_points_count() gives inconsistent answers on slices

; Can you show the output of the crash on CoCalc? > > Also, the crash could just be running out of memory... > > > > > > > On Saturday, November 4, 2017 at 3:46:01 PM UTC-7, Mark Bell wrote: > >> > >> Thanks! > >> > >> I'm

[sage-devel] Re: Polyhedron.integral_points_count() gives inconsistent answers on slices

Here is the full CoCalc output when I run "sage error.py" in a terminal, either via the web interface or via sshing into the machine: Traceback (most recent call last): File "error.py", line 42, in print(P.integral_points_count(preprocess=False)) File "/ext/sage/sage-8.0/local/lib/pytho

[sage-devel] Re: Polyhedron.integral_points_count() gives inconsistent answers on slices

Thanks! I'm not sure if this is the right place to add this but the attached example also causes LattE to crash, but I only see this behaviour when I run this code on CoCalc. When I run the script on my local machine with latte_int installed it completes and prints out 19958. Surely this isn't

[sage-devel] Re: Polyhedron.integral_points_count() gives inconsistent answers on slices

So when k = 19, sage.interfaces.latte.count and P.integral_points_count() give different answers. This seems to be the cause of the difference. Here is some more code showing the difference. -- You received this

[sage-devel] Re: Polyhedron.integral_points_count() gives inconsistent answers on slices

Great suggestion. Could you ask polymake to compute what the number of lattice points in each x_0 = k (for k = 1, ..., 100) slice? Does it match: [84, 84, 84, 81, 81, 81, 75, 75, 75, 66, 66, 66, 54, 54, 54, 39, 39, 39, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0

[sage-devel] Polyhedron.integral_points_count() gives inconsistent answers on slices

points_count() for k in range(1, 101)] [84, 84, 84, , 0, 0, 0] Which is fewer points in total: > sum(_) 1197 Can anyone reproduce this? Is this a bug in Sage or LattE? I'm using Sage 8.0 with LattE installed via "sage -i latte_int" and have attached the full example code.

[sage-devel] What exactly is R.gens() suposed to return?

There are some inconsistencies in the way `gens`, `gens_dict`, and `gens_dict_recursive` work in rings. There's some old questions on `gens` in https://groups.google.com/forum/#!msg/sage-devel/BRE2F90oezU/xmKC86SRllEJ;context-place=forum/sage-devel, and some more discussion in trac 22514. The

[sage-devel] Testing new graph algorithms

I've been working on some new algorithms for computing some properties (eccentricity, diameter, radius, ...) of (undirected) graphs and I'm looking for families to test these on. I've written a reasonable efficient C extension which implements these algorithms and so I've started comparing thes

[sage-devel] Inverting Integers gives different behaviour than in Python

In Python for an integer x, its invert ~x is defined to be its two-complement and is given by -1-x. On the other hand, in Sage Integers (from sage.rings.integer.Integer) have their __invert__ defined to be 1 / self

[sage-devel] Re: sage make fail @ ntl

help ! Mark -- 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@googlegr

Re: [sage-devel] sage make fail @ ntl

ome/modell/pkg/sage/sage-6.3/local/include/NTL/version.h # owner: modell # group: irsa user::rw- group::r-- mask::rwx other::r-- On Friday, August 22, 2014 12:01:35 PM UTC-7, Jori Mantysalo wrote: > > On Fri, 22 Aug 2014, Mark ODell wrote: > > > cp: preserving ACL for > >

[sage-devel] Re: sage make fail @ ntl

modell@bacchus$ mount /dev/xvda1 on / type ext3 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pip

[sage-devel] sage make fail @ ntl

ble building ntl. All the "Operation not supported" complaints are concerning, but maybe nothing. Thanks, Mark modell@bvacchus$ make . . . cp: preserving ACL for `/home/modell/pkg/sage/sage-6.3/local/include/NTL/version.h': Operation not supported cp: preserving perm

[sage-devel] sage make fail @ ntl

ble building ntl. All the "Operation not supported" complaints are concerning, but maybe nothing. Thanks, Mark modell@bvacchus$ make . . . cp: preserving ACL for `/home/modell/pkg/sage/sage-6.3/local/include/NTL/version.h': Operation not supported cp: preserving perm

[sage-devel] Re: [sage-combinat-devel] how to cure TestSuite failures involving Homs

basis" function to feed to module_morphism. There is no natural "home" for such functions, which are somewhat complicated and are created each time someone wants to tensor some morphisms. It makes no sense for these functions to be lexically tethered somewhere, which is what the pi

[sage-devel] Re: [sage-combinat-devel] how to cure TestSuite failures involving Homs

Homs, please add identity morphisms as category-flavored wrappers around a single little pure identity function, and the knowledge to the Hom code that the identity morphism composes trivially. --Mark -- You received this message because you are subscribed to the Google Groups "sage-deve

[sage-devel] Re: [sage-combinat-devel] how to cure TestSuite failures involving Homs

g to work if the method is called multiple times because the global reference will get overwritten. Solutions? --Mark -- 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, sen

[sage-devel] how to cure TestSuite failures involving Homs

Is there an easy way to get rid of the following TestSuite failures? Or does it require an overhaul of how sage handles morphisms? I understand why the first two tests fail. --Mark sage: F=CombinatorialFreeModule(ZZ,[1]) sage: def on_basis(x): ... return x

Re: [sage-combinat-devel] Re: [sage-devel] Re: Call for vote about ticket #10963: axioms and more functorial constructions

. In the meantime, we all need a version of sage to work with... --Mark -- 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...@googlegro

[sage-devel] problem building 5.2 from source

Tried to build version 5.2 from source. The make failed. Computer: Fujitsu Lifebook T900 Operating System: uname -a returns 3.5.0-2.fc17.x86_64 #1 SMP Mon Jul 30 14:48:59 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux (part of the error log follows) --

[sage-devel] Re: More bugs in Laurent polynomials?

re > the existence of basic coercion maps is defined. However, K is a generic > fraction field - it would be very bad style to have tests for "Laurent > polynomial rings" in a very general method. Yeah, how can K generally know about some "random" subring like S? I

[sage-devel] Re: More bugs in Laurent polynomials?

tor() sn.factor() > The last line will show you the source code, and you will see that it > is attempted to factor numerator and denominator. As it turns out, the > problem lies in the factorisation of Laurent series. The problem occurs when the Laurent polynomial ring unit element i

[sage-devel] More bugs in Laurent polynomials?

Bug report: I encountered some weird behavior in LaurentPolynomialRing, such as the nontransitivity of the '==' relation. Also, factoring in the fraction field caused an error. See below. Feature request: I would like elements of the fraction field F of a Laurent polynomial ring S (say with base

[sage-devel] creating custom subclasses of polynomial rings

nfused at the organizational principle behind the following output. sage: R = PolynomialRing(QQ,['x']) sage: R.__class__ sage: R.an_element().__class__ sage: S = PolynomialRing(QQ,['x','y']) sage: S.__class__ sage: S.an_element().__class__ --Mark -- To post

[sage-devel] Re: Cython debugger; GSOC

On Mar 21, 11:28 pm, Mark Florisson wrote: > On Mar 21, 8:06 pm, Robert Bradshaw wrote: > > > To use this Cython debugger one must start up Sage under gdb. > > (Essentially, this is sage -gdb that knows about Python/Cython, which > > is really nice.) I don't think

[sage-devel] Re: Cython debugger; GSOC

On Mar 21, 7:42 pm, David Roe wrote: > Hi everyone, > There is now a Cython debugger > (http://docs.cython.org/src/userguide/debugging.html).  It would be great if > this functionality were tied into the python debugger, so that (after you > compiled your program with some flags perhaps and sta

[sage-devel] Re: Cython debugger; GSOC

On Mar 21, 8:06 pm, Robert Bradshaw wrote: > To use this Cython debugger one must start up Sage under gdb. > (Essentially, this is sage -gdb that knows about Python/Cython, which > is really nice.) I don't think one could just drop down into it from > pdb. (Adding Cython support for pdb would be

[sage-devel] consistent trouble building sage from source

generated. Dunno how to attach it though (through this google-group interface). --Mark gcc -DL2SIZE=4194304 -I/home/msshimo/sage-5.0.beta8/spkg/build/ atlas-3.8.4.p1/ATLAS-build/include -I/home/msshimo/sage-5.0.beta8/spkg/ build/atlas-3.8.4.p1/ATLAS-build/../src//include -I/home/msshimo/ sage

[sage-devel] Re: Useful link - internal algorithms used by Mathematica

On Nov 8, 12:34 am, Tom Boothby wrote: > I was referring to the webpage, and not the journal article, lest I be > further accused of illicit drug use. As RJF said, that's part of the standard documentation and goes back as far as I can recall. It's in the Mathematica Book for version 2. -- To

[sage-devel] Re: Useful link - internal algorithms used by Mathematica

On Nov 7, 7:22 pm, Tom Boothby wrote: > Hey, that's pretty neat!  I wonder if this is a direct response to our > public criticism of their (extreme lack of) openness? > ... > > Mark Sofroniou (one of the numerical algorithm developers at Wolfram > > Research) and Gi

[sage-devel] Re: Sage and commercial software

On Nov 23, 11:01 pm, mhampton wrote: > I thought that Mark McClure's post on another thread raised some > interesting issues, and that it was worth responding to, but it was so > tangential that it deserves a seperate thread: Thank you to Marshall for a thoughtful response. I a

[sage-devel] Re: A Sage NSF proposal to the Computational Mathematics Program

who don't feel philosophically bound to open source"? Sage cannot expand to the 10^6 level by alienating these types of users. Mark -- 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...@googleg

[sage-devel] Re: A Sage NSF proposal to the Computational Mathematics Program

in the development of numerical software (both commercial and free) for many years. Thus, I really feel that your desire to "put Mathworks out of business" is misdirected, particularly in the context of your current grant proposal. Mark McClure -- To post to this group, send an email to

[sage-devel] Re: bug in plot3d?

experiencing this? I get the same behavior with plot3d and with parametric_plot3d. I seem to recall mesh=True working properly a few versions ago. Mark McClure --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe fro

[sage-devel] Re: sage-4.0

ng './sage -bdist 4.0', but there might be an environment variable I need to set first? What is the correct command sequence to build the app? Thanks, Mark McClure --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To un

[sage-devel] Re: What should happen if you type 'notebook()' ?

On May 30, 1:42 pm, Mike Hansen wrote: > On Sat, May 30, 2009 at 10:28 AM, mark mcclure wrote: > > On my Mac, Firefox opens up automatically.  How do you access the > > notebook on Windows, though?  I haven't figured out how to do so, > > presumably since the b

[sage-devel] Re: What should happen if you type 'notebook()' ?

eb browser > (go to the address noted above). On my Mac, Firefox opens up automatically. How do you access the notebook on Windows, though? I haven't figured out how to do so, presumably since the browser is a native Windows application, while S

[sage-devel] Re: Maple 13

On May 20, 6:19 pm, Stephen Forrest wrote: > 2009/5/18 mark mcclure > > > Here are a couple of graph theoretic timing comparisons > > between Sage 4.0.alpha0 and Maple 13.  They were > > performed on my Macbook Pro running OSX 10.4.11. They > > indicate that Maple

[sage-devel] Re: Wolfram Alpha and Google (Trendalyzer)

On May 20, 9:57 am, Jason Grout wrote: > Vinzent Steinberg wrote: > > On May 19, 2:25 pm, mark mcclure wrote: > >> On May 19, 2:08 am, Jason Grout > >> Not necessarily.  Evidently, there will be an API interface to > >> Wolfram Alpha that would, presum

[sage-devel] Re: Wolfram Alpha and Google (Trendalyzer)

Sage interface to Alpha... Not necessarily. Evidently, there will be an API interface to Wolfram Alpha that would, presumably, have its own terms of use. Although, exactly what the use of a programmatic interface to a web-site that offers a lot of answers to relatively vague questions is not

[sage-devel] Re: Maple 13

ory); n := 5; t := time(); mygraphs := NonIsomorphicGraphs(n, output = graphs, outputform = graph); time()-t isomorphicpairs := false; t := time(); for i to NonIsomorphicGraphs(n) do for j from i+1 to NonIsomorphicGraphs(n) do if IsIsomorphic(mygraphs[i], mygraphs[j]) then isomorphicpairs

[sage-devel] Re: 3.4.2 64 bit MacIntel 10.5 binary with only *one* doctest failure

s command on my 32 bit version. I expected this, since I've noticed the same behavior in 64 bit Mathematica, Matlab, and C, but it makes me wonder why we should be excited about 64 bit systems. Mark McClure --~--~-~--~~~---~--~~ To post to this group, send

[sage-devel] Re: Wolfram Alpha and Google (Trendalyzer)

that one tool can do that another cannot. I, for one, will happily continue to use all types of mathematical software. Mark --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send ema

[sage-devel] Re: Wolfram Alpha and Google (Trendalyzer)

a debate on this. On the contrary, my views are probably closer to the open source philosophy than Wolfram's "Why You Do Not Usually Need to Know about Internals" philosophy. That's just not where my skill set is. Mark --~--~-~--~~~---~--~~ To

[sage-devel] Re: Wolfram Alpha and Google (Trendalyzer)

On Apr 29, 1:37 pm, William Stein wrote: > On Wed, Apr 29, 2009 at 9:51 AM, mark mcclure wrote: > > > I think, though, that the statement that you need open source in order > > to have verifiable results is not really true. The fact is that bugs are > > found via experim

[sage-devel] Re: Wolfram Alpha and Google (Trendalyzer)

Remember also that n (10) specifies 10 bits of precision or about 3 digits. The following works: sage: sin(10^50).n(200) -78967249342931008271028953991740775396008340462140271914578 Mark --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegr

[sage-devel] Re: Wolfram Alpha and Google (Trendalyzer)

On Apr 29, 11:06 am, William Stein wrote: > On Wed, Apr 29, 2009 at 6:20 AM, mark mcclure wrote: > > The Q&A session includes several pointed > > questions surrounding open source and freedom of access > > to data. Some folks here might find the responses > > int

[sage-devel] Re: Wolfram Alpha and Google (Trendalyzer)

estion occurs about 1 hour 19 minutes into it. Mark McClure --~--~-~--~~~---~--~~ 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

[sage-devel] Re: [sage-devel][P=NP] On The Nature of Computational Complexity

= N P) >     [N == 1] What about P==0? That must be the interesting part. :) Mark McClure --~--~-~--~~~---~--~~ 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 F

[sage-devel] Re: Elementary Number Theory quickref

the card. I found Robert Bradshaw's code for complex_plot in trac so, presumably you're working with a patched or otherwise more recent version. The complex_plot looks great so I'm looking forward to trying it. Mark McClure --~--~-~--~~~---~--~~ To pos

[sage-devel] Re: Integration Development

On Mar 7, 5:47 pm, Robert Dodier wrote: > mark mcclure wrote: > > (%i1) integrate(1/x^3, x, 1, inf); > > Integral is divergent > > It's been fixed in CVS, so it will be in the next release. That's great Robert, thanks! Mark --~--~-~--~~~-

[sage-devel] Re: Integration Development

perform these > > integrals. > > For the record, what are some of integrals you tried? > ... > At present Sage punts to Maxima to compute integrals. Here's one of my least favorite examples: --- Maxima 5.17.1 session --- mark-mcclures-computer-2:~ markmcclure$ rm

[sage-devel] Re: Slowdown in is_isomorphic?

me wonder if I'm doing anything wrong in my code. The exact code I used to produce my originally posted timing results is below. My machine is a MacBook Pro running Sage 3.3 on OSX 10.4.11. I haven't tried your patch, but I'm looking forward to it. Mark --

[sage-devel] Re: help? doesn't work in sage 3.3 notebook

On Feb 27, 7:44 am, mabshoff wrote: > On Feb 27, 4:24 am, mark mcclure wrote: > > > The basic help mechanism doesn't seem to work in the the sage 3.3 > > notebook. > > I just checked and get the following on OSX: > >  * the 3.3 notebook 3.3 started fro

[sage-devel] Re: help? doesn't work in sage 3.3 notebook

On Feb 27, 7:44 am, mabshoff wrote: > On Feb 27, 4:24 am, mark mcclure wrote: > Overall I am tending to disable App bundles for 3.4 per default due to > time constraints and get it back to default for 3.4.x once the kinks > have been worked out. Thoughts? I do like the app; I assu

[sage-devel] Re: Slowdown in is_isomorphic?

= 10 vertices) for a particular application that I have in mind. That's why I ran the particular test I ran. But it's quite possible that the C_Graph implementation works on moderately large and sparse graphs. I'll probably look into this over the weekend. Mark --~--~--

[sage-devel] help? doesn't work in sage 3.3 notebook

e error below in the Sage 3.3 notebook. I'm running Sage 3.3 (upgraded from 3.3.rc2) in Sage.app on my MacBook Pro running OSX 10.4.11. Mark McClure -- Error message Traceback (most recent call last): File "", line 1, in File "/Users/mar

[sage-devel] Re: Slowdown in is_isomorphic?

On Feb 26, 11:35 pm, Jason Grout wrote: > What is the Networkx timing?  That seems like the best. That's just straight up NetworkX run independently of Sage. Of course, the code is almost identical. Mark --~--~-~--~~~---~--~~ To post to this group, se

[sage-devel] Re: Slowdown in is_isomorphic?

On Feb 26, 9:35 pm, Robert Miller wrote: > Between Sage 3.1.1 and 3.2.3, the background implementation > of graph isomorphism was completely switched over. ... > if the input graphs are based on NetworkX graphs, it will > go much more slowly than it used to. For maximum speed in > is_isomorphic,

[sage-devel] Slowdown in is_isomorphic?

de: %time result = false for i in xrange(0,len(some_graphs)-1): for j in xrange(i+1, len(some_graphs)): if some_graphs[i].is_isomorphic(some_graphs[j]): result = true break if result: break result Ma

[sage-devel] Re: savefig from pylab in 3.3

7;t worry so much next time. Thanks, Mark --~--~-~--~~~---~--~~ 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 this group at http://groups.

[sage-devel] Re: savefig from pylab in 3.3

aps, I'll compile the latest tomorrow and see if the problem persists. Thanks, Mark McClure --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups

[sage-devel] savefig from pylab in 3.3

over to my desktop where I can view it with Preview.app. The 3.3 error message is included below, Mark McClure --- Traceback (click to the left for traceback) ... ValueError: Unknown file type Traceback (most recent call last): File "", line 1

[sage-devel] Small problem with Sage.app environment

ot happen when I run Sage.app. Is there an easy way for me to set my PATH or other environment variables from within the sage notebook? Is there a logical init file to edit in the Sage.app package to make this happen automatically? Thanks, Mark McClure --~--~-~--~~~---

[sage-devel] Re: Sage 3.3.rc2 released

After installing the new spkg, sage compiled, Sage.app built, and all but the following three tests passed: sage -t "devel/sage/sage/graphs/graph_plot.py" sage -t "devel/sage/sage/misc/package.py" sage -t "devel/sage/sage/pl

[sage-devel] Re: Sage 3.3.rc2 released

On Feb 20, 9:18 am, mabshoff wrote: > On Feb 20, 6:08 am, mark mcclure wrote: > I screwed up, please try again. The problem is that I created a tar.gz > instead of a tar.bzip2. I had a feeling it was something like this. I had a class this morning and have only just started the bui

[sage-devel] Re: Sage 3.3.rc2 released

o sense to me, since I would need to have built sage already and the point is to try to build it? I ask because this makes me wonder if I'm mis-understanding something. I'll be leaving for work shortly, but I'll take my laptop with me. Mark -- Errors resulting from curl

[sage-devel] Re: Sage 3.3.rc2 released

should have mentioned that I've never applied a spkg before; some explicit instructions would help. Mark --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...

[sage-devel] Re: Sage 3.3.rc2 released

On Feb 20, 12:35 am, mabshoff wrote: > On Feb 18, 10:41 am, mark mcclure wrote: > > > I get an error building GMP on my MacBook Pro running > > OS X 10.4.11.   > > Hi Mark, > > I haven't gotten to this yet, but I have made this > >    http://trac.sage

[sage-devel] Re: Sage 3.3.rc2 released

uot;. > > Evidently there's still a little more to building the groovy Sage.app, > > though? > > Run "./sage -bdist 3.3.rc2" and wait until it finishes. Worked great, thanks. Mark McClure --~--~-~--~~~---~--~~ To post to this group

[sage-devel] Re: Sage 3.3.rc2 released

On Feb 18, 12:33 pm, mabshoff wrote: > 3.3.rc2 has been out for a good half day, Build went smoothly on my Intel MacPro running OS X 10.5.5. Passed all tests from 'sage -t devel/sage/sage/misc/all.py'. Evidently there's still a little more to building the groovy Sage.app, tho

[sage-devel] Re: Sage 3.3.rc2 released

On Feb 18, 1:44 pm, mabshoff wrote: > Ok, I know what went wrong. I assume this is a MacIntel. Can you send > me the complete compressed log? Correct, this is an Intel based Mac. I'll gzip the log and email it to you shortly. M

[sage-devel] Re: Sage 3.3.rc2 released

d so far. Mark McClure --- Log - gcc -std=gnu99 -DHAVE_CONFIG_H -I. -g -O2 -MT yasm.o -MD -MP - MF .deps/yasm.Tpo -c -o yasm.o `test -f 'frontends/yasm/yasm.c' || echo './'`frontends/yasm/yasm.c mv -f .deps/yasm.Tpo .deps/yasm.Po gcc -std=gnu99 -D

[sage-devel] Re: Sage 3.3.rc0 binary for MacIntel OSX 10.5

ssue remains. When Sage.app quits, MacOS gives me the message: "The application lisp.run quit unexpectedly." Not a problem as far as I'm concerned, but a bit strange. Mark McClure --~--~-~--~~~---~--~~ To post to this group, send email to sage-deve

[sage-devel] Re: Sage 3.3.rc0 binary for MacIntel OSX 10.5

: set_plot_option([gnuplot_term, aqua]); set_plot_option([gnuplot_pipes_term, aqua]); Of course, now I can no longer plot from my standalone copy of maxima. :) One final comment: George's patch was unnecessary. I hope I didn't send you on a wild goose chase. Ma

[sage-devel] Re: Sage 3.3.rc0 binary for MacIntel OSX 10.5

on this machine, although I do have Macports. Thanks, Mark McClure --- Post Patch error log Traceback (click to the left for traceback) ... RuntimeError: Unable to start maxima Traceback (most recent call last): File "", line 1, in File "/Users/mcmcclure/.sage/

[sage-devel] Re: Sage 3.3.rc0 binary for MacIntel OSX 10.5

applicable to Sage.app, not to the command line. That is, I'd like to be able to type: /Applications/Sage.app/Contents/Resources/sage/sage but I don't think your script ever even runs in that case. Thanks, Mark McClure --~--~-~--~~~---~--~~ To post to thi

[sage-devel] Re: Sage 3.3.rc0 binary for MacIntel OSX 10.5

Yeah, I noticed that too. :) Thanks for the help, Mark McClure --~--~-~--~~~---~--~~ 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,

[sage-devel] Re: Sage 3.3.rc0 binary for MacIntel OSX 10.5

On Feb 13, 12:55 pm, William Stein wrote: > On Fri, Feb 13, 2009 at 9:53 AM, mark mcclure wrote: > What happens when you type: > > ./sage -maxima I get the error message shown below. I had tried that already, since I frequently use sage precisely to access maxima. -

[sage-devel] Re: Sage 3.3.rc0 binary for MacIntel OSX 10.5

the rebase script ran: Thanks for the info. Unfortunately, Maxima still doesn't work for me. I included the error messages below. Also, I built sage from source, assuming that would work. I get virtually identical error messages with only the directory names changed. > Mark: Thanks again

[sage-devel] Re: Sage 3.3.rc0 binary for MacIntel OSX 10.5

te-packages/ sage/interfaces/maxima.py", line 450, in _start File "/Users/mabshoff/sage-3.3.rc0/local/lib/python2.5/site-packages/ sage/interfaces/expect.py", line 464, in _start RuntimeError: Unable to start maxima -- Perha

[sage-devel] Re: parallel computation

code that run fine in MPI universe of 1, and 2 but blew up in other cases. > > - Python does have a number of really good Object relational mapping > projects. The best is currently SQLAlchemy (which Sage already uses). > Thanks I will look into that. Cheers Mark > Cheers, > &

[sage-devel] Re: parallel computation

On Tue, May 20, 2008 at 3:48 PM, Mark V <[EMAIL PROTECTED]> wrote: > Hi William, > Thanks for taking time to respond so promptly. > > On Tue, May 20, 2008 at 1:17 PM, William Stein <[EMAIL PROTECTED]> wrote: >> On Mon, May 19, 2008 at 6:57 PM, MarkV <[EMAIL PROTEC

[sage-devel] Re: parallel computation

so) of >> storage :) >> Currently I use an Amazon machine image as a (Gnome) desktop machine - >> I know one user considered using an 8-cpu instance to compile their >> code more rapidly and this might help some SAGE devs? > > Cool. Some of us Sage devs are at universities

[sage-devel] Re: Sage 3.0 released

On Apr 23, 6:24 pm, mark mcclure <[EMAIL PROTECTED]> wrote: > On Apr 23, 6:17 pm, mabshoff <[EMAIL PROTECTED] > > dortmund.de> wrote: > > On Apr 24, 12:14 am, mark mcclure <[EMAIL PROTECTED]> wrote: > > > The trailing kg is missing. Should I simply chan

[sage-devel] Re: Sage 3.0 released

On Apr 23, 6:17 pm, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > On Apr 24, 12:14 am, mark mcclure <[EMAIL PROTECTED]> wrote: > > The trailing kg is missing. Should I simply change the > > name and try again? > > Yes. Run make, then a "sage -b". If

[sage-devel] Re: Sage 3.0 released

ere's not. Strangely, there's a file called: singular-3-0-4-2-20080405.p1.sp The trailing kg is missing. Should I simply change the name and try again? Mark --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscr

[sage-devel] Re: Sage 3.0 released

On Apr 23, 5:54 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > Could you type >./sage -br > form the SAGE_ROOT directory and send the output? Sure: -- sage: Building and installing modified SAGE library files. Installing c_lib g++

[sage-devel] Re: Sage 3.0 released

n/ in () : No module named sage.misc.misc ### end Sage messages I've uploaded the full 9.2 MB install.log here: http://facstaff.unca.edu/mcmcclur/install.log.txt Mark --~--~-~--~~~---~--~~ To post to this group, send email to

[sage-devel] Re: Sage 3.0 released

roblem, I upgraded to OS X 10.4.11. A rebuild is in progress and the install.log has already been overwritten. Sorry about that; perhaps I'll learn for the future. :) Presumably, by 5:30 or so I'll either have a working copy or I'll be ab

[sage-devel] Re: Sage 3.0 released

On Apr 23, 3:54 pm, mhampton <[EMAIL PROTECTED]> wrote: > I'm not sure what the problem is, probably William Stein or Michael > Abshoff will be able to answer that, but maybe its simplest to just > upgrade your gcc with the latest stuff from apple. My gcc is build > 5465; I'm not sure how they

[sage-devel] Re: Sage 3.0 released

On Apr 23, 1:08 pm, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > >> Are their binaries for OS X 10.4? > > NO. And there won't be until somebody volunteers to make them. > > Can you make them? > > Yes, do I just build and do sage -bdist? I attempted to compile sage 3.0 on my Mac G5 running OS

  1   2   >