Re: [sage-support] cypari fails to build on Ubuntu 18.04

On 2019-06-18 15:16, Kevin Horton wrote: 2. It is quite possible low memory is the issue, as I'm trying to install it on a Linode virtual server with 1 GB RAM. Yes, that's probably not enough for a big compilation. I would recommend at least 4GB of RAM, but you may get away with 2GB... at

Re: [sage-support] cypari fails to build on Ubuntu 18.04

Internal compiler error typically means one of the following: - Running out of memory during compilation - Buggy compiler - Hardware problem So the following questions need to be answered: 1. Is the problem reproducible? What happens when you try again? 2. Is this a machine with little memory

Re: [sage-support] Re: Computing a Groebner Basis (singular algorithm) raises an error

On 2019-05-27 16:11, Tracy Hall wrote: in particular it seems to have undefined behavior in subsequent calls after it has been interrupted by alarm(). This is simply a fact of life and not really considered to be a bug. You should not rely on the fact that interruptions (using either CTRL-C

Re: [sage-support] I absolutely dont know why but i am getting an error.

On 2019-04-17 09:32, Oliver Thiel wrote: Hello, I absolutely dont know why but i am getting an error. What did you do? What happened *exactly*? See also https://www.chiark.greenend.org.uk/~sgtatham/bugs.html -- You received this message because you are subscribed to the Google Groups

Re: [sage-support] Interface to 4ti2

On 2019-03-20 05:21, 'benyamin alizade' via sage-support wrote: When I run |sage -i 4ti2, it returns that -i is an unknown option for sage. What happens *exactly*? -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this

Re: [sage-support] A case of immaculate conception...

On 2019-03-19 12:52, Emmanuel Charpentier wrote: Defining a symbolic function seems to declare its arguments. I tend to think that everything on the left of the '=' sign in an assignment is stuff that is assigned to. So (a, b, c) = range(3) assigns to a, b and c. R. = ZZ[] assigns to

Re: [sage-support] much memory is used...

On 2018-10-09 12:00, Dima Pasechnik wrote: Well, primitive, as opposed to added by Sage. E.g. I suppose one cannot use it for RDF. If you really want to get elements of RDF, you could use a Sage vector instead. -- You received this message because you are subscribed to the Google Groups

Re: [sage-support] much memory is used...

On 2018-10-08 14:28, Dima Pasechnik wrote: Can you use array.array on anything that's not a primitive Python type? I don't know what you mean with "primitive Python type". Anyway, it supports various kinds of basic C types (like double for example). Docs here:

Re: [sage-support] much memory is used...

On 2018-10-08 13:19, Thierry Dumont wrote: So my list should use less than 1gb, if it phi was a C array. But it's not a C array. There is overhead for Python garbage collection, the Sage parent, the Cython virtual method table... If you really want a C array, use array.array or numpy. --

Re: [sage-support] Sage crashes on start

On 2018-07-18 05:58, 'Naturelover' via sage-support wrote: I just installed SageMath 7.6 Why such an old version? -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email

Re: [sage-support] Re: building documentation: says I should use a sage shell, but i am

On 2018-06-18 04:22, Matthew Lancellotti wrote: I am able to get around the first error by commenting out the try catch loop in conf.py: Which conf.py file are you talking about? -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe

Re: [sage-support] Re: building documentation: says I should use a sage shell, but i am

On 2018-06-18 05:54, Matthew Lancellotti wrote: sage-7.6-Ubuntu_14.04-x86_64.tar.bz2 Do you have a good reason to use an outdated version of Sage? Version 8.2 has been released. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To

Re: [sage-support] PARI/GP error in wrapping custom-defined PARI functions in Sage using the command gp.set()

On 2018-06-18 09:50, am...@ma.iitr.ac.in wrote: I have a library in PARI/GP and since Sage also supports the GP calculator I have been trying to shift my library using gp.set() and gp.get() commands. So far all functions are working but I got a PARI/GP error while implementing this function in

Re: [sage-support] Re: PariError: bug in LLL_cmbf [no factor], please report

Thanks for checking. In the mean time, I guess the problem might be related to the fact that I'm using a non-default value for primelimit in GP (100 instead of 50). But if you say that the problem is fixed by the PARI upgrade, I consider this issue closed. -- You received this

Re: [sage-support] Re: PariError: bug in LLL_cmbf [no factor], please report

On 2018-06-13 10:25, John Cremona wrote: THanks for looking into this Jeroen (I hoped you would). The file bug.gp you attached causes an error in the latest gp (version 2.10.0), after increasing parisizemax I get the same error message. What are the *exact steps* for

Re: [sage-support] Re: PariError: bug in LLL_cmbf [no factor], please report

I haven't managed to reproduce it in GP, I have no idea why. Typically, it's not so hard to translate a Sage bug like this to a PARI/GP bug. It must be something rather subtle. I'll try again tomorrow. I did manage to reproduce it with the PARI-in-Sage by running the attached GP script in

Re: [sage-support] Upgrade to 8.2 hangs at ncurses

On 2018-05-10 19:38, Robert Gross wrote: I have aliased cp to "cp -i" and "mv" to "mv -i". What do you mean this *exactly*? -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it,

Re: [sage-support] Cython in jupyter notebook

On 2018-04-15 16:08, Simon King wrote: Hi! The following cython code compiles fine in SageMath command line version and it *used* to compile fine in the jupyter notebook one year ago: Fix at https://trac.sagemath.org/ticket/25177 -- You received this message because you are subscribed to the

Re: [sage-support] ipywidgets and sage

On 2018-03-21 11:49, Marcin Kostur wrote: btw, will it be sufficient when major version number will match? Probably, but I cannot say for sure. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving

Re: [sage-support] ipywidgets and sage

On 2018-03-21 10:05, Marcin Kostur wrote: Hi, How to get working ipywidgets *or @interact" when using sagemath kernel in external jupyter/jupyterlab? The problem is the version of ipywidgets in Sage must match with the version in the external jupyter. If you are using Sage 8.1, this is

Re: [sage-support] Issue compiling Cython code that uses Sage

On 2018-03-15 13:22, Marc Mezzarobba wrote: but the variant below doesn't? That's certainly a bug: https://trac.sagemath.org/ticket/24987 -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving

Re: [sage-support] Has Big-Endian support been deprecated yet?

On 2018-03-13 20:33, Kim Walisch wrote: primecount currently only supports little-endian CPUs. That sounds very fishy to me. What are you doing in your code that it supports only little-endian? If your code only works for a particular endianness, it probably means that you are nasty stuff

Re: [sage-support] Sage Crash Report

On 2018-03-10 12:29, Alasdair McAndrew wrote: As created just now. Enjoy! How did you get that SageMath installation on your computer? Was it a binary install, a source install, an upgrade from an earlier version? In any case, I would suggest to simply reinstall Sage. -- You received this

Re: [sage-support] avoiding startup time cost with multiple invocations

On 2018-01-10 19:27, Vincent Delecroix wrote: Have a look at https://docs.python.org/2/extending/embedding.html Even simpler would be to use Cython to interface between C++ and Python/Sage. -- You received this message because you are subscribed to the Google Groups "sage-support"

Re: [sage-support] LattE failed to build

There seems to be a problem with your networking setup. Does this help: https://superuser.com/questions/879731/osx-ssh-could-not-resolve-hostname-nodename-nor-servname-provided-or-not-kno -- You received this message because you are subscribed to the Google Groups "sage-support" group. To

Re: [sage-support] LattE failed to build

Logs please -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to

Re: [sage-support] Re: Map from S.base() to S?

Thanks! On 2017-11-27 10:14, Simon King wrote: Hi Jeroen, On 2017-11-27, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: I might be missing something, but is there a generic recipe in Sage to get a map from S.base() to S? I want something which works in as much generality as possible f

[sage-support] Map from S.base() to S?

I might be missing something, but is there a generic recipe in Sage to get a map from S.base() to S? I want something which works in as much generality as possible for any structure S. I feel like that should exist but I couldn't find it. -- You received this message because you are

Re: [sage-support] Sage Crash Report

On 2017-10-26 10:50, Dima Pasechnik wrote: from your log: ImportError: libgfortran.so.3: cannot open shared object file: No such file or directory installing libfortran3 will fix the problem. Or waiting for Sage 8.1 since that problem has been fixed in the mean time. -- You received this

Re: [sage-support] Sage Crash Report

This is a known problem which will be fixed for Sage 8.1 For now, you have to install gfortran from your Fedora distribution. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it,

Re: [sage-support] Sage Crash Support

On 2017-10-22 21:14, Alvaro Ezequiel wrote: I installed Sage correctly. When I'm going to execute it this happens and crash... What happens? -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving

Re: [sage-support] Sage Crash Report

On 2017-10-22 21:01, Jan Groenewald wrote: If you can email this file to the developers ...provided with information on how you installed Sage, what OS you are using, which version of Sage you are running, what command you ran when you got this error. Too many people think that a "Crash

Re: [sage-support] Sage crash on first run - can't find the fortran compiler

This should be fixed in the next version of Sage: https://github.com/sagemath/binary-pkg/pull/12 -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [sage-support] Troubleshooting standalone scripting issues (seeking knowledge about interpreter and preparser)

Confirmed, this is a bug in the tutorial. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send

Re: [sage-support] Sage 8.0.beta12 Crash Report

This is a customized version of Sage. For example, the file src/sage/dynamics/complex_dynamics/mandel_julia.py (which is causing the problems) does not exist in the official SageMath. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To

Re: [sage-support] Trouble building development version

On 2017-06-15 17:48, David Loeffler wrote: I just downloaded the sage-8.0.beta10 tarball, unpacked it, and typed 'make'. After a short interval, I got the error message below. What am I doing wrong? Do you have any unusual environment variables set? -- You received this message because you

Re: [sage-support] How to use Sphinx to create documentation for a project that uses Sage?

On 2017-05-31 12:42, Paul Leopardi wrote: On Wednesday, 31 May 2017 19:39:32 UTC+10, Jeroen Demeyer wrote: I think you need to import sage.all first, before importing anything else from sage. Thanks, in which file do you mean, every Python file that uses Sage, or some specific file

Re: [sage-support] How to use Sphinx to create documentation for a project that uses Sage?

On 2017-05-31 12:55, Paul Leopardi wrote: Thanks, I think I figured out what you mean. I updated conf.py to contain the following: That's not what I meant since I said that the issues you are having are unrelated to Sphinx. So by "fixing" it in Sphinx you are working around the problem, not

Re: [sage-support] How to use Sphinx to create documentation for a project that uses Sage?

I think you need to import sage.all first, before importing anything else from sage. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [sage-support] How to use Sphinx to create documentation for a project that uses Sage?

On 2017-05-30 15:24, Paul Leopardi wrote: Do you understand the problem yet, or do I need to explain it again in greater detail? I understand the problem, but you are focusing too much on the detail of Sphinx. The problem is unrelated to Sphinx; it has to do with your Sage/Python

Re: [sage-support] How to use Sphinx to create documentation for a project that uses Sage?

On 2017-05-28 14:33, Paul Leopardi wrote: Hello, I am trying to create HTML documentation for my Boolean-Cayley-graphs project ( https://github.com/penguian/Boolean-Cayley-graphs ) that uses Sage. If I try to just use Sphinx, following the instructions at

Re: [sage-support] Problem compiling Sage 7.6 from source

Is the problem reproducible, i.e. does it happen again if you rebuild Sage? Which compiler are you using? -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [sage-support] complex numbers printing real part + imaginary part

On 2017-04-11 18:25, Pedro Cruz wrote: Hello, sage is printing b*I + a and we want to see a + b * I Do you have a complete example? -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails

Re: [sage-support] sage-7.6 build fails on Fedora-21

On 2017-03-28 06:34, Jose Gaetan Pierre wrote: sage-7.6 fails on fedora-21 (7.4 built ok). error occurred during dochtml build of graphs. Complete log file please. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this

Re: [sage-support] Sage Crash Report

On 2017-03-19 14:08, Kam wrote: Attached is a report about a crash that happened here in Chicago... enjoy the read! :) Don't press CTRL-C when Sage is starting up and all should be fine. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To

Re: [sage-support] Doubt related to commits in trac

On 2017-03-10 09:39, Ashutosh Ahelleya wrote: Heyy, Thanks and yes I am using git trac. Maybe you forgot to run $ git trac checkout 22312 when changing tickets. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this

Re: [sage-support] Running sage scripts noninteractively (possible bug)

On 2017-03-07 10:19, Jeroen Demeyer wrote: On 2017-03-06 23:58, Watson Ladd wrote: Or should I just change to load instead of attach? The problem is limited to load(), so that would work. Sorry: I meant to say: the problem is limited to attach(), so load() should work. -- You received

Re: [sage-support] Running sage scripts noninteractively (possible bug)

On 2017-03-06 23:58, Watson Ladd wrote: Or should I just change to load instead of attach? The problem is limited to load(), so that would work. Thinking about it, actually attach() only makes sense in interactive sessions. So I see no reason to use it in scripts. -- You received this

Re: [sage-support] Running sage scripts noninteractively (possible bug)

Confirmed: https://trac.sagemath.org/ticket/22527 -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this

Re: [sage-support] Running sage scripts noninteractively (possible bug)

We need more details. In particular it would be useful to attach a minimal testcase with the problematic .sage files. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an

Re: [sage-support] Silly Cython question

On 2017-02-21 22:02, Watson Ladd wrote: I am having trouble figuring out which imports I need to get the right names to appear Use the import_statements() function to determine which import statements you need. There shouldn't be a difference between Python and Cython regarding import

[sage-support] Example GAP computation

Can somebody please provide some example "hello-world" GAP computation? Just something which can be used to showcase the abilities of GAP but which takes at most a few seconds to run. I need this to make a "Demo" GAP notebook for OpenDreamKit. -- You received this message because you are

Re: [sage-support] Compilation of 7.6.beta1 on Ubuntu 16-10

On 2017-01-31 12:24, Thierry Dumont wrote: I just git clone sage, then checkout origin/develop and make. Then after some time, Python 3 is installed and compiled. Are you really sure about that? Did you set the SAGE_PYTHON3 environment variable? Could you please send your logs/install.log

Re: [sage-support] Compilation of 7.6.beta1 on Ubuntu 16-10

On 2017-01-31 09:42, Thierry Dumont wrote: When trying to compile 7.6.beta1, which installed Python3, I got a cython problem (cmp...): That's not news... Nobody ever said that Sage works with Python 3. -- You received this message because you are subscribed to the Google Groups

Re: [sage-support] Cython problem

On 2017-01-25 17:07, jordan.h.e...@gmail.com wrote: Hello, I've been trying to use cython in Jupyter and it fails to compile. My version of Sage is 7.3. It was installe from the ppa. I run Linux Mint. I guess that you are missing a compiler toolchain. In your case, the system header files

Re: [sage-support] Sage needing write access to itself

Also: please describe *exactly* what goes wrong ("this doesn't work" is not precise enough to understand the problem). -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an

Re: [sage-support] Sage needing write access to itself

Exactly how did you build/install Sage? -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send

Re: [sage-support] "Precision too low for generators, not given"

On 2017-01-05 13:17, Erick Knight wrote: Thanks for both of your replies. Just to double check so that I don't have any misunderstanding, PARI is correctly determining whether my ideal is principal, and if it is, it is attempting to produce a generator. It may fail at that, but, since I never

Re: [sage-support] "Precision too low for generators, not given"

Sorry, I was wrong. I actually looked at the PARI source code this time and the warning comes from the bnfisprincipal() function to determine the class of a given ideal in the class group (so, in particular, it can be used to check whether an ideal is principal). This function can also compute

Re: [sage-support] "Precision too low for generators, not given"

I think it means that PARI didn't compute the unit group for certain number fields. Since you don't need the unit group, I see no issue. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails

Re: [sage-support] Re: Something like Mathematica's `Interact`?

On 2016-12-07 04:45, William Stein wrote: You can also track progress on porting interact to Jupyter at [3], though it looks like nobody has touched that in several months. For the record, the main obstacle here is the release of ipywidgets 6 (currently in beta!). I don't want to rely on git

Re: [sage-support] Re: How to limit heavy computations

On 2016-11-27 14:10, Jori Mäntysalo wrote: In general it is not easy to limit resource usage in Linux. It's not easy, that's true. But that's independent of the fact that ulimit within SageNB simply doesn't work due to some SageNB bug. I have known about this bug for years but never bothered

Re: [sage-support] Sage Crash Report

Details please... How did you install Sage? -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group,

Re: [sage-support] Re: Unable to launch SageMath 7.4 on macOS Sierra (10.12.1)

On 2016-11-08 23:01, quark67000 wrote: It seems that on 7.4, SageMath has a bad signals.sofile on the Mac version. No, this problem almost certainly has nothing to do with signals.so As Volker said, it is https://trac.sagemath.org/ticket/21772 -- You received this message because you are

Re: [sage-support] How could I import igraph or python-igraph in the python bundled with sage?

On 2016-11-07 13:52, Eden Harder wrote: I installed sagemath with hombrew on MacOS. And later I use `sage -i python_igraph` to install python_igraph. After that, I found that 1. I cannot import python_igraph in sage The correct command is: import igraph -- You received this message because

Re: [sage-support] Re: @interact command not working in Sage 7.3 & 7.4

On 2016-10-27 00:02, kcrisman wrote: That said, there are still some incompatibilities in interact syntax, the last I heard (Jason Grout said the jupyter people were working actively no that, though). In interact *syntax* or interact *functionality*? Of course, the interact functionality is

Re: [sage-support] QQbar coercion question

On 2016-10-24 17:54, Nils Bruin wrote: Pow is not *that* special. It is more special than you think. Currently, powering does not go through the coercion framework at all. So actions won't get looked up... Of course, this could be changed. However, the *default* implementation of all

Re: [sage-support] @interact command not working in Sage 7.3 & 7.4

On 2016-10-23 19:03, ahauskne...@umassd.edu wrote: Hi the @interact command no longer seems to be working in Sage 7.3 and Sage 7.4 on an Mac Book Pro running El Capitan: Works for me on Sage 7.5.beta0. In fact I did some @interact developed recently and I never had a problem like that.

Re: [sage-support] QQbar coercion question

On 2016-10-23 10:33, Vincent Delecroix wrote: In general, pow(a, b) should only depend on parent(a) and parent(b) and not the actual values of a and b. This is how behave all arithmetic operations. +1 I don't see it as a problem that 2^QQbar(1) fails. -- You received this message because you

Re: [sage-support] How to return an RDF (or CDF) value from a Cython function ?

On 2016-10-17 15:10, Emmanuel Charpentier wrote: Thank you Vincent. this is much clearer. It seems that I have some things left to understand about the Sage class and types hierarchies. There is a difference between a type and a parent. A parent is a mathematical object. It is the

Re: [sage-support] How to catch exceptional values (+ in plot3d, one exceptional point ruins the whole plot).

On 2016-10-11 22:07, William Stein wrote: try: return abs(gamma(x+I*y)) except: return 0 That is almost never what you want, since this will also catch things like KeyboardInterrupt. Better use try: ... except Exception: ... -- You received this message because you are

Re: [sage-support] Re: Element vs UniqueRepresentation

On 2016-10-10 17:31, Simon King wrote: I just tested that in the current Sage development version my proof-of-concept would still work. But still Python 2, right? And looking at _PyType_CalculateMetaclass, I don't see why it wouldn't work in Python3. Maybe I'm misunderstanding you, but

Re: [sage-support] Element vs UniqueRepresentation

Try this: sage: from sage.misc.inherit_comparison import InheritComparisonClasscallMetaclass sage: class A(Element, UniqueRepresentation): : __metaclass__ = InheritComparisonClasscallMetaclass -- You received this message because you are subscribed to the Google Groups "sage-support"

Re: [sage-support] huge virtual memory size when launching 7.3

On 2016-09-21 16:19, Jonathan Bober wrote: I moved discussion to sage-devel, but wanted to add for anyone who comes across this and has problems: my simple temporary workaround is to change the line paristack_setsize(size, mem.virtual_memory_limit() // 4) to paristack_setsize(size,

Re: [sage-support] FYI : ipywidgets allows (sort of) interactive Sage graphs in Jupyter notebook.

On 2016-09-20 22:09, Emmanuel Charpentier wrote: May I ask why ? (Just curious, no hostility whatsoever implied...). Because those packages are installed and the nbextension is enabled in Sage by default: https://trac.sagemath.org/ticket/21256 -- You received this message because you are

Re: [sage-support] FYI : ipywidgets allows (sort of) interactive Sage graphs in Jupyter notebook.

On 2016-09-20 16:12, Emmanuel Charpentier wrote: sage -pip install ipywidgets echo "jupyter nbextension enable --py --sys-prefix widgetsnbextension" | sage -sh In recent Sage betas, the above should not be needed. -- You received this message because you are subscribed to the Google Groups

Re: [sage-support] huge virtual memory size when launching 7.3

On 2016-09-20 12:54, Jonathan Bober wrote: From reading what you've sent, I guess that what you have in mind is calling mmap with PROT_NONE and then calling mprotect() to change that to read/write whenever growing the stack? That seems like it might be a reasonable thing to do (though I'm only

Re: [sage-support] huge virtual memory size when launching 7.3

After spending some time reading on the subject, I think I might have a solution to this "problem". It involves calling mmap() with PROT_NONE, which will require a patch to upstream PARI. However, before implementing this, I would like a *strong commitment* from somebody to review my patch

Re: [sage-support] Re: huge virtual memory size when launching 7.3

On 2016-09-19 19:58, Jeroen Demeyer wrote: * https://lwn.net/Articles/627557/ This last page indicates that one should use PROT_NONE to work around the issue you are having. Note this nice quote: > Sadly, the commit charge implications of MAP_NORESERVE are documented but silently bro

Re: [sage-support] Re: huge virtual memory size when launching 7.3

On 2016-09-19 14:04, Jonathan Bober wrote: With overcommit_memory set to 2, I'm not sure that there is a right thing to do. If I'm the only person in the world with this problem, then I should keep my mouth shut and get with the times, but I don't think this setup is so unreasonable. Some

Re: [sage-support] Re: huge virtual memory size when launching 7.3

On 2016-09-19 19:01, William Stein wrote: We should revert whatever trac ticket did this The first version of this is from https://trac.sagemath.org/ticket/19883 or at least make it an option to not allocate such a large address space. That's easy to do. How would you see the user

Re: [sage-support] Re: huge virtual memory size when launching 7.3

On 2016-09-19 14:04, Jonathan Bober wrote: That doesn't really solve the problem, which I phrased poorly. The machine has an (antiquated) setup where, when a process requests X bytes of memory, the kernel reserves X bytes of physical memory for it. Well, in that case you would indeed "lose"

Re: [sage-support] Re: huge virtual memory size when launching 7.3

On 2016-09-19 13:02, Jonathan Bober wrote: If I ulimit -v 8 GB, say, (which is 512/64), and the PARI allocater immediately grabs 2 GB of the virtual address space for itself, then that seems like it leaves only 6 GB for malloc/sage_malloc/whatever else, which would be effectively limiting the

Re: [sage-support] Re: huge virtual memory size when launching 7.3

On 2016-09-19 11:54, Jonathan Bober wrote: But in that case the memory does effectively get "used", if it is the case that a quarter of the machine's memory is only available from the PARI memory allocater. If I'm not using the PARI parts of Sage, is that memory completely wasted? There should

Re: [sage-support] Re: huge virtual memory size when launching 7.3

Why don't you use ulimit -v to limit the per-process available memory? That would make sense when starting lots of processes even without the PARI non-issue. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and

Re: [sage-support] Interface to lie broken in sage 7.3?

The *real* underlying problem is of course that LiE doesn't come with a build/install system, which makes such strange steps necessary. This is also the (only?) reason why this is an experimental (instead of optional) package. -- You received this message because you are subscribed to the

Re: [sage-support] Re: huge virtual memory size when launching 7.3

On 2016-08-31 08:57, Thierry Dumont wrote: On machine 2, sage stating process (as mesured with top) uses about 39GB (no more...) out of 153.79 available. It doesn't actually "use" that memory. It is reserved virtual memory but it does not take up physical memory or swap space. -- You

Re: [sage-support] Re: huge virtual memory size when launching 7.3

On 2016-08-30 20:26, leif wrote: this makes the usage of 'ulimit -v' nearly impossible I don't see why. You can still use 'ulimit -v'. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails

Re: [sage-support] Dividing a matrix by integer one returns a matrix over rational field

There is a general philosophy in Sage that the *parent* of the output of an operation should only depend on the *parent* of the inputs. So, because 5/2 is a Rational, also 5/1 should be a Rational. -- You received this message because you are subscribed to the Google Groups "sage-support"

Re: [sage-support] Re: Building Sage 7.2 from source: Error installing package gcc-4.9.3.p1

On 2016-05-28 04:41, paulmasson wrote: Yes, I did git clone of sage.git on github. Do you think I should just delete it all and start again fresh? Is that the usual way to address such seemingly random errors? No idea. There is clearly something wrong with your setup but I cannot tell

Re: [sage-support] Re: Building Sage 7.2 from source: Error installing package gcc-4.9.3.p1

On 2016-05-27 04:30, paulmasson wrote: File is indeed not in the indicated directory. It should be there. Please try "make sagelib-clean" and then run "make" again and see if the problem remains... -- You received this message because you are subscribed to the Google Groups "sage-support"

Re: [sage-support] Re: How to get all solutions of a MILP?

On 2016-05-18 13:44, Dima Pasechnik wrote: Do you mean that you want a cleaner interface for p.polyhedron() in the case when p has more than 1 variable? Yes. Example: sage: P = MixedIntegerLinearProgram(solver="PPL") sage: x = P.new_variable(nonnegative=True) sage: y =

Re: [sage-support] Re: How to get all solutions of a MILP?

On 2016-04-19 15:00, Dima Pasechnik wrote: here is an example: sage: P=3*polytopes.cube() sage: (p,x)=P.to_linear_program(solver='ppl',return_variable=True) sage: p.set_objective(x[0]) # maximizing x[0] over 3 times inflated unit cube sage: p.solve() 3 sage: p.add_constraint(x[0]==3) # restrict

Re: [sage-support] Re: Issue build sagemath 7.2 from source.

Please send the complete log /home/pietrol/Sage/sage-7.2/logs/pkgs/gcc-4.9.3.p1.log together with /home/pietrol/Sage/sage-7.2/local/var/tmp/sage/build/gcc-4.9.3.p1/build/config.log or any other config.log located inside /home/pietrol/Sage/sage-7.2/local/var/tmp/sage/build/gcc-4.9.3.p1 --

Re: [sage-support] Issue build sagemath 7.2 from source.

On 2016-05-17 13:33, Pietro Liguori wrote: Hi all, I try to build sagemath 7.2 from source. My computer is Red Hat Enterprise Linux Server release 5.11 (Tikanga) x86_64. I suggest you run "make distclean" and "make" again. If that also fails, send the logfile of the package which failed. --

[sage-support] How to get all solutions of a MILP?

Hello, I have a MixedIntegerLinearProgram where all variables are integers. I want to minimize one of the variables, but I need *all* solutions, i.e. all assignments to the variables which minimize the goal function (I know that this list is finite). Is there a simple way to do this?

Re: [sage-support] Need handholding about Sage Git good practices.

On 2016-04-01 21:31, Emmanuel Charpentier wrote: Fine, but now, my patch contains about 890 (IIRC) commits already in 7.2beta2. What's your definition of "contains" here? Your branch (I guess that's what you meant with "patch") "contains" all commits made in the past in Sage. I don't see

Re: [sage-support] Re: Re: Multivariate division with remainder of polynomials

On 2016-03-31 11:06, Marc Mezzarobba wrote: Jeroen Demeyer wrote: Is there any reason that quo_rem is not consistent with .mod()? That is no longer arbitrary and would also extend the Euclidean division of univariate polynomials. Not quite: you'd have to return a tuple of quotients. I don't

Re: [sage-support] Re: Multivariate division with remainder of polynomials

On 2016-03-30 16:08, Marc Mezzarobba wrote: I think it is just a more or less arbitrary function that satisfies quo*q + rem == p and extends the Euclidean division of univariate polynomials. (But // can still be useful for exact divisions or divisions by monomials...) Is there any reason that

Re: [sage-support] Moore–Penrose pseudoinverse?

This is now implemented and ready for review at http://trac.sagemath.org/ticket/20287 -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to

  1   2   3   4   >