Hello,
> Really?! Are you saying that looking at standard/*/ is more inconvenient
> than looking at */* and checking that a file there says standard (or have a
> file
> named standard) ?
It may not be more convenient indeed if you only want to remember the
'status' (standard/optional/experimental
On Wednesday, 13 May 2015 22:26:25 UTC+1, leif wrote:
>
> Dima Pasechnik wrote:
> > On Wednesday, 13 May 2015 20:55:16 UTC+1, leif wrote:
> >
> > Dima Pasechnik wrote:
> > > On Wednesday, 13 May 2015 17:55:17 UTC+1, leif wrote:
> > >
> > > Volker Braun wrote:
> > >
John Cremona wrote:
> Is anyone planning to update the version of Singular used by Sage?
http://trac.sagemath.org/ticket/17254
> We appear to use 3.1.7 which is not listed at
> http://www.singular.uni-kl.de/index.php/news.html but 3.1.6 was
> released in 2012, there were two releases in 2014 an
On 05/14/15 09:00, John Cremona wrote:
Is anyone planning to update the version of Singular used by Sage?
We appear to use 3.1.7 which is not listed at
http://www.singular.uni-kl.de/index.php/news.html but 3.1.6 was
released in 2012, there were two releases in 2014 and the current one
is 4.0.2 r
Dima Pasechnik wrote:
> On Wednesday, 13 May 2015 20:55:16 UTC+1, leif wrote:
>
> Dima Pasechnik wrote:
> > On Wednesday, 13 May 2015 17:55:17 UTC+1, leif wrote:
> >
> > Volker Braun wrote:
> > > IMHO:
> > >
> > > * The package type (standard/optional/ex
Is anyone planning to update the version of Singular used by Sage?
We appear to use 3.1.7 which is not listed at
http://www.singular.uni-kl.de/index.php/news.html but 3.1.6 was
released in 2012, there were two releases in 2014 and the current one
is 4.0.2 released on 2015-03-05.
I'm asking becaus
On Wednesday, 13 May 2015 20:55:16 UTC+1, leif wrote:
>
> Dima Pasechnik wrote:
> > On Wednesday, 13 May 2015 17:55:17 UTC+1, leif wrote:
> >
> > Volker Braun wrote:
> > > IMHO:
> > >
> > > * The package type (standard/optional/experimental) should be in a
> > file
> >
On Wed, May 13, 2015 at 10:02 PM, Johannes wrote:
> What kind of issues? And what kind of help? Maybe Ican spend some time on it
> too.
Thank you for your interest! :-)
The list off issues is here:
https://github.com/sagemath/website/issues
... where I think most of them are either "invalid" or
On 13.05.2015 21:36, Harald Schilly wrote:
I'm happy if there were a few more helping hands for the website.
There are several technical and financial constraints (besides the
time I'm spending with it), which might shed some light on the reasons
why some things do happen.
What kind of issues
Dima Pasechnik wrote:
> On Wednesday, 13 May 2015 17:55:17 UTC+1, leif wrote:
>
> Volker Braun wrote:
> > IMHO:
> >
> > * The package type (standard/optional/experimental) should be in a
> file
> > inside the package directory
>
> hmm...
>
> rather, how about SAGEROOT/bui
> I'm happy if there were a few more helping hands for the website.
Maybe I could help, and probably others too. Could you tell us what
you would need hands for, if what you have in mind are frequent tasks?
I would not mind dealing with changelogs, and possibly with packages
too. I was digging ar
Harald Schilly wrote:
> On Wed, May 13, 2015 at 9:17 PM, Nathann Cohen
> wrote:
>> What about all links from other pages to our doc? All broken?
>
> Do you have a list of all links? Me neither.
>
> It's possible to add a redirection page for the /doc/ page, that could help.
Sure. Currently th
On Wed, May 13, 2015 at 9:29 PM, Nathann Cohen wrote:
> As you just came and broke everything at once without asking ...
I'm happy if there were a few more helping hands for the website.
There are several technical and financial constraints (besides the
time I'm spending with it), which might she
> Do you have a list of all links? Me neither.
To be honest I do not care much, I was merely asking out of curiosity.
These days I write many 'doc' patches, and every time I change a
page's name the reviewers go ballistic and tell me about "the links
that I break". The fashion seems to be toward a
On Wed, May 13, 2015 at 9:17 PM, Nathann Cohen wrote:
> What about all links from other pages to our doc? All broken?
Do you have a list of all links? Me neither.
It's possible to add a redirection page for the /doc/ page, that could help.
-- harald
--
You received this message because you ar
> The documentation is at http://doc.sagemath.org/ … that previous
> location was only possible because a lot of things could be mashed
> together via symlinks.
What about all links from other pages to our doc? All broken?
Nathann
--
You received this message because you are subscribed to the G
On Wed, May 13, 2015 at 8:12 PM, kcrisman wrote:
> If you or someone else is messing around a bit with the doc, note that
> currently
>
> http://www.sagemath.org/doc/
The documentation is at http://doc.sagemath.org/ … that previous
location was only possible because a lot of things could be mashe
On Wednesday, 13 May 2015 17:55:17 UTC+1, leif wrote:
>
> Volker Braun wrote:
> > IMHO:
> >
> > * The package type (standard/optional/experimental) should be in a file
> > inside the package directory
>
hmm...
rather, how about SAGEROOT/build/pkg/standard/
, SAGEROOT/build/pkg/optional/, e
On 12.05.2015 09:28, Nathann Cohen wrote:
Okay, so what do we do with this bug?
1) make Sage's default 'max' be 'max_symbolic' (yes/no)
+1 imho the only reason not to do is performance, and it seems to be ok
like pointed Nils pointed out.
2) Return "Unknown" instead of False in the __boo
Hi,
Harald is currently in the process of migrating the website.
On Wed, May 13, 2015 at 11:16 AM, Nathann Cohen wrote:
>> If you or someone else is messing around a bit with the doc, note that
>> currently
>>
>> http://www.sagemath.org/doc/
>>
>> gives a 404 error for Github Pages ?!?!
>
> Same
> If you or someone else is messing around a bit with the doc, note that
> currently
>
> http://www.sagemath.org/doc/
>
> gives a 404 error for Github Pages ?!?!
Same here. And I was about to ask for
http://www.sagemath.org/packages/standard/list
To be replaced with
http://www.steinertriples.fr/n
If you or someone else is messing around a bit with the doc, note that
currently
http://www.sagemath.org/doc/
gives a 404 error for Github Pages ?!?! and I'm sure this is connected to
not being able to download packages when using git pull to update your repo.
--
You received this message bec
Volker Braun wrote:
> IMHO:
>
> * The package type (standard/optional/experimental) should be in a file
> inside the package directory
Yes. Suggestions?
checksums.ini and package-version.txt don't seem appropriate to add it
there (nor of course SPKG.txt), so we'd need a new file I think.
It wo
On Wednesday, May 13, 2015 at 12:48:41 PM UTC+2, Nathann Cohen wrote:
>
> Some of us were wondering who was in charge of generating Sage's
> changelogs ...
>
I'm also wondering about a proper way to deal with them. The transition of
the webite away from the UW servers has completed and the cha
Nathann Cohen wrote:
> Some of us were wondering who was in charge of generating Sage's
> changelogs [1], and whether the script used for that could be made
> public?
>
> It would be cool if we could gather somewhere the tools that are used
> for Sage's 'administration'.
>
> (I do not mind helpin
>Really, bool(x) means known_true(x).
>And of course, not(known_true(x))
>is not the same as known_false(x).
Sure, but adequate naming is crucial, too.
Also the design as is does not prevent a developer from applying boolean
operations (negating, and,or,...) by accident on the result.
A similar
2015-05-12 21:03:27 UTC+2, Jakob Kroeker:
> > Its just behaving as specified, False means "cannot decide"
> I find, this was a pretty unfortunate specification.
> I think it would be kind of ok in case 'bool()' would be
> named 'Holds_If_True_Otherwise_Unknown()' instead
Really, bool(x) mea
I would prefer a RAISES section that also defines what happens if
preconditions are violated, but calling it ASSUMPTIONS would be fine with
me too. In any case, it ought to be documented at
http://www.sagemath.org/doc/developer/coding_basics.html#the-docstring-of-a-function-content
On Wednesd
Hello everybody,
Some of us were wondering who was in charge of generating Sage's
changelogs [1], and whether the script used for that could be made
public?
It would be cool if we could gather somewhere the tools that are used
for Sage's 'administration'.
(I do not mind helping clean&document th
Hi Leif,
On 2015-05-13, leif wrote:
> Simon King wrote:
>> In his previous post, Nicolas mentioned that sometimes one needs to
>> formulate preconditions that self needs to provide, or one needs to fix
>> a notation involving self. I believe that preconditions should be
>> formulated in an ASSUMP
Simon King wrote:
>> Really, this is about presenting a consistent documentation to end users.
>> They shouldn't have to know how Python scopes the object state, and they
>> most certainly shouldn't have to guess whether Nicolas thought it would be
>> a good idea to add 'self' to the INPUT secti
On Monday, May 11, 2015 at 12:21:49 PM UTC+2, Simon King wrote:
>
> On 2015-05-11, Vincent Delecroix <20100.d...@gmail.com >
> wrote:
> > On 11/05/15 11:42, Volker Braun wrote:
> >> IMHO the only bug is that commenting on closed tickets is possible.
> >>
> > This is not a bug! It is really u
Some of you may have heard of the SPDX workgroup
and the open compliance standard they are developing.
http://www.linuxfoundation.org/news-media/announcements/2015/05/linux-foundation-s-spdx-workgroup-announces-new-open-compliance
http://spdx.org/
https://lists.spdx.org/mailman/listinfo/spdx-tec
I think it should be possible to edit a closed ticket,
at least to
a. mention follow-up tickets
b. mention related discussions on sage-devel etc
c. add keywords
A nice feature, which would complement (a) above,
would be a "cited in" field, which would self-update
whenever the ticket is mentioned
On Sunday, May 10, 2015 at 10:33:51 AM UTC+2, Benjamin Hackl wrote:
>
> I'm strongly in favor of returning an element of PowerSeriesRing -- within
> the current
> implementation, this happens:
>
> sage: (1/(1+x)).series(x, 2) + (1/(1-x)).series(x, 2)
> (1 + (-1)*x + Order(x^2)) + (1 + 1*x + Order
35 matches
Mail list logo
