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.
>
>
> > 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 exce
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!
>
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
cp
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 = S
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)
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
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 erro
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 wrote:
> Could someone help me with the following error message? I am making a lot
> of rev
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
On Tue, May 26, 2015 at 1:01 PM, Volker Braun 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
replacemen
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:
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 som
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 Pytho
>
> 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.
On Tue, May 26, 2015 at 11:53 AM, kcrisman 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
> 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 backwa
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 por
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:
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 com
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'
>
> 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.modul
> 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 unsubscr
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 st
>
> 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 s
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
Hi!
On 2015-05-26, Francois Bissey wrote:
>> On 26/05/2015, at 21:52, Jeroen Demeyer 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
> On 26/05/2015, at 21:52, Jeroen Demeyer 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 simpli
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
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 thi
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
wrote:
Hello everybody,
I just noticed that the wiki page on "Sage Days
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
>> wrote:
>>>
>>> Hello everybody,
>>>
>>> I just noticed that the wiki page on "Sage Days" [2] can be reached
On 26/05/15 06:38, William Stein wrote:
On Mon, May 25, 2015 at 12:05 PM, Nathann Cohen 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)
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
34 matches
Mail list logo
