[sage-devel] Re: trouble with error message during doctest
On Tuesday, May 26, 2015 at 4:41:01 PM UTC-7, David Perkinson wrote:
Success!
Doctesting 1 file.
sage -t src/sage/sandpiles/sandpile.py
[871 tests, 29.75 s]
--
All tests passed!
--
Total time for all tests: 30.2 seconds
cpu time: 18.5 seconds
cumulative wall time: 29.8 seconds
As advised, I replaced all instances of doctest:1: with doctest:
(I had tried doctest:.:, but that did not work.)
Right: in doctest results, ... is a wild card and can match anything. A
single dot would have to be matched exactly.
John
Thanks very much!
On Tuesday, May 26, 2015 at 4:36:07 PM UTC-7, John H Palmieri wrote:
On Tuesday, May 26, 2015 at 4:31:54 PM UTC-7, David Perkinson wrote:
EXAMPLES::
sage: S = sandpiles.Complete(4)
sage: D = SandpileDivisor(S, {0: 0, 1: 0, 2: 8, 3: 0})
sage: E = SandpileDivisor(S, {0: 2, 1: 2, 2: 2, 3: 2})
sage: v = firing_vector(S, D, E)
doctest:...: DeprecationWarning: firing_vector() will soon be
removed. Use SandpileDivisor.is_linearly_equivalent() instead.
See http://trac.sagemath.org/12345 for details.
doctest:1: DeprecationWarning: May 25, 2015: Replaced by
SandpileDivisor.is_linearly_equivalent.
See http://trac.sagemath.org/12345 for details.
Does it help if you replace doctest:1 with doctest:...? Search for
other occurrences of 'DeprecationWarning' in the source code, and make
yours like more like those. To search:
sage: search_src('DeprecationWarning')
--
John
--
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: Python 3 and the sage notebook
Personally, I'm fine with EOL for SageNB in 2020 together with Python 2.x. IMHO we should focus our energy on having a superior alternative ready by then. +1 At some point hopefully soon Jupyter notebook should be a sufficient replacement to sagenb, due to excellent work of volker and others. It takes very much the same approach ui-wise as sagenb, and is just missing some graphics/other support. And under the hood the architecture is better. 2020 seems more than reasonable, for sure. My concerns are * That people can still (easily) use their worksheets regardless of which Sage they download/build *right now* (which suggests keeping sagenb Python3-compatible) * That there is a really good migration flow for sws - whatever Jupyter will be, as with previous versions of sagenb migration * That Jupyter could be used as an in-house sagenb replacement for small-scale multi-user (which I hear is in the works) for those who would prefer this to trying to manage a local SMC installation But some of those questions may be naive. -- 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: Function call interface.
On Tuesday, May 26, 2015 at 10:15:02 PM UTC+2, David Einstein wrote: ... is the expected interface for classes that inherit from BuiltinFunction documented somewhere. The ones I know about are listed in the code for BuiltinFunction._register_function, but don't seem to be documented. For example, I believe that _evalf is supposed to be the numerical evaluation function, but do not have a clear understanding of what types it is expected to return, what exceptions it is expected to raise, etc. First, some information can be gained from the symbolic functions wiki page: http://trac.sagemath.org/wiki/symbolics/functions The most recently closed tickets and many of those needing work can be seen as example for good practice, because they were under scrutiny of the usual suspects regarding symbolics. While looking at #15786 with an eye to understanding the architecture of sage, I noticed the following comment before the __call__ method of Function_ceil and Function_floor. #FIXME: this should be moved to _eval_ ... Unfortunately, if we move all of the code from Function_ceil.__call__ to Function_ceil._eval_ then the call to BuiltinFunction.__call__ will then call Function_ceil._eval_ and we are on the way to infinite recursion. We cannot call BuiltinFunction._eval_, because BuiltinFunction does not implement _eval_. Is there some way to avoid this recursion? I don't think there is actually this problem because Jeroen Demeyer has included some neat tricks in BuiltinFunction that prevent this. Note that BuiltinFunction.__call__ also may call Function.__call__ which has complicated logic. What is the problem with overloading __call__? I was convinced by Jeroen that it's not necessary. I cannot point to his exact argument at the moment, sorry. 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] A suggestion for make
On 2015-05-24 20:41, john_perry_usm wrote: Does it seem reasonable to add a prompt at the beginning of the Makefile that points this out, suggests './sage -b' if they just want to fix some changes I am very much against this. The normal way to rebuild is to use make, while ./sage -b should only be used if you know what you're doing. I have seen several bug reports which were just people forgetting to run make. So my impression is that we need to advertise ./sage -b less, not more. I agree with Simon that the docs are annoying. However, I usually run make in a different shell window. I can already run and test Sage while the documentation is still building. Jeroen. -- 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 with vars()?
I opened a ticket for the underlying issue: == Trac #18512: Move notebook() into Sage Right now the `notebook()` function is a lazy import from sagenb. Hence any access (like looking at the docstring) imports sagenb which changes the display backend which causes various problems (see https://groups.google.com/d/msg/sage-devel/3uaY6xHLMqQ/Zyn67xJ0LaMJ). It also doesn't fit into a world where there is more than one notebook. And its current behavior of turning the current Sage session into a notebook server can't work with the IPython notebook or SMC. First, we should definitely move `notebook` into the Sage library to move it away from sagenb. The more general question is what to do with it then. Options are * Just let it launch SageNB, any other notebook needs to be launched via `sage --notebook=...` on the commandline * Deprecate `notebook()` altogether * Let `notebook()` always spawn an independent process, and add an argument to select which one Status: new Component: notebook Last modified: 2015-05-26 07:04:55 Created: 2015-05-26 07:04:55 UTC Report upstream: N/A Authors: Reviewers: Branch: Keywords: Dependencies: -- URL: http://trac.sagemath.org/18512 == On Wednesday, May 6, 2015 at 10:51:27 AM UTC+2, Jean-Pierre Flori wrote: Dear all, My Sage 6.6 install quits after printing a depreciation warning message when I issue: sage: vars() Same is true for at least globals(). Any clue on what's going on? Best, JP -- 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] A short description of what Sage days are on the wiki page
On 26/05/15 06:38, William Stein wrote: On Mon, May 25, 2015 at 12:05 PM, Nathann Cohen nathann.co...@gmail.com wrote: Hello everybody, I just noticed that the wiki page on Sage Days [2] can be reached quite easily from Sage's website [1]. Thus, we can expect many persons (ignorant of our customs and traditions) to read it. This page is actually quite clean and up-to-date, but it was lacking a short paragraph at the top of the page explaining to newcomers what exactly Sage days are. I added a short one, which everybody can freely [edit/change totally]. It is my first time editing this page, and I thought it would be a good idea to write here to tell everybody how public that page is. I changed it to the following: Sage Days are gatherings of people interested in SageMath development. Contributors, enthusiastic users, and newcomers often attend. Sage Days are organized by a wide range of people around the globe. This is not how I do practice Sage days. There are days which gather developers, but I did quite a few which were just about advertising Sage to newcomers. 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] A short description of what Sage days are on the wiki page
On 26/05/15 09:25, William Stein wrote: On Tue, May 26, 2015 at 12:17 AM, Vincent Delecroix 20100.delecr...@gmail.com wrote: On 26/05/15 06:38, William Stein wrote: On Mon, May 25, 2015 at 12:05 PM, Nathann Cohen nathann.co...@gmail.com wrote: Hello everybody, I just noticed that the wiki page on Sage Days [2] can be reached quite easily from Sage's website [1]. Thus, we can expect many persons (ignorant of our customs and traditions) to read it. This page is actually quite clean and up-to-date, but it was lacking a short paragraph at the top of the page explaining to newcomers what exactly Sage days are. I added a short one, which everybody can freely [edit/change totally]. It is my first time editing this page, and I thought it would be a good idea to write here to tell everybody how public that page is. I changed it to the following: Sage Days are gatherings of people interested in SageMath development. Contributors, enthusiastic users, and newcomers often attend. Sage Days are organized by a wide range of people around the globe. This is not how I do practice Sage days. There are days which gather developers, but I did quite a few which were just about advertising Sage to newcomers. Are you proposing changing it to the following: Sage Days are gatherings of people interested in SageMath. Contributors, enthusiastic users, and newcomers often attend. Sage Days are organized by a wide range of people around the globe. ? What about Sage Days are gatherings of people interested in SageMath, from newcomers to contributors. Sage Days are organized by a wide range of people around the globe. 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.
[sage-devel] Python 2.7.10 released
Pyton 2.7.10 released. https://www.python.org/downloads/release/python-2710/ Python 2.7.10 Release Date: 2015-05-23 Python 2.7.10 is a bug fix release of the Python 2.7.x series. Changelog: https://hg.python.org/cpython/raw-file/15c95b7d81dc/Misc/NEWS -- 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] A short description of what Sage days are on the wiki page
On Tue, May 26, 2015 at 12:17 AM, Vincent Delecroix 20100.delecr...@gmail.com wrote: On 26/05/15 06:38, William Stein wrote: On Mon, May 25, 2015 at 12:05 PM, Nathann Cohen nathann.co...@gmail.com wrote: Hello everybody, I just noticed that the wiki page on Sage Days [2] can be reached quite easily from Sage's website [1]. Thus, we can expect many persons (ignorant of our customs and traditions) to read it. This page is actually quite clean and up-to-date, but it was lacking a short paragraph at the top of the page explaining to newcomers what exactly Sage days are. I added a short one, which everybody can freely [edit/change totally]. It is my first time editing this page, and I thought it would be a good idea to write here to tell everybody how public that page is. I changed it to the following: Sage Days are gatherings of people interested in SageMath development. Contributors, enthusiastic users, and newcomers often attend. Sage Days are organized by a wide range of people around the globe. This is not how I do practice Sage days. There are days which gather developers, but I did quite a few which were just about advertising Sage to newcomers. Are you proposing changing it to the following: Sage Days are gatherings of people interested in SageMath. Contributors, enthusiastic users, and newcomers often attend. Sage Days are organized by a wide range of people around the globe. ? William -- 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] Does anybody ever use make build-serial?
On 26/05/2015, at 21:52, Jeroen Demeyer jdeme...@cage.ugent.be wrote: Hello, when support for building Sage in parallel was added, a target build-serial was added to the top-level Makefile. However, I don't think that this actually has a use-case. Can’t think of one either. In order to simplify building Sage, I propose to remove this target. +1 My eventual goal is to move more stuff from the top-level Makefile down into build/Makefile (and possibly a new src/doc/Makefile) -- 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: Does anybody ever use make build-serial?
Neither can I. If I recall correctly, exporting MAKE=make -j1 forces a serial build. And I have never heard of that make target before... +1 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: Does anybody ever use make build-serial?
Hi! On 2015-05-26, Francois Bissey francois.bis...@canterbury.ac.nz wrote: On 26/05/2015, at 21:52, Jeroen Demeyer jdeme...@cage.ugent.be wrote: when support for building Sage in parallel was added, a target build-serial was added to the top-level Makefile. However, I don't think that this actually has a use-case. Can’t think of one either. Neither can I. If I recall correctly, exporting MAKE=make -j1 forces a serial build. And I have never heard of that make target before... Best regards, Simon -- 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: Why \wedge works but \vee does not?
It's not a bug. The backslash is used in string formatting: \v has some meaning, while \w does not. See http://pythonweb.org/projects/webmodules/doc/0.5.3/html_multipage/lib/node48.html Unfortunately, the backslash is also used in LaTeX formatting. I discovered a long time ago that it's best to pass Latex in strings with double backslash, for instance, \\vee. I guess the raw string thing works, too. john perry -- 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] Does anybody ever use make build-serial?
Hello, when support for building Sage in parallel was added, a target build-serial was added to the top-level Makefile. However, I don't think that this actually has a use-case. In order to simplify building Sage, I propose to remove this target. My eventual goal is to move more stuff from the top-level Makefile down into build/Makefile (and possibly a new src/doc/Makefile) -- 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: what needs deprecation?
I vote for a case-by-case basis, but with a bias towards not deprecating. Same but with (slight) bias toward deprecating, in terms of things like this. I disagree that from sage.module.cool_but_hidden import SolveRiemannHypothesis SolveRiemannHypothesis() changing to from sage.module.prove_all import SolveRiemannHypothesis SolveRiemannHypothesis() is an implementation detail, because there are so many Python modules that one has to import in this way even to use. (Such as trying to use Sympy or matplotlib or Scipy inside of Sage.) It may be the case that the cognoscenti consider that a detail, but I figure tab-completable things probably should at least be considered semi-public. This isn't Java! But of course in some circumstances (maybe even many) this could be troublesome. In this case it was an underscore method, though, right? So not too easily visible, not in documentation... I could go either way. If other stuff, then maybe not. Have fun! -- 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] 404 Error: page not found
Click Changelog on http://www.sagemath.org/ Or README.txt on http://www.sagemath.org/download-source.html http://www.sagemath.org/mirror/src/README.txt Ralf -- 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: 404 Error: page not found
Click Changelog on http://www.sagemath.org/ Correct. Jeroen has the script for this - we also need to run it for 6.6 and 6.7. As always, I'm happy to do the proofreading... -- 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] Python 3 and the sage notebook
In the interest of reducing the work required for supporting Python 3, unless there is some champion out there who wants to do the hard work making sagenb work with Python 3, the sage notebook will not be joining the rest of sage with Python 3. So, with that said, is there anyone interested in porting (and maintaining) sagenb to python 3? -- Andrew -- 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: Python 3 and the sage notebook
In the interest of reducing the work required for supporting Python 3, unless there is some champion out there who wants to do the hard work making sagenb work with Python 3, the sage notebook will not be joining the rest of sage with Python 3. That would be really bad for backward incompatibility unless you mean Sage will support Python 2 and 3, but the notebook will only run under 3. Even the likely-appearing SMC personal edition is really not the same. So, with that said, is there anyone interested in porting (and maintaining) sagenb to python 3? https://github.com/sagemath/sagenb/issues/343 I mean, how many Python 2-isms can there be in sagenb? (Other than formatting, which we've already been trying to encourage people to switch over - I don't know that there are a lot of print statements. Presumably there are other things.) -- 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: Python 3 and the sage notebook
Personally, I'm fine with EOL for SageNB in 2020 together with Python 2.x. IMHO we should focus our energy on having a superior alternative ready by then. On Tuesday, May 26, 2015 at 8:12:30 PM UTC+2, R. Andrew Ohana wrote: In the interest of reducing the work required for supporting Python 3, unless there is some champion out there who wants to do the hard work making sagenb work with Python 3, the sage notebook will not be joining the rest of sage with Python 3. So, with that said, is there anyone interested in porting (and maintaining) sagenb to python 3? -- Andrew -- 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] Function call interface.
While looking at #15786 with an eye to understanding the architecture of sage, I noticed the following comment before the __call__ method of Function_ceil and Function_floor. #FIXME: this should be moved to _eval_ After some rummaging about I see that the problem is that the function looks something like def __call__(self, x): try a bunch of stuff else: return BuiltinFunction.__call__(self, SR(x_original)) the intention being, if we cannot find a numerical result, just leave it as a symbolic result. This works when we overload the __call__ interface because the BuiltinFunction.__call__ will not reach our code again. Unfortunately, if we move all of the code from Function_ceil.__call__ to Function_ceil._eval_ then the call to BuiltinFunction.__call__ will then call Function_ceil._eval_ and we are on the way to infinite recursion. We cannot call BuiltinFunction._eval_, because BuiltinFunction does not implement _eval_. Is there some way to avoid this recursion? What is the problem with overloading __call__? On a not entirely unrelated note, is the expected interface for classes that inherit from BuiltinFunction documented somewhere. The ones I know about are listed in the code for BuiltinFunction._register_function, but don't seem to be documented. For example, I believe that _evalf is supposed to be the numerical evaluation function, but do not have a clear understanding of what types it is expected to return, what exceptions it is expected to raise, etc. -- 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 hilbert numerator of a big ideal?
Hi! So, the workaround I found was to wrap cocoa using a subprocess... It works quite ok for my purposes... Thanks for your help! JP Le samedi 23 mai 2015 08:05:51 UTC+3, john_perry_usm a écrit : Ok, I'll have a look at frobby! Just to check, I installed Macaulay2 and did the same computation and it gave me the right answer... CoCoA might also compute the correct answer, as I believe CoCoA switches silently to bigint whenever it notices the need. I don't think Sage supports CoCoA anymore though. (I'd like to fix that one day, but there are lots of things I'd like to do one day...) So I could interface my code, but this is not the optimal way. If it is a bug, it should be looked at and repaired... I'm willing to be corrected here, but my reaction is that this is not a bug. Sage uses Singular as its commutative algebra engine, and Singular advertises this limitation. As an analogy, it's not a bug if a computer algebra system that cautions users that it works only modulo a prime p gives you 1-2=p-1 instead of -1. That doesn't mean we can't address it. Hilbert series polynomials work with int, so maybe a workaround would be to check output from Singular, and see if 2^32 divides it; if so, cancel the corresponding term. I don't know if we can guarantee that this is always correct. Alternately, we can ask upstream. john perry -- 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: Python 3 and the sage notebook
On Tue, May 26, 2015 at 11:53 AM, kcrisman kcris...@gmail.com wrote: In the interest of reducing the work required for supporting Python 3, unless there is some champion out there who wants to do the hard work making sagenb work with Python 3, the sage notebook will not be joining the rest of sage with Python 3. That would be really bad for backward incompatibility unless you mean Sage will support Python 2 and 3, but the notebook will only run under 3. Even the likely-appearing SMC personal edition is really not the same. I mean that you will continue to be able to use sagenb under Python 2 (which Sage should support for a good long while), but unless someone ports sagenb to also work under Python 3, then you will not be able to use sagenb with sage on sagenb when you build sage with Python 3. So, with that said, is there anyone interested in porting (and maintaining) sagenb to python 3? https://github.com/sagemath/sagenb/issues/343 I mean, how many Python 2-isms can there be in sagenb? (Other than formatting, which we've already been trying to encourage people to switch over - I don't know that there are a lot of print statements. Presumably there are other things.) -- 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. -- Andrew -- 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: Python 3 and the sage notebook
I mean that you will continue to be able to use sagenb under Python 2 (which Sage should support for a good long while), but unless someone ports sagenb to also work under Python 3, then you will not be able to use sagenb with sage on sagenb when you build sage with Python 3. Oh. So we would start providing binaries for Python2 and others with Python3? -- 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: sage binaries useless for development
Hi, I've decided to not worry about this sad loss of functionality. Instead, for SageMathCloud at least, I'm just going to write a new bdist that will start over by doing (1) tar'ing up a clean Sage build. I may then add (2) reducing the size a little, if there is anything obvious, which doesn't break developing Sage. Nobody says you have to make a tarball of sage using bdist. William On Mon, May 25, 2015 at 9:24 PM, William Stein wst...@gmail.com wrote: On Mon, May 25, 2015 at 12:44 PM, Dima Pasechnik dimp...@gmail.com wrote: On Monday, 25 May 2015 20:17:49 UTC+1, William wrote: Hi, Just curious -- is this intentional? 1. Build sage. 2. Type ./sage -bdist ... 3. Extract the resulting tarball elsewhere 4. Type make inside the extracted directory. BOOM! Total disaster. Has it ever worked? Yes, because the first version of sage -bdist was a 1-liner that just tar'd up the exact installation. Then we kept removing things to save disk space... My unusual, but I think a very important, basic design principle with sage binaries was that it was *super important* that one could do development with them. The idea is that a person would play with Sage (as a user), then with minimal effort switch to doing some development and contributing. This has clearly been completely lost in the current binaries. It's also been lost in SageMathCloud -- but I hope to get it back there (e.g., there could be a link the output of a docstring or source code of a function in a worksheet, which would setup a dev environment, and get you going editing that very function...) IMHO nothing beyond 'sage -b' worked in this case... It starts by trying to download tarballs from the internet, etc... this is certainly worse than it was. -- William -- William (http://wstein.org) -- 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. -- William (http://wstein.org) -- William (http://wstein.org) -- 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] A short description of what Sage days are on the wiki page
On Tue, May 26, 2015 at 12:33 AM, Vincent Delecroix 20100.delecr...@gmail.com wrote: On 26/05/15 09:25, William Stein wrote: On Tue, May 26, 2015 at 12:17 AM, Vincent Delecroix 20100.delecr...@gmail.com wrote: On 26/05/15 06:38, William Stein wrote: On Mon, May 25, 2015 at 12:05 PM, Nathann Cohen nathann.co...@gmail.com wrote: Hello everybody, I just noticed that the wiki page on Sage Days [2] can be reached quite easily from Sage's website [1]. Thus, we can expect many persons (ignorant of our customs and traditions) to read it. This page is actually quite clean and up-to-date, but it was lacking a short paragraph at the top of the page explaining to newcomers what exactly Sage days are. I added a short one, which everybody can freely [edit/change totally]. It is my first time editing this page, and I thought it would be a good idea to write here to tell everybody how public that page is. I changed it to the following: Sage Days are gatherings of people interested in SageMath development. Contributors, enthusiastic users, and newcomers often attend. Sage Days are organized by a wide range of people around the globe. This is not how I do practice Sage days. There are days which gather developers, but I did quite a few which were just about advertising Sage to newcomers. Are you proposing changing it to the following: Sage Days are gatherings of people interested in SageMath. Contributors, enthusiastic users, and newcomers often attend. Sage Days are organized by a wide range of people around the globe. ? What about Sage Days are gatherings of people interested in SageMath, from newcomers to contributors. Sage Days are organized by a wide range of people around the globe. Sounds good to me -- anybody should feel free to edit the wiki... 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. -- William (http://wstein.org) -- 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: Python 3 and the sage notebook
On Tue, May 26, 2015 at 1:01 PM, Volker Braun vbraun.n...@gmail.com wrote: Personally, I'm fine with EOL for SageNB in 2020 together with Python 2.x. IMHO we should focus our energy on having a superior alternative ready by then. +1 At some point hopefully soon Jupyter notebook should be a sufficient replacement to sagenb, due to excellent work of volker and others. It takes very much the same approach ui-wise as sagenb, and is just missing some graphics/other support. And under the hood the architecture is better. -- William On Tuesday, May 26, 2015 at 8:12:30 PM UTC+2, R. Andrew Ohana wrote: In the interest of reducing the work required for supporting Python 3, unless there is some champion out there who wants to do the hard work making sagenb work with Python 3, the sage notebook will not be joining the rest of sage with Python 3. So, with that said, is there anyone interested in porting (and maintaining) sagenb to python 3? -- Andrew -- 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. -- William (http://wstein.org) -- 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] Log files in dot-sage
Hello, There are apparently log files written to .sage. This causes issues with SageMathCell which makes .sage immutable and there are commands that trigger creation of some of these files, but it looks like the list is growing, currently print gp.eval(5*6;) in a cell leads to IOError: [Errno 13] Permission denied: '/home/sc_work/.sage/gp-expect.log' My questions: 1) Why are such log files created there at all? 2) Why have things that didn't use them before started creating them now? 3) Is there a better solution to the problem than touching this file before making .sage immutable? Thank you! 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.
[sage-devel] trouble with error message during doctest
Could someone help me with the following error message? I am making a lot of revisions to sandpile.py, and all doctests had passed up until I decided to deprecate some functions. After that, I needed to add the deprecation warnings to some Examples sections. I cleared up all those errors and was hoping to get the All tests passed! line but got this instead: = Doctesting 1 file. sage -t src/sage/sandpiles/sandpile.py Error: Source line number found -- sage -t src/sage/sandpiles/sandpile.py # Source line number found -- Total time for all tests: 30.6 seconds cpu time: 0.0 seconds cumulative wall time: 0.0 seconds = Thanks, David -- 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: trouble with error message during doctest
This message apparently means Doctest contains explicit source line number. Can you provide an example of a doctest you changed when adding the deprecation warnings? John On Tuesday, May 26, 2015 at 4:11:36 PM UTC-7, David Perkinson wrote: Could someone help me with the following error message? I am making a lot of revisions to sandpile.py, and all doctests had passed up until I decided to deprecate some functions. After that, I needed to add the deprecation warnings to some Examples sections. I cleared up all those errors and was hoping to get the All tests passed! line but got this instead: = Doctesting 1 file. sage -t src/sage/sandpiles/sandpile.py Error: Source line number found -- sage -t src/sage/sandpiles/sandpile.py # Source line number found -- Total time for all tests: 30.6 seconds cpu time: 0.0 seconds cumulative wall time: 0.0 seconds = Thanks, David -- 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: trouble with error message during doctest
One more thing: I also replaced each instance of doctest:858: with
doctest:
On Tuesday, May 26, 2015 at 4:31:54 PM UTC-7, David Perkinson wrote:
EXAMPLES::
sage: S = sandpiles.Complete(4)
sage: D = SandpileDivisor(S, {0: 0, 1: 0, 2: 8, 3: 0})
sage: E = SandpileDivisor(S, {0: 2, 1: 2, 2: 2, 3: 2})
sage: v = firing_vector(S, D, E)
doctest:...: DeprecationWarning: firing_vector() will soon be
removed. Use SandpileDivisor.is_linearly_equivalent() instead.
See http://trac.sagemath.org/12345 for details.
doctest:1: DeprecationWarning: May 25, 2015: Replaced by
SandpileDivisor.is_linearly_equivalent.
See http://trac.sagemath.org/12345 for details.
Here is an example of a way I modified an EXAMPLES section. When I first
ran the doctest it gave errors of the form: expect blah1, got blah2. In
each of these cases, I just replaced blah1 by blah2.
On Tuesday, May 26, 2015 at 4:21:10 PM UTC-7, John H Palmieri wrote:
This message apparently means Doctest contains explicit source line
number. Can you provide an example of a doctest you changed when adding
the deprecation warnings?
John
On Tuesday, May 26, 2015 at 4:11:36 PM UTC-7, David Perkinson wrote:
Could someone help me with the following error message? I am making a
lot of revisions to sandpile.py, and all doctests had passed up until I
decided to deprecate some functions. After that, I needed to add the
deprecation warnings to some Examples sections. I cleared up all those
errors and was hoping to get the All tests passed! line but got this
instead:
=
Doctesting 1 file.
sage -t src/sage/sandpiles/sandpile.py
Error: Source line number found
--
sage -t src/sage/sandpiles/sandpile.py # Source line number found
--
Total time for all tests: 30.6 seconds
cpu time: 0.0 seconds
cumulative wall time: 0.0 seconds
=
Thanks,
David
--
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: trouble with error message during doctest
On Tuesday, May 26, 2015 at 4:31:54 PM UTC-7, David Perkinson wrote:
EXAMPLES::
sage: S = sandpiles.Complete(4)
sage: D = SandpileDivisor(S, {0: 0, 1: 0, 2: 8, 3: 0})
sage: E = SandpileDivisor(S, {0: 2, 1: 2, 2: 2, 3: 2})
sage: v = firing_vector(S, D, E)
doctest:...: DeprecationWarning: firing_vector() will soon be
removed. Use SandpileDivisor.is_linearly_equivalent() instead.
See http://trac.sagemath.org/12345 for details.
doctest:1: DeprecationWarning: May 25, 2015: Replaced by
SandpileDivisor.is_linearly_equivalent.
See http://trac.sagemath.org/12345 for details.
Does it help if you replace doctest:1 with doctest:...? Search for
other occurrences of 'DeprecationWarning' in the source code, and make
yours like more like those. To search:
sage: search_src('DeprecationWarning')
--
John
--
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] trouble with error message during doctest
Not a complete answer, but it's coming from matching the regular expression re.compile(r^\s*doctest:[0-9]) See line 257 of sage/doctest/sources.py David On Tue, May 26, 2015 at 7:11 PM, David Perkinson dav...@reed.edu wrote: Could someone help me with the following error message? I am making a lot of revisions to sandpile.py, and all doctests had passed up until I decided to deprecate some functions. After that, I needed to add the deprecation warnings to some Examples sections. I cleared up all those errors and was hoping to get the All tests passed! line but got this instead: = Doctesting 1 file. sage -t src/sage/sandpiles/sandpile.py Error: Source line number found -- sage -t src/sage/sandpiles/sandpile.py # Source line number found -- Total time for all tests: 30.6 seconds cpu time: 0.0 seconds cumulative wall time: 0.0 seconds = Thanks, David -- 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. -- 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: trouble with error message during doctest
Success!
Doctesting 1 file.
sage -t src/sage/sandpiles/sandpile.py
[871 tests, 29.75 s]
--
All tests passed!
--
Total time for all tests: 30.2 seconds
cpu time: 18.5 seconds
cumulative wall time: 29.8 seconds
As advised, I replaced all instances of doctest:1: with doctest:
(I had tried doctest:.:, but that did not work.)
Thanks very much!
On Tuesday, May 26, 2015 at 4:36:07 PM UTC-7, John H Palmieri wrote:
On Tuesday, May 26, 2015 at 4:31:54 PM UTC-7, David Perkinson wrote:
EXAMPLES::
sage: S = sandpiles.Complete(4)
sage: D = SandpileDivisor(S, {0: 0, 1: 0, 2: 8, 3: 0})
sage: E = SandpileDivisor(S, {0: 2, 1: 2, 2: 2, 3: 2})
sage: v = firing_vector(S, D, E)
doctest:...: DeprecationWarning: firing_vector() will soon be
removed. Use SandpileDivisor.is_linearly_equivalent() instead.
See http://trac.sagemath.org/12345 for details.
doctest:1: DeprecationWarning: May 25, 2015: Replaced by
SandpileDivisor.is_linearly_equivalent.
See http://trac.sagemath.org/12345 for details.
Does it help if you replace doctest:1 with doctest:...? Search for
other occurrences of 'DeprecationWarning' in the source code, and make
yours like more like those. To search:
sage: search_src('DeprecationWarning')
--
John
--
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: trouble with error message during doctest
EXAMPLES::
sage: S = sandpiles.Complete(4)
sage: D = SandpileDivisor(S, {0: 0, 1: 0, 2: 8, 3: 0})
sage: E = SandpileDivisor(S, {0: 2, 1: 2, 2: 2, 3: 2})
sage: v = firing_vector(S, D, E)
doctest:...: DeprecationWarning: firing_vector() will soon be
removed. Use SandpileDivisor.is_linearly_equivalent() instead.
See http://trac.sagemath.org/12345 for details.
doctest:1: DeprecationWarning: May 25, 2015: Replaced by
SandpileDivisor.is_linearly_equivalent.
See http://trac.sagemath.org/12345 for details.
Here is an example of a way I modified an EXAMPLES section. When I first
ran the doctest it gave errors of the form: expect blah1, got blah2. In
each of these cases, I just replaced blah1 by blah2.
On Tuesday, May 26, 2015 at 4:21:10 PM UTC-7, John H Palmieri wrote:
This message apparently means Doctest contains explicit source line
number. Can you provide an example of a doctest you changed when adding
the deprecation warnings?
John
On Tuesday, May 26, 2015 at 4:11:36 PM UTC-7, David Perkinson wrote:
Could someone help me with the following error message? I am making a
lot of revisions to sandpile.py, and all doctests had passed up until I
decided to deprecate some functions. After that, I needed to add the
deprecation warnings to some Examples sections. I cleared up all those
errors and was hoping to get the All tests passed! line but got this
instead:
=
Doctesting 1 file.
sage -t src/sage/sandpiles/sandpile.py
Error: Source line number found
--
sage -t src/sage/sandpiles/sandpile.py # Source line number found
--
Total time for all tests: 30.6 seconds
cpu time: 0.0 seconds
cumulative wall time: 0.0 seconds
=
Thanks,
David
--
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.
