Re: [sage-devel] Re: Memory leak? Creation of DiGraph slows down.
So it seems to come from the have_dot2tex() function, in that it tests the installation of dot2tex by executing a dot2tex command. I think the easiest and best solution would be to make have_dot2tex() into a @cached_function. Best, Travis On Saturday, May 30, 2015 at 8:23:57 AM UTC-7, Jori Mäntysalo wrote: On Sat, 30 May 2015, Nathann Cohen wrote: OK, so it's dot2tex (I guess). Somebody wants to test with it installed? Having doc2tex turns a 100ms function into a 30s functions ? O_o I tested this on 6.8beta1 on quite old and slow computer with 32-bit kernel. In this machine the result after dot2tex was An exception has occurred, use %tb to see the full traceback. SystemExit: 1 I guess this relates to same bug somewhere. It worked fast without dot2tex installed. -- Jori Mäntysalo -- 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@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: MathJax limit for TeX expression in notebook
+1 to this. What is the best course of action? Opening a ticket? Can you figure out where to change this in Sage first? Then opening a ticket seems reasonable. -- 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@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Memory leak? Creation of DiGraph slows down.
I did P6=Posets(6).list() and then for 4 time I ran the code you give, and instead of 33s I get 94ms :-P sage: P6=Posets(6).list() sage: %timeit for P in P6:g=P.hasse_diagram() 10 loops, best of 3: 94.2 ms per loop sage: %timeit for P in P6:g=P.hasse_diagram() 10 loops, best of 3: 97.2 ms per loop sage: %timeit for P in P6:g=P.hasse_diagram() 10 loops, best of 3: 94.6 ms per loop sage: %timeit for P in P6:g=P.hasse_diagram() 10 loops, best of 3: 94.2 ms per loop My guess is that you did not run what you claim :-P Nathann -- 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@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] patchbot vs sagedev.py doctest
Hi,
i am trying to run some patchbots within a VM, i am using a ptestlong-ed
version of Sage 6.7, but when the patchbot runs tests, i got an error
during the test of sagedev.py (while i have no error with make ptestlong):
sage -t --long --warn-long 75.9 src/sage/dev/sagedev.py
**
File src/sage/dev/sagedev.py, line 897, in
sage.dev.sagedev.SageDev.checkout_branch
Failed example:
dev.git.echo.stash('apply')
Exception raised:
Traceback (most recent call last):
File
/opt/sagemath_tmonteil-debian-unstable-64/sage-6.7/local/lib/python2.7/site-packages/sage/doctest/forker.py,
line 496, in
_run
self.compile_and_execute(example, compiler, test.globs)
File
/opt/sagemath_tmonteil-debian-unstable-64/sage-6.7/local/lib/python2.7/site-packages/sage/doctest/forker.py,
line 858, in
compile_and_execute
exec(compiled, globs)
File doctest sage.dev.sagedev.SageDev.checkout_branch[18], line 1,
in module
dev.git.echo.stash('apply')
File
/opt/sagemath_tmonteil-debian-unstable-64/sage-6.7/local/lib/python2.7/site-packages/sage/dev/git_interface.py,
line 1199
, in meth
return self(git_cmd, *args, **kwds)
File
/opt/sagemath_tmonteil-debian-unstable-64/sage-6.7/local/lib/python2.7/site-packages/sage/dev/git_interface.py,
line 227,
in _execute
raise GitError(exit_code, cmd, stdout, stderr)
GitError: git returned with non-zero exit code (1) for git -c
user.email=d...@test.test -c user.name=doctest stash apply.
output to stderr: refs/stash@{0} is not a valid reference
**
File src/sage/dev/sagedev.py, line 915, in
sage.dev.sagedev.SageDev.checkout_branch
Failed example:
dev.checkout(branch=branch1)
Expected:
The following files in your working directory contain uncommitted changes:
BLANKLINE
tracked
BLANKLINE
Discard changes? [discard/Cancel/stash] discard
On local branch branch1 without associated ticket.
BLANKLINE
# Use sage --dev merge to include another ticket/branch.
# Use sage --dev commit to save changes into a new commit.
Got:
On local branch branch1 without associated ticket.
BLANKLINE
# Use sage --dev merge to include another ticket/branch.
# Use sage --dev commit to save changes into a new commit.
**
If, on the same machine, if test the same file by hand, i have no problem:
./sage -t --long src/sage/dev/sagedev.py
Running doctests with ID 2015-05-20-21-47-49-c8392758.
Git branch: patchbot/ticket_merged
Doctesting 1 file.
sage -t --long --warn-long 76.3 src/sage/dev/sagedev.py
[868 tests, 39.35 s]
--
All tests passed!
--
Total time for all tests: 39.5 seconds
cpu time: 7.7 seconds
cumulative wall time: 39.3 seconds
The same problem appears on Debian/Ubuntu, 32/64 bits, various releases,
see http://patchbot.sagemath.org/ticket/0/
Any idea of what could be wrong here ?
Ciao,
Thierry
--
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@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Arb as a standard package?
Vincent Delecroix wrote: As I already mentioned on tickets, the semantic of equality is a bit different for intervals and balls. This is annoying since they basically represent the same objects (=intervals with diadic bounds). This is my only objection for having it standard right now. If I understand correctly, you disagree with some of the choices made in the high-level sage bindings for arb, that is, ball fields and their elements. But I'd say this is largely independent of whether arb is a dependency of sage or not. Isn't it? Regarding the technical issue, I am not convinced that intervals and balls should be interchangeable. Sure, they represent similar objects, but it seems to me that their typical use cases are different: basically, intervals represented by their endpoints are more convenient to do bisection, bound the range of a function on a “large” box, or similar things, while balls are better if you want to do arithmetic on real numbers and keep track of roundoff errors (though of course both balls and intervals *can* be used in both cases). To put it another way, I think of (real) intervals as ranges of real numbers, and of balls as specific reals known imprecisely. This makes a difference for instance in code like interval = ... f = x - y f(x=interval, y=interval) If you think of 'interval' as a range, say [0,1], you expect an interval enclosing the range of 'f' over [0,1]². While if you think of it as a single number, say pi ± 1e-10, it is acceptable (and better) to return 0. In the first case, 'interval == interval' should return False unless 'interval' is a point interval; in the second, you can have it return True when 'interval is interval' (but of course 'interval == copy(interval)' should still be False). And so on. The differences between the underlying libraries (arb and mpfi) in this respect are the main reason for the slightly different semantics of equality between Sage real balls and real intervals (as discussed in more detail on the same tickets you mention). I personally find it is useful to have separate parents supporting the “intervals-as-ranges” model and the “intervals-as-points” model. That being say, I too was skeptical about the semantics of ball equality at first, and I wouldn't be opposed to making RBF closer to RIF in this respect. -- Marc -- 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@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Memory leak? Creation of DiGraph slows down.
On Fri, 29 May 2015, Nathann Cohen wrote: I did P6=Posets(6).list() and then for 4 time I ran the code you give, and instead of 33s I get 94ms :-P sage: P6=Posets(6).list() sage: %timeit for P in P6:g=P.hasse_diagram() 10 loops, best of 3: 94.2 ms per loop OK, so it's dot2tex (I guess). Somebody wants to test with it installed? -- Jori Mäntysalo
Re: [sage-devel] Re: Memory leak? Creation of DiGraph slows down.
OK, so it's dot2tex (I guess). Somebody wants to test with it installed? Having doc2tex turns a 100ms function into a 30s functions ? O_o Nathann -- 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@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Bug in pickling of callable symbolic functions
On Sunday, May 3, 2015 at 3:45:26 PM UTC+2, Eric Gourgoulhon wrote: G(a, y)multiple polylogarithm G(a, s, y)multiple polylogarithm with explicit signs for the imaginary parts S(n, p, x)Nielsen’s generalized polylogarithm H(m, x)harmonic polylogarithm Thanks for your answer and the link! This is clearly the source of the problem. The code for these functions was commented out in Pynac (and incorrectly so), and so they were dysfunctional for quite some time already, only existing in the registry. I just removed them. The only thing that could happen are pickles from the time they were still accessible from Sage (which I doubt they were). The changes will appear in pynac-0.4.1. Regards, -- 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@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Arb as a standard package?
On Friday, 29 May 2015 17:23:29 UTC+1, vdelecroix wrote: On 29/05/15 17:46, Marc Mezzarobba wrote: Fredrik Johansson's Arb library hasn't been an optional package for a full year yet, but Volker already suggested fast-tracking it to standard a while ago[1], and the (few) replies to his message were positive. Doing it now would make the development of the sage bindings a bit easier. Does anyone object to this change? As I already mentioned on tickets, the semantic of equality is a bit different for intervals and balls. This is annoying since they basically represent the same objects (=intervals with diadic bounds). This is my only objection for having it standard right now. Otherwise, I would be very happy to have it available for many applications in other parts of Sage! well, it's not the only bit of Sage with semantics a bit different from some other bit... I don't think this should preclude arb from becoming a standard package. Vincent -- 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@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: dpkg: error processing package sagemath-upstream-binary (--configure):
Hi Unfortunately 6.7ppa8revert6.6 has the same problem :( You should be able to do sudo apt-get install sagemath-upstream-binary=6.6ppa1 sudo apt-mark hold sagemath-upstream-binary to have a working system while the PPA is broken. Once it is fixed, I will let you know, you can, sudo apt-mark hold sagemath-upstream-binary I'll be looking for apt/dpkg/ppa help from colleagues over the next week to try and get a fixed version, any version, in the PPA, to prevent breaking further people's installations. To prevent this in future, we'll probably start a separate development PPA. Apologies for the inconvenience. There will be maybe only one more test this weekend; 6.7ppa9revert6.6 where I try a dpkg quilt format rather than native. Volker, I would very much like to get the buildslave binaries from snapperkob to test. Will they be uploaded to the sagemath download mirror (even though Thierry's binaries are there already)? Regards, Jan On 30 May 2015 at 02:34, Dow Drake dowdr...@gmail.com wrote: Thanks Jan! I was having the same issue with 6.7. The 6.6 deb you posted installed fine. Best, Dow Drake On Friday, May 29, 2015 at 8:42:26 AM UTC-7, Jan Groenewald wrote: The sage installation tree has moved is *probably* unrelated. It always says that on upgrade. I suspect two possibilities 1) it is from Thierry's binary not a buildslave binary 2) I changed the dpkg-source format from quilt to native to solve (1)'s impact on dpkg, and at the same time removed .git (had to) and then much more unneeded files. 6.7ppa7 is uploading with all the build and config and other folders back in the package (but not all the languages in docs). Should be there soon. I can still try going back to 6.6 to test that. Since the PPA is now broken:(, I might as well upload my tests there. If someone wants the working deb, it is at: https://launchpad.net/~aims/+archive/ubuntu/sagemath/+build/7362961/+files/sagemath-upstream-binary_6.6ppa1_amd64.deb You can download and dpkg -i that for a working installation (I think) Regards, Jan On 29 May 2015 at 17:18, Adrian Lam adrian...@gmail.com wrote: On Friday, May 29, 2015 at 2:50:02 PM UTC+1, Jan Groenewald wrote: Hi I'm working on this but compressing, building debs, and uploading takes quite long. Any feedback on any new version working or not working is useful. If I don't have it working by end of weekend I'll probably revert to 6.6 with a version number like 6.7ppa14revertsage6.6 in the PPA and make a new dev PPA. Apologies for the inconvenience. Regards, Jan Ubuntu 14.04.2, tried upgrading to 6.7ppa6 (from 6.7ppa4), still not working. By the way, since no one else has mentioned, upon FIRST attempt to upgrade, the log actually has 3 more lines: Setting up sagemath-upstream-binary (6.7ppa6) ... Running Sage once as root to set paths ┌┐ │ SageMath Version 6.7, Release Date: 2015-05-17 │ │ Type notebook() for the browser-based notebook interface.│ │ Type help() for help.│ └┘ The Sage installation tree has moved from /opt/sagemath_tmonteil-ubuntu-trusty-64/sage-6.7 to /usr/lib/sagemath Updating various hardcoded paths... (Please wait at most a few minutes.) DO NOT INTERRUPT THIS. Done updating paths. Traceback (most recent call last): File /usr/lib/sagemath/local/bin/sage-ipython, line 7, in module from sage.repl.interpreter import SageTerminalApp It has the The Sage installation tree has moved... line. Don't know whether it'll be useful though. Thanks. -- 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+...@googlegroups.com. To post to this group, send email to sage-...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ -- 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@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ -- 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@googlegroups.com. Visit
[sage-devel] Re: MathJax limit for TeX expression in notebook
+1 to this. What is the best course of action? Opening a ticket? Best regards, Michał On Friday, May 29, 2015 at 6:41:36 AM UTC+2, Andrey Novoseltsev wrote: On Thursday, 28 May 2015 16:45:20 UTC-6, kcrisman wrote: On Thursday, May 28, 2015 at 5:21:01 PM UTC-4, Michal Bejger wrote: Dear Sage Devs, I have a question related to the limited length of a TeX expression rendered by MathJax in the notebook - the variable responsible for it is MAXBUFFER [1], and its default value is 5*1024 (5KB), which in most cases is quite all right but sometimes, for example when printing tensor components in SageManifolds (sagemanifolds.obspm.fr), it's not enough. Is it possible to pass a MathJax preamble in the notebook? Or alternatively, can we have MAXBUFFER increased in Sage local/share/mathjax/config/TeX-AMS_HTML-full.js default configuration? In principle you should be able to just hardcode a different value in in your own notebook server. I suspect my students are hitting the same issue from time to time when working on optimization problems, I just had no idea how it can be fixed. What is the downside of increasing this buffer to say 10 or 20 kilobytes? My understanding is that the same MathJax is now shared by all frontends, so improvements will affect everybody! Andrey -- 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@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Arb as a standard package?
On 30/05/15 11:47, Dima Pasechnik wrote: On Friday, 29 May 2015 17:23:29 UTC+1, vdelecroix wrote: On 29/05/15 17:46, Marc Mezzarobba wrote: Fredrik Johansson's Arb library hasn't been an optional package for a full year yet, but Volker already suggested fast-tracking it to standard a while ago[1], and the (few) replies to his message were positive. Doing it now would make the development of the sage bindings a bit easier. Does anyone object to this change? As I already mentioned on tickets, the semantic of equality is a bit different for intervals and balls. This is annoying since they basically represent the same objects (=intervals with diadic bounds). This is my only objection for having it standard right now. Otherwise, I would be very happy to have it available for many applications in other parts of Sage! well, it's not the only bit of Sage with semantics a bit different from some other bit... This is the worst non-argument I can imagine: this is how it is in other places, so let do it that way. godwinLet me apply it to - software bugs: let us introduce this bug, because there are a lot of bugs in other softwares - women salaries vs men salaries: it is normal that for the same job a woman is less payed because it is the way it is in most situation - etc /godwin In other words, you can not minimize a problem by saying that it is a fact in many other places! I don't think this should preclude arb from becoming a standard package. Me neither, I just wanted to point out that it can be a source of trouble for everybody. Vincent -- 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@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: dpkg: error processing package sagemath-upstream-binary (--configure):
For what it's worth, I did not have success on Xubuntu 14.04 with sudo add-apt-repository ppa:aims/sagemath sudo apt-get update sudo apt-get install sagemath-upstream-binary=6.6ppa1 It reported that the package version was not found. But I did succeed with downloading the deb from the link above and calling sudo dpkg -i sagemath-upstream-binary_6.6ppa1_amd64.deb On Saturday, May 30, 2015 at 3:57:33 AM UTC-7, Jan Groenewald wrote: Hi Unfortunately 6.7ppa8revert6.6 has the same problem :( You should be able to do sudo apt-get install sagemath-upstream-binary=6.6ppa1 sudo apt-mark hold sagemath-upstream-binary to have a working system while the PPA is broken. Once it is fixed, I will let you know, you can, sudo apt-mark hold sagemath-upstream-binary I'll be looking for apt/dpkg/ppa help from colleagues over the next week to try and get a fixed version, any version, in the PPA, to prevent breaking further people's installations. To prevent this in future, we'll probably start a separate development PPA. Apologies for the inconvenience. There will be maybe only one more test this weekend; 6.7ppa9revert6.6 where I try a dpkg quilt format rather than native. Volker, I would very much like to get the buildslave binaries from snapperkob to test. Will they be uploaded to the sagemath download mirror (even though Thierry's binaries are there already)? Regards, Jan On 30 May 2015 at 02:34, Dow Drake dowd...@gmail.com javascript: wrote: Thanks Jan! I was having the same issue with 6.7. The 6.6 deb you posted installed fine. Best, Dow Drake On Friday, May 29, 2015 at 8:42:26 AM UTC-7, Jan Groenewald wrote: The sage installation tree has moved is *probably* unrelated. It always says that on upgrade. I suspect two possibilities 1) it is from Thierry's binary not a buildslave binary 2) I changed the dpkg-source format from quilt to native to solve (1)'s impact on dpkg, and at the same time removed .git (had to) and then much more unneeded files. 6.7ppa7 is uploading with all the build and config and other folders back in the package (but not all the languages in docs). Should be there soon. I can still try going back to 6.6 to test that. Since the PPA is now broken:(, I might as well upload my tests there. If someone wants the working deb, it is at: https://launchpad.net/~aims/+archive/ubuntu/sagemath/+build/7362961/+files/sagemath-upstream-binary_6.6ppa1_amd64.deb You can download and dpkg -i that for a working installation (I think) Regards, Jan On 29 May 2015 at 17:18, Adrian Lam adrian...@gmail.com wrote: On Friday, May 29, 2015 at 2:50:02 PM UTC+1, Jan Groenewald wrote: Hi I'm working on this but compressing, building debs, and uploading takes quite long. Any feedback on any new version working or not working is useful. If I don't have it working by end of weekend I'll probably revert to 6.6 with a version number like 6.7ppa14revertsage6.6 in the PPA and make a new dev PPA. Apologies for the inconvenience. Regards, Jan Ubuntu 14.04.2, tried upgrading to 6.7ppa6 (from 6.7ppa4), still not working. By the way, since no one else has mentioned, upon FIRST attempt to upgrade, the log actually has 3 more lines: Setting up sagemath-upstream-binary (6.7ppa6) ... Running Sage once as root to set paths ┌┐ │ SageMath Version 6.7, Release Date: 2015-05-17 │ │ Type notebook() for the browser-based notebook interface.│ │ Type help() for help.│ └┘ The Sage installation tree has moved from /opt/sagemath_tmonteil-ubuntu-trusty-64/sage-6.7 to /usr/lib/sagemath Updating various hardcoded paths... (Please wait at most a few minutes.) DO NOT INTERRUPT THIS. Done updating paths. Traceback (most recent call last): File /usr/lib/sagemath/local/bin/sage-ipython, line 7, in module from sage.repl.interpreter import SageTerminalApp It has the The Sage installation tree has moved... line. Don't know whether it'll be useful though. Thanks. -- 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+...@googlegroups.com. To post to this group, send email to sage-...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ -- 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+...@googlegroups.com javascript:. To post to this group, send email to
Re: [sage-devel] Re: dpkg: error processing package sagemath-upstream-binary (--configure):
Where of course the command to unhold in future is unhold, not hold. Regards, Jan On 30 May 2015 at 12:57, Jan Groenewald j...@aims.ac.za wrote: Hi Unfortunately 6.7ppa8revert6.6 has the same problem :( You should be able to do sudo apt-get install sagemath-upstream-binary=6.6ppa1 sudo apt-mark hold sagemath-upstream-binary to have a working system while the PPA is broken. Once it is fixed, I will let you know, you can, sudo apt-mark hold sagemath-upstream-binary I'll be looking for apt/dpkg/ppa help from colleagues over the next week to try and get a fixed version, any version, in the PPA, to prevent breaking further people's installations. To prevent this in future, we'll probably start a separate development PPA. Apologies for the inconvenience. There will be maybe only one more test this weekend; 6.7ppa9revert6.6 where I try a dpkg quilt format rather than native. Volker, I would very much like to get the buildslave binaries from snapperkob to test. Will they be uploaded to the sagemath download mirror (even though Thierry's binaries are there already)? Regards, Jan On 30 May 2015 at 02:34, Dow Drake dowdr...@gmail.com wrote: Thanks Jan! I was having the same issue with 6.7. The 6.6 deb you posted installed fine. Best, Dow Drake On Friday, May 29, 2015 at 8:42:26 AM UTC-7, Jan Groenewald wrote: The sage installation tree has moved is *probably* unrelated. It always says that on upgrade. I suspect two possibilities 1) it is from Thierry's binary not a buildslave binary 2) I changed the dpkg-source format from quilt to native to solve (1)'s impact on dpkg, and at the same time removed .git (had to) and then much more unneeded files. 6.7ppa7 is uploading with all the build and config and other folders back in the package (but not all the languages in docs). Should be there soon. I can still try going back to 6.6 to test that. Since the PPA is now broken:(, I might as well upload my tests there. If someone wants the working deb, it is at: https://launchpad.net/~aims/+archive/ubuntu/sagemath/+build/7362961/+files/sagemath-upstream-binary_6.6ppa1_amd64.deb You can download and dpkg -i that for a working installation (I think) Regards, Jan On 29 May 2015 at 17:18, Adrian Lam adrian...@gmail.com wrote: On Friday, May 29, 2015 at 2:50:02 PM UTC+1, Jan Groenewald wrote: Hi I'm working on this but compressing, building debs, and uploading takes quite long. Any feedback on any new version working or not working is useful. If I don't have it working by end of weekend I'll probably revert to 6.6 with a version number like 6.7ppa14revertsage6.6 in the PPA and make a new dev PPA. Apologies for the inconvenience. Regards, Jan Ubuntu 14.04.2, tried upgrading to 6.7ppa6 (from 6.7ppa4), still not working. By the way, since no one else has mentioned, upon FIRST attempt to upgrade, the log actually has 3 more lines: Setting up sagemath-upstream-binary (6.7ppa6) ... Running Sage once as root to set paths ┌┐ │ SageMath Version 6.7, Release Date: 2015-05-17 │ │ Type notebook() for the browser-based notebook interface.│ │ Type help() for help.│ └┘ The Sage installation tree has moved from /opt/sagemath_tmonteil-ubuntu-trusty-64/sage-6.7 to /usr/lib/sagemath Updating various hardcoded paths... (Please wait at most a few minutes.) DO NOT INTERRUPT THIS. Done updating paths. Traceback (most recent call last): File /usr/lib/sagemath/local/bin/sage-ipython, line 7, in module from sage.repl.interpreter import SageTerminalApp It has the The Sage installation tree has moved... line. Don't know whether it'll be useful though. Thanks. -- 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+...@googlegroups.com. To post to this group, send email to sage-...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ -- 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@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ -- You received this message because you are
Re: [sage-devel] Re: dpkg: error processing package sagemath-upstream-binary (--configure):
Hi, Obviously confronted with the same issue since an update last Thursday, I tried to revert as you posted above: sudo apt-get install sagemath-upstream-binary=6.6ppa1 Reading package lists... Done Building dependency tree Reading state information... Done E: Version ‘6.6ppa1’ for ‘sagemath-upstream-binary’ was not found Could you tell me how to install the previous version on Ubuntu 14.04 ? Thanks -- 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@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: dpkg: error processing package sagemath-upstream-binary (--configure):
sorry, just saw your post above ... On Saturday, 30 May 2015 16:10:46 UTC+2, Frederic Durodie wrote: Hi, Obviously confronted with the same issue since an update last Thursday, I tried to revert as you posted above: sudo apt-get install sagemath-upstream-binary=6.6ppa1 Reading package lists... Done Building dependency tree Reading state information... Done E: Version ‘6.6ppa1’ for ‘sagemath-upstream-binary’ was not found Could you tell me how to install the previous version on Ubuntu 14.04 ? Thanks -- 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@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Arb as a standard package?
On Friday, May 29, 2015 at 12:23:29 PM UTC-4, vdelecroix wrote: On 29/05/15 17:46, Marc Mezzarobba wrote: Fredrik Johansson's Arb library hasn't been an optional package for a full year yet, but Volker already suggested fast-tracking it to standard a while ago[1], and the (few) replies to his message were positive. Doing it now would make the development of the sage bindings a bit easier. Does anyone object to this change? As I already mentioned on tickets, the semantic of equality is a bit different for intervals and balls. This is annoying since they basically represent the same objects (=intervals with diadic bounds). This is my only objection for having it standard right now. Otherwise, I would be very happy to have it available for many applications in other parts of Sage! This definition of equality reflects a subtle difference between mpfi and arb, namely that arb simplifies some expressions based on pointer comparison. This reduces computation time and in some case leads to tighter enclosures. In particular, arb evaluates x * x as x^2 (which, in turn, affects many functions). One could still define (x == x) - False for non-exact arbs in Sage, but doing so potentially makes the difference in semantics for other operations harder to discover. I don't feel particularly strongly about keeping this feature forever. One could have separate squaring functions and do the same pointer comparisons at a higher level (the main drawback is that this leads to more code in various places). Code written with the current semantics in mind will remain valid if this feature is removed in the future. Conversely, one has to have this in mind when porting mpfi code to arb, though code that breaks because of this should be exceedingly rare. Fredrik -- 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@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Memory leak? Creation of DiGraph slows down.
On Sat, 30 May 2015, Nathann Cohen wrote: OK, so it's dot2tex (I guess). Somebody wants to test with it installed? Having doc2tex turns a 100ms function into a 30s functions ? O_o I tested this on 6.8beta1 on quite old and slow computer with 32-bit kernel. In this machine the result after dot2tex was An exception has occurred, use %tb to see the full traceback. SystemExit: 1 I guess this relates to same bug somewhere. It worked fast without dot2tex installed. -- Jori Mäntysalo
