On this URL:
http://boxen.math.washington.edu/home/sagemath/sage-mirror//devel/
the README says:
Dear Release-Manager, please keep this directory's footprint
small, because it goes around the world. Latest tarball only ;)
It's got a full history from sage-6.4.rc2, though. Would it be possible
IMHO always assume constructive unless otherwise noted if you do things on
the computer. You can pick elements of sets, elements of two sets (or other
structure) can actually be distinguished, etc.
Why not have an Iterable() category for everything with __iter__? There is
no need to restrict ou
Le 11/03/2015 17:53, William Stein a écrit :
1. Setup/write an editorial notification system to encourage the
reviewing of tickets, similar to how every journal on the planet has
an automated system for ensuring papers get reviewed, seeing the
status of outstanding papers, etc. Maybe we coul
>
> 1. Setup/write an editorial notification system to encourage the
> reviewing of tickets, similar to how every journal on the planet has
> an automated system for ensuring papers get reviewed, seeing the
> status of outstanding papers, etc. Maybe we could even just use an
> existing
On Wed, Mar 11, 2015 at 9:44 AM, Julien Puydt wrote:
> Hi,
>
> I was thinking it would be interesting to have a look at the tickets needing
> review, so I browsed the list... and saw one of them was waiting since about
> three years (sic). I put it to needs_info because obviously everything in it
Dear Sage developers,
This e-mail is to request some feedback for:
#17160: Finitely generated axiom for (mutiplicative) magmas, semigroups,
monoids, groups
Context
---
Currently in Sage, any finite semigroup (set with a multiplication) is
automatically assumed to be a finite en
Hi,
I was thinking it would be interesting to have a look at the tickets
needing review, so I browsed the list... and saw one of them was waiting
since about three years (sic). I put it to needs_info because obviously
everything in it is so clearly outdated. But then there are also many
who a
Marc Mezzarobba wrote:
> There are *tons* of modules missing from the reference manual, some
> obsolete, some still in pre-sphinx style or with rst syntax errors,
> some whose user documentation in fact appears in another module, and
> many apparently just forgotten.
>
> A few weeks ago I started
Hello,
> I was not aware of the hypergraph definition until I encountered this code.
> I would have called these "matchings" in hypergraphs which seems to me the
> dominant terms of these things (from a quick search) in the literature.
An example there:
http://en.wikipedia.org/wiki/Packing_in_a_h
On Wednesday, 11 March 2015 02:51:10 UTC-4, Nathann Cohen wrote:
>
> Hello !
>
> > One idea is for packing to have some kind of trivial default ($t=0$,
> > $\lambda=1$) for incidence structure, make a child class called
> hypergraphs
> > which has defaults $t=1$, $\lambda=1$ and put d
10 matches
Mail list logo
