On Tue, Jan 5, 2016 at 5:57 AM, kcrisman wrote:
> The question wasn't for you, but for all those who early in this thread said
> how awesome Jupyter was. But thank you for confirming.
Some people tend to use/develop either Jupyter or SageMath notebooks
exclusively, and remain a little ignorant o
On Mon, Jan 4, 2016 at 10:21 AM, kcrisman wrote:
> Thank you Jonathan for clarifying what I thought was obvious in what I was
> saying.
>
>
>> > As stated, that would break the compatibility with SMC magics that
>> William
>> > just declared intangible (and always "cell magic").
>>
>> Just to be
On Sun, Jan 3, 2016 at 1:49 PM, Emmanuel Charpentier
wrote:
>
>
> Le dimanche 3 janvier 2016 21:23:56 UTC+1, Volker Braun a écrit :
>>
>> On Sunday, January 3, 2016 at 5:36:30 PM UTC+1, Emmanuel Charpentier
>> wrote:
>>>
>>> [ BTW : that's not really a bug, but rather a design conflict : the
>>> o
On Sun, Jan 3, 2016 at 8:36 AM, Emmanuel Charpentier
wrote:
> Dear Volker,
>
> Le dimanche 3 janvier 2016 16:33:36 UTC+1, Volker Braun a écrit :
>>
>> On Sunday, January 3, 2016 at 2:41:51 PM UTC+1, Emmanuel Charpentier
>> wrote:
>>>
>>> "other language" cells : %maxima and %r (possibly other inte
Hi,
Is there anybody that can help me with the Sage booth at the Joint
Math Meetings this coming week?
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 ema
On Sat, Jan 2, 2016 at 10:41 AM, kcrisman wrote:
>
>> You still haven't understood that this is about how to create new
>> notebooks. We have the legacy support covered by shipping the old notebook.
>> Also, I don't recall Microsoft bundling a free copy of word 2007 with word
>> 2010, you are comp
On Saturday, January 2, 2016, Volker Braun wrote:
> You still haven't understood that this is about how to create new
> notebooks. We have the legacy support covered by shipping the old notebook.
> Also, I don't recall Microsoft bundling a free copy of word 2007 with word
> 2010, you are comparin
Thanks everybody -- that was extremely helpful!
On Wed, Dec 30, 2015 at 12:49 PM, Francois Bissey
wrote:
>
>> On 31/12/2015, at 09:31, Volker Braun wrote:
>>
>> There isn't an easy way to "delete everything thats not needed in a
>> system-wide install". Ideally you should only need the "sage" s
Hi,
I just built Sage-6.10 from source and installed quite a few packages,
which uses a total of 10G
of precious disk space:
salvus@compute0-us:/projects/sage/sage-6.10$ du -sch * |sort -h
0 config.log
0 data
4.0Kbootstrap
4.0Khome
4.0KVERSION.txt
8.0KMakefile
8.0K
On Tue, Dec 29, 2015 at 8:21 PM, Nathan Dunfield wrote:
>> (2) The current version on the pyx website is 0.14 (and they had
>> releases this year), but we're distributing version 0.10 from *2007*!
>
>
> Not that it matters, but for Python 2.7 the current version of pyx is 0.12.1
> (circa 2012);
On Tue, Dec 29, 2015 at 2:05 PM, mmarco wrote:
> In the cases mentioned in the ticket, the situation is the opposite of what
> you describe: they work well(ish) on 64 bits, but are somehow broken on 32
> bits.
It doesn't matter -- just swap 32 and 64 bit...
> Hence the question is wether we sho
http://trac.sagemath.org/ticket/19802
On Tue, Dec 29, 2015 at 1:41 PM, Volker Braun wrote:
> "pyx" is an old-style spkg, nobody has touched it in at least 2 years when
> we changed the packaging system. Nobody tests it, clearly nobody uses it,
> and I dare say nobody knows what its for. Apparentl
On Tue, Dec 29, 2015 at 1:07 PM, Volker Braun wrote:
> Its yet another old-style spkg booby trap.
Can you please clarify -- what does the problem I described have to do
with old style versus new style? The problem is code that contains a
docstring whose existence breaks import the python path mo
Hi,
An optional (not experimental) package called "pyx" is available for Sage [1].
DO NOT INSTALL IT!
I just did on Ubuntu 15.10, and it completely hosed my python install,
so that I couldn't start sage/ipython/etc. It turned out that "import
path" (path.py is part of python) failed due to a
On Tue, Dec 29, 2015 at 10:22 AM, mmarco wrote:
> In #19781 there are some issues with several optional packages that don't
> build or work correctly on 32 bits. Volker points that the lack of
> availability of 32 bits platforms make them harder to test and fix. So,
> should we change the policy a
On Sunday, December 27, 2015, Jori Mäntysalo wrote:
> On Sun, 27 Dec 2015, Nathann Cohen wrote:
>
> I expect to have two direct lines, but instead longer line bends at element
>>> 2. Is there some reason for this?
>>>
>>
>> You incorrectly believe that the poset code computes the layout
>> compon
On Sun, Dec 20, 2015 at 4:06 PM, Volker Braun wrote:
> On Sunday, December 20, 2015 at 10:27:39 PM UTC+1, William wrote:
>>
>> Notebooks in sagenb are basically individual files; it's just that
>> they are stored as a directory tree in the filesystem.
>
>
> Yes, what I meant was: SageNB doesn't sh
On Sun, Dec 20, 2015 at 12:47 PM, Volker Braun wrote:
> The ticket already has a notice printed that tells you how to run the old
> SageNB
>
> Realistically, since we are switching to a model where notebooks are
> individual files there is always going to be somebody who won't read the
> hints. We
On Sun, Dec 20, 2015 at 10:52 AM, Dima Pasechnik wrote:
>
>
> On Friday, 18 December 2015 15:27:29 UTC, Volker Braun wrote:
>>
>> IMHO the Jupyter/IPython notebook is a clear winner, no real contest.
>>
>> Nobody prevents you form using SageNB for existing worksheets or the live
>> documentation;
On Sat, Dec 19, 2015 at 10:23 AM, kcrisman wrote:
>
>>> There are some things which don't work yet in Sage on Jupyter, for
>>> example interacts.
>>
>>
>> SageNB interacts don't work, but Jupyter interacts do. The syntax is
>> slightly different but it would be easy enough to provide a compatibili
On Fri, Dec 18, 2015 at 6:50 AM, mancio wrote:
> Hello,
>
> I am experimenting some problem concerning the pickling of 3D graphic
> objects.
>
> Here the exemple:
>
> 2D)
> c = circle((1,1), 1)
> show(loads(dumps(c)))
>
> And I get the 2D plot of the circle
>
> 3D)
> c = circle((1,1,1), 1)
> d = l
On Fri, Dec 18, 2015 at 6:47 AM, Emmanuel Charpentier
wrote:
> A few addenda :
>
> Pros :
> * The python debugger works in the IPython notebook. Damn useful !
> * Some extensions developed for Python worksheets run in Sage worksheets.
>
> Cons :
> * (Currently) no standard way to create a cell
On Thursday, December 17, 2015, Francois Bissey <
francois.bis...@canterbury.ac.nz> wrote:
>
> > On 18/12/2015, at 19:08, William Stein >
> wrote:
> >
> > - The biggie is of course switching from Python 2.x to Python 3.x.
> That may be pushing it for the
Hi,
Does anybody want to migrate wiki.sagemath.org to github?
-- William
-- Forwarded message --
From: jhonrubia6
Date: Thu, Dec 17, 2015 at 5:54 AM
Subject: [sage-devel] how to publish new quickref card in spanish
To: sage-devel
Hi,
I translated the quickref card to spanis
This seems like a good thread to think about the nontrivial backwards
incompatible changes that are in our future:
- The biggie is of course switching from Python 2.x to Python 3.x.
- Making Jupyter notebook the default.
- ???
William
On Thu, Dec 17, 2015 at 10:05 PM, Andrey Novoseltsev
+1 the version!
On Thursday, December 17, 2015, Francois Bissey <
francois.bis...@canterbury.ac.nz> wrote:
> +1
> > On 18/12/2015, at 12:42, Volker Braun > wrote:
> >
> > Should we switch to 7.0 after 6.10?
> >
> > http://trac.sagemath.org/ticket/19641 [remove (DY)LD_LIBRARY_PATH]
> requires eve
On Sat, Dec 12, 2015 at 1:40 PM, Emmanuel Charpentier
wrote:
> Dear list,
>
> Our current R interface uses pexpect. It is functional, at least from the
> command line.
>
> However, the "%r" magic, working from the command line and the Sage
> notebook, cannot be (usefully) used in the Jupyter noteb
On Fri, Dec 11, 2015 at 8:51 AM, Volker Braun wrote:
> On Friday, December 11, 2015 at 5:13:18 PM UTC+1, William wrote:
>>
>> 3*(z+1)*(z-i)ˆ2*(z-1+i)ˆ3
>> won't quite work. Instead do
>
>
> On the plus side its somewhat unlikely that one would enter U+02C6
> accidentally instead of ^
I did th
On Fri, Dec 11, 2015 at 7:29 AM, Dima Pasechnik wrote:
>
>
> On Friday, 11 December 2015 14:09:03 UTC, kcrisman wrote:
>>
>> http://www.ams.org/notices/201511/rnoti-p1350.pdf
>>
>> Especially thanks to Robert Bradshaw for first introducing this in
>> http://trac.sagemath.org/ticket/5606 !
That's
https://youtu.be/ffPbVQa0WQs
--
Best Regards,
William
Found/CEO of SageMath, Inc.
Professor of Mathematics
--
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 sag
Installing music21 is trivial -- just use "pip install music21". I
tried with SMC:
https://cloud.sagemath.com/projects/4a5f0542-5873-4eed-a85c-a18c706e8bcd/files/support/2015-12-08-141248-music21.sagews
However, to display music, one would need a way to get a png or svg
image written to a file;
On Tue, Dec 8, 2015 at 12:38 PM, Ursula Whitcher wrote:
> In Sage's contour plots, the default colors shade from black to white. This
> applies to both the shades used to fill and the actual color of the contour
> lines. If you turn off the fill color, the highest contour will be
> white-on-whit
On Thu, Dec 3, 2015 at 12:44 AM, Marc Mezzarobba wrote:
> William Stein wrote:
>> I think we should revisit our decision -- from long ago -- to make
>> domain:complex the default for Sage. Paul Zimmerman argued for it a
>> long time ago. However, my impression is that sy
Hi,
I think we should revisit our decision -- from long ago -- to make
domain:complex the default for Sage. Paul Zimmerman argued for it a
long time ago. However, my impression is that symbolic integration is
used mainly by people who are doing purely real-variable undergraduate
education, and f
On Sunday, November 22, 2015, Mark Bell wrote:
> Thank you for tracking this down so quickly and for already submitting a
> correction. If I am understanding your response correctly then I think I
> need to just hope that trac 14243 is accepted and then wait for the next
> version of sage that in
On Fri, Nov 20, 2015 at 12:44 PM, Mark Bell wrote:
> I've just upgraded to Sage 6.9 from 6.8. I have a large number of packages
> that I've installed by using:
> python setup.py install --user
> so they have been placed in /home/me/.local/lib/python2.7/site-packages/...
>
> Previously Sage would
On Thu, Nov 19, 2015 at 10:34 AM, Stefan wrote:
> On Wednesday, November 18, 2015 at 2:12:43 PM UTC-6, Nathann Cohen wrote:
>>
>> Hello Jori,
>>
>> We should of course state such things as clearly as possible in the
>> doc, that's an mandatory step.
>>
>> In some cases, however, the users call fun
https://vimeo.com/146207495
--
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 th
On Friday, November 13, 2015, Sébastien Labbé wrote:
> Is this a feature or a bug?
>
>
Feature - the calls all happen at once starting with the same state of sage
including the random state.
>
> sage: @parallel
> : def f(a):
> : return a+random()
> :
> sage: [v for _,v in f(ran
On Friday, November 6, 2015, John H Palmieri wrote:
> At http://trac.sagemath.org/ticket/19503, we have a branch which
> implements the omission of 'TESTS:' blocks in docstrings when you do 'foo?'
> (and optionally, but this is not the default behavior, it can omit them in
> the reference manual)
Does this mean computers aren't constantly getting faster anymore? l miss
the 90s... :-)
On Wednesday, November 4, 2015, kcrisman wrote:
>
>> That's actually a great idea!
>>
>> Although, to simplify parsing, I would only allow seconds with a syntax
>> similar to optional:
>>
>> # long time: 300
On Tue, Nov 3, 2015 at 9:50 AM, Jean-Baptiste Priez
wrote:
> Hello tikz lovers!!
>
> I create a(nother) ticket to use tikz picture with jupiter (
> http://trac.sagemath.org/ticket/19515).
> (I don't understand the reason of the ticket #18116 and it doesn't work
> on my sage 6.9... )
>
>
For what
On Tue, Nov 3, 2015 at 5:53 AM, kcrisman wrote:
>
> Hi Sage Developers,
>>
>> Who is interested in a Sage Days adjacent to the Joint Math Meetings
>> in January 2016 in Seattle? I have funding for US citizens. And I
>> live in Seattle.
>>
>>
> Just for clarification, were you thinking before (s
Hi Sage Developers,
Who is interested in a Sage Days adjacent to the Joint Math Meetings
in January 2016 in Seattle? I have funding for US citizens. And I
live in Seattle.
-- William
--
William (http://wstein.org)
--
You received this message because you are subscribed to the Google Groups
On Thu, Oct 29, 2015 at 11:03 AM, Nathann Cohen wrote:
> [...] come show us that you still know how to write python code.
Flame bait.
https://groups.google.com/forum/#!forum/sage-flame
http://wiki.sagemath.org/CodeOfConduct
--
William (http://wstein.org)
--
You received this message because
On Thu, Oct 29, 2015 at 10:42 AM, Nathann Cohen wrote:
>> That's what
>>
>> # long time
>>
>> is supposed to be for.
>
> I don't think so. You wouldn't want to see a doctest take one hour to
> run, even if it is flagged with 'long time'. I don't know about you,
> but I run 'long' doctests seve
On Thu, Oct 29, 2015 at 10:22 AM, Jori Mäntysalo wrote:
> On Thu, 29 Oct 2015, John H Palmieri wrote:
>
>> Should it hide "TESTS" blocks? Same questions when you ask for interactive
>> help via "foo?".
>
>
> foo??? should do what foo?? does now, i.e. show the source. foo?? should do
> what foo? do
On Thu, Oct 29, 2015 at 10:12 AM, Nathann Cohen wrote:
>> Yep! That's why I called it "not tested". In my opinion, the only
>> reasonable change would be
>>
>> " # not tested" > " # broken"
>>
>> That would probably create an even more accurate impression.
>
> I flagged many doctests
On Thu, Oct 29, 2015 at 5:30 AM, Jeroen Demeyer wrote:
> On 2015-10-29 13:23, Samuel Lelièvre wrote:
>>
>> However, to the non-expert eye, such as a non-developer user
>> reading the documentation, seeing "# not tested" produces the
>> impression that this piece of code is not guaranteed to work,
On Thu, Oct 29, 2015 at 4:57 AM, Volker Braun wrote:
> On Thursday, October 29, 2015 at 12:44:23 PM UTC+1, Nathann Cohen wrote:
>>
>> We need this at least in the case of a non-gpl-compatible package.
>
>
> No. The default should be to error out, and a command line switch like
> "--accept-license=
On Wednesday, October 28, 2015, Volker Braun wrote:
> zeromq is a standard package; which command are you running?
>
>
sage -I csdp
> Command-line tools shouldn't ask stupid questions, this totally defeats
> the use of the commandline UI as building blocks for writing scripts. I
> said that bef
How do I make it so that "sage -i " doesn't
interactively ask this question?
=== WARNING ===
│ZEROMQ=zeromq-4.0.5
You are about to download and install an experimental package.
This probably won't work at all for yo
On Sun, Oct 25, 2015 at 9:54 AM, Volker Braun wrote:
> On Sunday, October 25, 2015 at 5:49:45 PM UTC+1, William wrote:
>>
>> At least openssl very recently changed their license to be
>> GPL-compatible, so it is legal to include with Sage... finally.
>
>
> No they didn't; They announced their inte
On Sun, Oct 25, 2015 at 3:11 AM, Volker Braun wrote:
> On Sunday, October 25, 2015 at 10:13:39 AM UTC+1, François wrote:
>>
>> That explain why I had to change the configuration for git.
>> No openssl headers, I have heard they are going to switch to libressl,
>
>
> Not sure about that, they proba
Hi Nathann,
What problem are you solving by using immutable matrices/vectors? Why
is anything immutable for what you are doing?
For reference, I explained above the actual problem which motivated my
writing immutable matrices/vectors for Sage in the first place.
-- William
On Fri, Oct 23, 201
On Fri, Oct 23, 2015 at 6:04 AM, William Stein wrote:
> On Fri, Oct 23, 2015 at 5:04 AM, Nathann Cohen
> wrote:
>> Hello everybody,
>>
>> When calling .row() on an immutable matrix, one gets mutable vectors.
>> I can easily avoid it for the code I am writing, bu
On Fri, Oct 23, 2015 at 5:04 AM, Nathann Cohen wrote:
> Hello everybody,
>
> When calling .row() on an immutable matrix, one gets mutable vectors.
> I can easily avoid it for the code I am writing, but do you think we
> should do something about it?
m.row() returns a new (copy) of the row of the
On Thu, Oct 22, 2015 at 10:19 AM, Ralf Hemmecke wrote:
> Hello,
>
> I'd like to convert some simple .sws file into Ipython notebooks
> (.ipynb). Searching for a converter led me to
>
> https://github.com/anteprandium/sagews2ipynb
>
> but unfortunately the README.md says nothing about how to actual
On Wed, Oct 21, 2015 at 12:19 PM, Christian Nassau
wrote:
> On 21.10.2015 21:11, John H Palmieri wrote:
>>
>> The latest beta version of Sage should build on OS X 10.11. It has a
>> serious limitation: you can't move the installation once it has been built.
>> I don't know if anyone is working on
Fantastic!!
On Wed, Oct 21, 2015 at 12:11 PM, John H Palmieri
wrote:
> As you said in another thread, look at the big red message at the top of
>
> http://www.sagemath.org/download-mac.html
>
> which points to
>
> http://trac.sagemath.org/ticket/19370
>
> The latest beta version of Sage shoul
Hi,
I'm curious. Is *anybody* reading this actually actively working on
(or planning to work on) making it Sage runs on the current version of
OS X ("El Capitan")?
With the last OS X version, Sage got ported to work on it by me buying
Andrew Ohana [1] a nice laptop running on OS X on the conditi
On Tue, Oct 20, 2015 at 12:08 PM, wrote:
> But it's working otherwise! Meaning that if I don't pass to the cuspidal
> subspace, it appears to be correctly computing slopes. And it is so much
> faster than working over Q(zeta_11)...
Well that's interesting! Other people have worked a lot on th
http://www.computingreviews.com/review/review_review.cfm?listname=highlight&review_id=143718
--
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
On Tue, Oct 20, 2015 at 11:33 AM, wrote:
> The following code crashes and asks me to report this as a bug:
>
> sage: Qp = pAdicField(11)
>
> sage: G = DirichletGroup(11,Qp)
>
> sage: omega = G.0
>
> sage: M = ModularSymbols(omega^2,2)
For what it is worth, I'm extremely surprised that the Modula
On Thursday, October 15, 2015, Bill Page wrote:
> The version of pexpect with the new option is still a branch called
>
> https://github.com/pexpect/pexpect/tree/superfluous-sleep
>
> I think they are waiting for us to say that it works with Sage.
>
Make sure to test the latency/speed/overhead u
On Sat, Oct 10, 2015 at 10:47 AM, Dima Pasechnik wrote:
> some thoughts for inclusion:
>
> People working in combinatorial enumeration used to swear by nauty, there was
> no alternative, basically.
>
> It is a very solid plain C code, working on all sorts of platforms.
Excellent. I skimmed some
On Sat, Oct 10, 2015 at 12:50 AM, Jeroen Demeyer wrote:
> On 2015-10-09 20:50, Dima Pasechnik wrote:
>>
>> Good to go? I suppose we need a formal vote to make the package
>> standard, right?
>
>
> Of course. It's not clear to me that it should be standard, by the way...
Indeed -- there are questi
On Fri, Oct 9, 2015 at 10:36 AM, Volker Braun wrote:
> On Friday, October 9, 2015 at 7:08:19 PM UTC+2, William wrote:
>>
>> the copyright notice above very explicitly states that "all
>> rights reserved"
>
>
> As you said, thats a no-op:
> http://www.iusmentis.com/copyright/allrightsreserved/
>
>
On Fri, Oct 9, 2015 at 9:19 AM, Dima Pasechnik wrote:
>
>
> On Friday, 9 October 2015 07:44:55 UTC-7, Volker Braun wrote:
>>
>> Looks great; The two restrictions
>>
>> * * You must not remove this section of the text, containing author
>> *
>> * attribution, copyright notice, and legal discl
>>> On cygwin32 the result was decent.
>>
>>
>>
>> How many people *use* it?
>
> Not even me!
> I guess it misses advertising, proper packaging, proper testing, proper
> continuous integration, ...
The last few times I spent months on Windows porting, the net result
of using Cygwin was -- in pract
On Thursday, October 8, 2015, Jean-Pierre Flori wrote:
>
>
> On Thursday, October 8, 2015 at 9:10:17 PM UTC+2, William wrote:
>>
>>
>>
>> On Thursday, October 8, 2015, David Joyner wrote:
>>
>>> On Thu, Oct 8, 2015 at 2:58 PM, William Stein wrote
On Thursday, October 8, 2015, David Joyner wrote:
> On Thu, Oct 8, 2015 at 2:58 PM, William Stein > wrote:
> >
> >
> > On Thursday, October 8, 2015, David Joyner > wrote:
> >>
> >> Before this thread drops off the radar, I have a question. How har
gt; > I see that there is a list of packages here:
> >
> > http://sourceforge.net/p/msys2/wiki/Packages/
> >
> >>
> >>
> >> Generally speaking, mingw-w64 is a really good option for C/C++
> >> development on Windows. The biggest problem is the pro
The other part of the copyright notice says "you must document any
changes". That's presumably GPL incompatible too though it is very
vague
On Thursday, October 8, 2015, Dima Pasechnik wrote:
> ok, so we can make nauty standard package!
> -- Forwarded message --
> From: "Dim
e effect of disrupting Sage's current
> build process. Disabling system integrity protection may allow you to
> build Sage, but it also disables a security feature of your operating
> system.
> >
> > David
> >
> > On Wed, Oct 7, 2015 at 12:52 PM, William Stein
On Wednesday, October 7, 2015, David Roe wrote:
> I'm confused by that as well, but apparently some people have succeeded at
> building Sage after making this change. Maybe there are other ways that
> disabling SIP affects Sage's build. I was trying to describe the reasons
> that users might he
t; made this change to make it more difficult for malware to affect the
> operating system, but it has the side effect of disrupting Sage's current
> build process. Disabling system integrity protection may allow you to
> build Sage, but it also disables a security feature of your op
orts.
I think we should mention it.
>
> On Wed, Oct 7, 2015 at 12:38 PM, William Stein > wrote:
>
>> Hi,
>>
>> We need to post a statement on the Sagemath.org website about the El
>> Capitan os x 10.11 situation, since I'm getting (or will be getting)
>
Hi,
We need to post a statement on the Sagemath.org website about the El
Capitan os x 10.11 situation, since I'm getting (or will be getting)
emails "left and right" from people freaking out about this.
Here's one answer -- how could it be reworded to be right?
---
Hi,
As far as I know, there is
On Tue, Oct 6, 2015 at 11:34 AM, Alexander Tchekhovskoy
wrote:
> I find that the LaTeX editor at SageMath randomly applies some of the
> changes more than once, sometimes in weird ways. For instance, I type
>
> \usepackage{bm}
>
> and it stays for a while. But some time later, I get
>
> \usepacka
On Sunday, October 4, 2015, Jori Mäntysalo wrote:
> On Sun, 4 Oct 2015, William Stein wrote:
>
> If I am right, there is no EASY parallel functions in Sage.
>>>
>>
>> Type
>>
>> parallel?
>>
>> in Sage for a simple but very useful parallel
On Sun, Oct 4, 2015 at 10:29 PM, Jori Mäntysalo wrote:
> Just a stupid side-question:
>
> On Sun, 4 Oct 2015, Victor Shoup wrote:
>
>> Also, now that NTL is threadsafe, I'm looking at making some of the
>> low-level routines thread enhanced.
>
>
>> For up to 4 threads, I get close to linear speedu
On Sat, Oct 3, 2015 at 8:35 AM, Thierry Dumont
wrote:
> Hello,
>
> I am preparing a talk I will give to a group of engineers, about
> "Notebooks". I mean web technology based notebooks (not java, qt or
> something else, but notebooks which use your web browser); so I will speak
> about Sage Notebo
Hi,
In the meantime, I think ASAP on the OS X binary download page we should:
(1) move the "Usage:" message to the top (it's *hidden* at the bottom
where nobody will ever see it).
(2) add that there is no way to run Sage on 10.11 except to either
disable Apple's system integrity protection, or
On Thu, Oct 1, 2015 at 12:35 PM, Nathann Cohen wrote:
>> This message seems like flamebait [1],
>
> That's because I took your proposal of hiding bugs under the carpet
> and *not tell the users* as an insult against scientific honesty. The
> kind of honesty that I would expect if I were a user of
On Thu, Oct 1, 2015 at 12:00 PM, Bill Page wrote:
> On 1 October 2015 at 14:23, William Stein wrote:
>> ...
>> One other impression you have is that categories were just bolted on
>> by combinatorics people at the end. However, David Kohel and I
>> actually imp
On Thu, Oct 1, 2015 at 11:27 AM, Nathann Cohen wrote:
>[...]
> Professionals. That's a joke.
This message seems like flamebait [1], hence probably does not belong
on this list, and belongs on sage-flame [2] instead. I think it is
best if people direct any responses to sage-flame [2] rather than
On Thu, Oct 1, 2015 at 11:00 AM, Bill Page wrote:
> On 1 October 2015 at 13:07, William Stein wrote:
>> On Thu, Oct 1, 2015 at 9:38 AM, Bill Page wrote:
>>> [Changed thread subject from: Sources of funding - perhaps computer
>>> manufacturers? ]
>>>
&g
On Thu, Oct 1, 2015 at 9:38 AM, Bill Page wrote:
> [Changed thread subject from: Sources of funding - perhaps computer
> manufacturers? ]
>
> What I find hard to swallow is the peculiar mix of "parent",
> "category", and Python data types (class system and inheritance). In
> spite of the available
On Thu, Oct 1, 2015 at 8:07 AM, Travis Scrimshaw wrote:
>
>>>
>>> Thanks Volker for writing an e-mail before the clash.
>>>
>>> To my mind, it is a complete nonsense to merge this stopgap in a rc0. We
>>> would have time to fix the hash issues along a development cycle starting
>>> from an early b
On Thursday, October 1, 2015, Vincent Delecroix <20100.delecr...@gmail.com>
wrote:
> Hello,
>
> Thanks Volker for writing an e-mail before the clash.
>
> To my mind, it is a complete nonsense to merge this stopgap in a rc0. We
> would have time to fix the hash issues along a development cycle star
On Wed, Sep 30, 2015 at 3:12 PM, Michael Orlitzky wrote:
> On 09/30/2015 02:25 PM, William Stein wrote:
>> However, from 2011 to now, year-on-year growth is
>> slightly less than 0%. It was maybe -10% from 2013 to 2014.
>
> There are probably a lot of people like me who
On Tuesday, September 29, 2015, Bill Page
wrote:
> On 29 September 2015 at 19:41, Dima Pasechnik > wrote:
> >
> > cryptographers (some of them can certainly qualify as engineers) use
> Magma a lot.
> >
>
> OK. Would you say that Sage is a viable alternative for them?
>
>
No. Going into details
On Mon, Sep 28, 2015 at 10:25 AM, Francesco Biscani
wrote:
>> Exactly. And also the mission statement: viable alternative to the Ma's -
>> that is tricky!
>
>
> I have always felt a tad confused and mislead by this statement.
>
> As someone who has interacted over the years with physicists and en
On Monday, September 28, 2015, kcrisman wrote:
>
>>> The much-maligned controversial statement (Sage doomed) worth reviewing?
>>>
>>
>> Though I think the growth/survival of the SageMath project is in serious
>> jeopardy due to lack of funding, I for one am definitely not giving up.
>> The activi
On Sun, Sep 27, 2015 at 11:39 PM, Jori Mäntysalo wrote:
> On Fri, 25 Sep 2015, William Stein wrote:
>
>>>> 1) Should we include symbols in docstrings? I.e. add \otimes to
>>>> ordinal_product() of posets, as used in Enumerative combinatorics?
>
>
>>&g
On Sunday, September 27, 2015, Nathann Cohen
wrote:
> > Though I think the growth/survival of the SageMath project is in serious
> > jeopardy due to lack of funding, I for one am definitely not giving up.
> The
> > activity is not doomed. If anything the only thing to do is try much
> > harder,
On Sunday, September 27, 2015, rjf wrote:
> Unless you can argue that having a Sage port will increase sales, then the
> marketing types
> won't care.
>
> Unless you can argue that giving money to a university is a better way to
> pursue
> a research topic of interest, then the research types wou
On Sun, Sep 27, 2015 at 3:53 AM, Samuel Lelievre
wrote:
>
>
> 2015-09-26 09:53:38 UTC+2, Ralf Stephan:
>>>
>>> The question is if we should call it is().
>>
>>
>> Impossible because it is a Python keyword.
>> So, lacking a better proposal I'll stick to holds()
>
>
> What about the following, where
On Fri, Sep 25, 2015 at 9:33 AM, Eric Gourgoulhon
wrote:
>
>
> Le vendredi 25 septembre 2015 16:47:23 UTC+2, William a écrit :
>>
>>
>> > we may assume that most users understand LaTeX.
>>
>> This is a questionable assumption. Numerical most users of Sage are
>> undergraduates, and most undergrad
801 - 900 of 9552 matches
Mail list logo