On Thu, Apr 2, 2015 at 3:11 PM, William Stein wrote:
> The feeling is very mutual. My dream would be that SMI = (SageMath,
> Inc.) is very successful and can be one of JH's industry partners, and
> that SMI can financially (and otherwise) help to support JH
> development.
>
That would be awesom
I didn't even know that that was possible, yet another way to plot stuff
that is not accessible via plot()...
There is no ticket for refactoring view() into something consistent except
for the awfully vague #18033. IMHO the finite state machines should go with
the program and
* Have plot() pro
On Thu, Apr 2, 2015 at 3:00 PM, Fernando Perez wrote:
>
> On Wed, Apr 1, 2015 at 9:54 PM, William Stein wrote:
>>
>> If somebody from JH decides to explain how every point above is
>> slightly wrong, that would be nice, since I can't imagine that they
>> aren't wrong!
>
>
> Actually, I don't see
On Wed, Apr 1, 2015 at 9:54 PM, William Stein wrote:
> If somebody from JH decides to explain how every point above is
> slightly wrong, that would be nice, since I can't imagine that they
> aren't wrong!
>
Actually, I don't see any major errors in there :)
Just to add some detail, the basic de
I would love to see the knot theory code merged, but right now i think it
needs more than someone looking at it and saying that it is ok. It needs
someone to look at it and saying which parts have to be fixed or improved.
Sadly, i don't think it is ready for merging yet.
That said, I know of se
On Thu, Apr 2, 2015 at 11:45 AM, kcrisman wrote:
>>
>> > There a new function sage.misc.superseded.experimental is proposed,
>> > which acts like a deprecation, but giving a FutureWarning stating that
>> > this code/module is experimental (and a trac ticket number as
>> > reference).
>> >
>> > You
The command
view(transducers.GrayCode())
produces tikz-output which can be show by latex. In sagenb this was
shown directly inside the notebook, while in the ipython-notebook this
opens a new pdf with the picture.
It would be nice to have this shown in the ipynb...
Comments? Guesses when this w
>
>
> > There a new function sage.misc.superseded.experimental is proposed,
> > which acts like a deprecation, but giving a FutureWarning stating that
> > this code/module is experimental (and a trac ticket number as
> reference).
> >
> > You can include this in functions or in __init__ of cl
Am 2015-04-02 um 13:25 schrieb Daniel Krenn:
> Am 2015-04-02 um 13:18 schrieb Thierry:
>> Should we offer a kind of test-sage ? Should we propose a kind of
>> proprecation warning that says "This code is very new and its design is not
>> foolproof. Its design might change.".
>
> This could look li
On Thu, Apr 2, 2015 at 9:06 AM, Bill Hart wrote:
>
>
> On 2 April 2015 at 17:31, William Stein wrote:
>>
>> On Thu, Apr 2, 2015 at 12:09 AM, Bill Hart
>> wrote:
>> >
>> >
>> > On 31 March 2015 at 15:18, William Stein wrote:
>> >
>> >
>> >>
>> >>
>> >> All that said, Julia seems really exciting
>
>
The discussion about programming languages for X is largely a rehash of
discussions that are inherently
non-convergent .
The language syntax and semantics tends to be pointless from a particular
advanced standpoint,
which is that if you want to design a language to do some task T, you ca
On 2 April 2015 at 17:31, William Stein wrote:
> On Thu, Apr 2, 2015 at 12:09 AM, Bill Hart
> wrote:
> >
> >
> > On 31 March 2015 at 15:18, William Stein wrote:
> >
> >
> >>
> >>
> >> All that said, Julia seems really exciting. If people write major
> >> packages of functionality in Julia tha
On Thu, Apr 2, 2015 at 12:09 AM, Bill Hart wrote:
>
>
> On 31 March 2015 at 15:18, William Stein wrote:
>
>
>>
>>
>> All that said, Julia seems really exciting. If people write major
>> packages of functionality in Julia that people doing mathematics
>> really need, and is better than what is a
Its of course a quite difficult machine learning exercise to find the
optimal match from tracebacks to hints that are helpful to a beginner.
Though deciding based on a regex on the input and traceback is probably a
good start.
On Thursday, April 2, 2015 at 4:16:39 PM UTC+2, William wrote:
>
On Thu, Apr 2, 2015 at 7:57 AM, Jori Mantysalo wrote:
> On Thu, 2 Apr 2015, William Stein wrote:
>
We could translate en dash into hypen on the commandline to avoid that
surprise...
>
>
>> Another idea would be to do something only if an exception is actually
>> raised. I.e., if a user
On Thu, Apr 2, 2015 at 7:52 AM, kcrisman wrote:
>>
>> A large amount of common help/support questions could have the answers
>> automated and built in. This would be 100% optional, triggered only
>> on interactive errors, and not change Sage's library in any way
>> (except possibly with the addi
On Thu, 2 Apr 2015, William Stein wrote:
We could translate en dash into hypen on the commandline to avoid that
surprise...
Another idea would be to do something only if an exception is actually
raised. I.e., if a user interactively runs some block of input (in a
notebook, command line, wha
On Thu, Apr 2, 2015 at 4:25 AM, Daniel Krenn wrote:
> Am 2015-04-02 um 13:18 schrieb Thierry:
>> Should we offer a kind of test-sage ? Should we propose a kind of
>> proprecation warning that says "This code is very new and its design is not
>> foolproof. Its design might change.".
>
> This could
>
>
> A large amount of common help/support questions could have the answers
> automated and built in. This would be 100% optional, triggered only
> on interactive errors, and not change Sage's library in any way
> (except possibly with the addition of this).
>
>
This is all an intriguing id
On OSX we don't build our own sqlite as that tends to conflict with the
OSX-provided version.
On Thursday, April 2, 2015 at 4:36:03 PM UTC+2, David Einstein wrote:
>
> I'm beginning to understand what is wrong. A couple of years ago I must
> have overwritten the default python 2.7 with someth
I'm beginning to understand what is wrong. A couple of years ago I must
have overwritten the default python 2.7 with something newer (I have vague
recollections of needing it to get scipy working). A stupid thing to do,
and I should know better.
Now _sqlite3 is in
/System/Library/Framework
If I recall correctly, Kyle Kelly (who works at Rackspace) has worked a
lot with setting up JupyterHub with Docker containers. That's how
http://tmpnb.org works, for example. He would be one of the best people
to contact about how to set something like that up.
Thanks,
Jason
On 4/2/15 02:
On Thu, Apr 2, 2015 at 7:02 AM, kcrisman wrote:
>>
>> We could translate en dash into hypen on the commandline to avoid that
>> surprise...
>
>
> Interesting idea, though what if it was intended in something, such as a
> plot legend?
>
Another idea would be to do something only if an exception is
If a group of people want to work on an isolated feature they could always
fork Sage and review each other's stuff as they go along. The only downside
is that they can't use use our trac to split it into subtasks as our git
viewer would always show the entire branch, not the subtask branch. But
Am 2015-04-02 um 13:18 schrieb Thierry:
> Should we offer a kind of test-sage ? Should we propose a kind of
> proprecation warning that says "This code is very new and its design is not
> foolproof. Its design might change.".
This could look like this:
public/misc/experimental_code_warning
The
Hi,
during the talk about coding theory rewrite at sd66, we were discussing
about the groups of people starting to develop some code for Sage and
waiting to have something ready and clean to start submitting (e.g.
matroids, finite state machines, manifolds), which could lead to a
patchbomb that wi
On Sunday, 29 March 2015 19:39:04 UTC+1, William wrote:
>
> On Sun, Mar 29, 2015 at 11:20 AM, Dima Pasechnik > wrote:
> > On 2015-03-29, William Stein > wrote:
> >> On Fri, Mar 27, 2015 at 1:14 AM, Dima Pasechnik > wrote:
> >>>
> >>>
> >>> On Thursday, 26 March 2015 19:48:37 UTC, Jeroen De
On Sunday, March 29, 2015 at 5:23:53 PM UTC+2, jplab wrote:
>
> What do you think?
>
Hi, sorry to spoil the party. I'm strongly against changing the logo in
such a substantial way. I'm happy with slight adoptions or creating
"doodles" (temporary modifications with a specific theme) but not a
On Thursday, April 2, 2015 at 7:32:12 AM UTC+2, Jori Mantysalo wrote:
>
> if f(x):
Python calls the magic __nonzero__ method (renamed to __bool__ in Python 3)
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and s
Very rougly, JH is right now an authenticating reverse proxy. Every user
gets basically a single-user notebook running in a separate process
(possibly on a different machine). The upside is that it is simple and if
you can run a single-user notebook then you can also run JH, and it scales
much
On 31 March 2015 at 15:18, William Stein wrote:
>
>
> All that said, Julia seems really exciting. If people write major
> packages of functionality in Julia that people doing mathematics
> really need, and is better than what is already in Sage, we could
> consider adding Julia to Sage... S
31 matches
Mail list logo
