On Fri, Nov 16, 2018 at 2:38 PM Luca De Feo wrote:
>
> > How fast will new SageMath versions be packaged? I suppose that fast
> > enought, and those needing the bleeding edge version can compile it
> > themself.
>
> I agree. Ubuntu bionic has 8.1, cosmic has 8.3.
>
> Unless we screw up and make
On Sun, Nov 11, 2018 at 11:28 PM Emmanuel Charpentier
wrote:
>
> Dear Erik,
>
> Le vendredi 9 novembre 2018 17:56:58 UTC+1, Erik Bray a écrit :
>>
>> On Fri, Nov 9, 2018 at 2:38 PM Emmanuel Charpentier
>> wrote:
>> >
>> >
>> >
>>
I have an idea of what might cause this and will submit a fix, but
just manually delete the existing file and try again.
On Mon, Nov 12, 2018 at 8:23 AM David Coudert wrote:
>
> Hello,
>
> After git pull to go from 8.5.beta2 to 8.5.beta3, I get a compilation error
> with gsl-2.5 (see attached
On Fri, Nov 9, 2018 at 2:38 PM Emmanuel Charpentier
wrote:
>
>
>
> Le vendredi 9 novembre 2018 13:40:12 UTC+1, Erik Bray a écrit :
>>
>> Can someone remind me again why SSL libs aren't provided by the system
>> on macOS, and/or why those libs can't be used for b
On Fri, Nov 9, 2018 at 2:14 PM Dima Pasechnik wrote:
>
> On Fri, Nov 9, 2018 at 8:01 AM Erik Bray wrote:
> >
> > On Fri, Nov 9, 2018 at 1:50 PM Dima Pasechnik wrote:
> > >
> > > On Fri, Nov 9, 2018 at 7:40 AM Erik Bray wrote:
> > > >
> &g
On Fri, Nov 9, 2018 at 1:50 PM Dima Pasechnik wrote:
>
> On Fri, Nov 9, 2018 at 7:40 AM Erik Bray wrote:
> >
> > Can someone remind me again why SSL libs aren't provided by the system
> > on macOS, and/or why those libs can't be used for building Python's
> > ssl
Can someone remind me again why SSL libs aren't provided by the system
on macOS, and/or why those libs can't be used for building Python's
ssl module?
Surely the Python community at large has some experience with this but
I don't really know what that experience constitutes...
On Fri, Nov 9, 2018
x.
It might have re-occurred for you (or anyone) if you changed to an old
branch and re-built.
> On Monday, August 27, 2018 at 1:46:25 AM UTC-7, Erik Bray wrote:
>>
>> On Sat, Aug 25, 2018 at 3:39 PM Sébastien Labbé wrote:
>> >
>> > On one machine, I get th
On Tue, Nov 6, 2018 at 12:57 PM Jeroen Demeyer wrote:
>
> On 2018-10-31 22:23, Volker Braun wrote:
> > With ipython/jupyter you can't run the notebook in the current Python
> > session, but you can just launch a completely new process.
>
> Are you sure? Can't you just import the Jupyter
here, but
never really made progress on it. I think the one "new" point I'm
making here is that `import sage` should *just work* without having to
set any special environment variables :/
> Am Dienstag, 6. November 2018 11:10:52 UTC+1 schrieb Erik Bray:
>>
>> On Mon, Nov
On Fri, Nov 2, 2018 at 3:19 PM John Cremona wrote:
>
>
>
> On Fri, 2 Nov 2018 at 13:21, Vincent Delecroix <20100.delecr...@gmail.com>
> wrote:
>>
>>
>>
>> Le 31/10/2018 à 13:50, Samuel Lelievre a écrit :
>> >
>> >
>> > Le mardi 30 octobre 2018 08:06:15 UTC+1, Frédéric Chapoton a écrit :
>> >>
>>
On Mon, Nov 5, 2018 at 8:11 AM Jori Mäntysalo wrote:
>
> I am trying to marry SageMath and Jupyterhub. I think I got them engaged,
> but the wedding night has a problem:
>
> Error: You must set the SAGE_ROOT environment variable or run this
> script from the SAGE_ROOT or SAGE_ROOT/local/bin/
On Tue, Nov 6, 2018 at 10:41 AM Frédéric Chapoton wrote:
>
> Well, python3 builtin "round" calls the method "__round__" of the objects,
> which does not exist for sage objects so far and which is expected to do
> something different from what sage does with its methods .round
>
> See ticket
Also, Samuel, could you forward this to debian-science-sage mailing
list?On Mon, Nov 5, 2018 at 1:02 PM Samuel Lelièvre
wrote:
>
> Dear sage-devel,
>
> The freeze period for the next Debian release starts on
> 12 January 2019, as discussed at
>
>
On Mon, Nov 5, 2018 at 8:12 PM David Roe wrote:
>
>
>
> On Mon, Nov 5, 2018 at 7:02 AM Samuel Lelièvre
> wrote:
>>
>> Dear sage-devel,
>>
>> The freeze period for the next Debian release starts on
>> 12 January 2019, as discussed at
>>
>> https://trac.sagemath.org/ticket/22626#comment:118
>>
We already have notebook(). We should change that so that the default
notebook to launch is the jupyter notebook.
On Wed, Oct 31, 2018 at 1:50 PM Samuel Lelievre
wrote:
>
>
>
> Le mardi 30 octobre 2018 08:06:15 UTC+1, Frédéric Chapoton a écrit :
>>
>> Because we do not have a clean command
On Wed, Oct 31, 2018 at 12:25 AM Thierry
wrote:
>
> Hi,
>
> On Tue, Oct 30, 2018 at 04:18:16PM -0700, 'Paul Mercat' via sage-devel wrote:
> > Hi !
> >
> > I'm currently working on things in sage that uses the librairy SDL2.
> > This librairy is not part of sage if I'm not mistaken, but it is
On Sun, Oct 14, 2018 at 10:42 AM François Bissey wrote:
>
>
>
> > On 14/10/2018, at 21:37, Vincent Delecroix <20100.delecr...@gmail.com>
> > wrote:
> >
> > I am impressed by the number of persons
> > I see still using the legacy notebook.
>
> The whole math department of university of Canterbury
It might be more useful to see the config.log for R. I think usually
when a build fails there is a message providing a path to the
config.log of the build.
This would tell us exactly what commands configure ran and why it
failed (in principle).
On Sun, Oct 28, 2018 at 12:55 PM 'Paul Mercat' via
On Wed, Oct 24, 2018 at 1:02 PM Sébastien Labbé wrote:
>
>
>
> On Wednesday, October 24, 2018 at 1:00:15 PM UTC+2, Sébastien Labbé wrote:
>>
>> This seems great! It seems something that should be incorporated in ipython
>> as an option so that Sage could just use it.
>
>
> Actually, there exists
I have no idea what modular symbols are, and wikipedia is not much
help beyond it having something to do with modular forms, though I
found an interesting book [1] on the subject. But it seems to work in
8.4.beta7:
$ ./sage
┌┐
│
Ditto Dima; this is an entirely local problem. Are you running an ssh-agent?
On Mon, Oct 8, 2018 at 2:20 PM Dima Pasechnik wrote:
>
> Works for me. Your log seems to indicate that something is wrong on your end.
> (perhaps permissions of files containing keypairs?)
> Have a look at
>
On Wed, Oct 3, 2018 at 6:53 PM Dima Pasechnik wrote:
>
> On Wed, Oct 3, 2018 at 3:16 PM Dima Pasechnik wrote:
> >
> > 1) How does one suppress noisy messages about threads (coming from ipython,
> > I suppose)?
> >
> > 2) How does one supress breaks coming from Python try/except blocks?
>
> OK,
On Fri, Sep 28, 2018 at 10:03 PM Harald Schilly
wrote:
>
>
>
> On Monday, September 24, 2018 at 3:12:12 PM UTC+2, kcrisman wrote:
>>
>> Certainly R and probably other similar mathematical FLOSS does have
>> foundations...
>
>
> I just came across this thread. Many years ago I had the idea to
Hi folks,
The topic of Sage joining the NumFOCUS [1] organization was raised in
the recent thread [2] about the SageMath Foundation. When I first
started working on Sage I was frankly surprised that it wasn't already
affiliated with NumFOCUS, along with many other projects on which Sage
is built
gt; Mirrored from git://git.sagemath.org/sage.git.
> The repository failed to update 1 week ago.
> Repository mirroring has been paused due to too many failed attempts, and can
> be resumed by a project maintainer.
> Last successful update 2 weeks ago.
>
>
> On Saturday, Septe
At least three people have reported the same problem, just FYI.
Perhaps something went wrong with building the .dmg. I don't know how
to fix it (I don't know anything about dmgs):
https://ask.sagemath.org/question/43594/problems-installing-sage-83-on-osx
--
You received this message because
On Mon, Sep 3, 2018 at 3:53 PM Erik Bray wrote:
>
> On Tue, Aug 21, 2018 at 10:43 AM Erik Bray wrote:
> >
> > Hi all,
> >
> > Earlier this spring Julian Rüth and I sat down and created a mirror of
> > Sage's repository over at GitLab:
>
On Wed, Sep 26, 2018 at 4:48 PM William Stein wrote:
>
> On Wed, Sep 26, 2018 at 3:14 AM, Dima Pasechnik wrote:
> > On Wed, Sep 26, 2018 at 10:35 AM Jeroen Demeyer wrote:
> >>
> >> On 2018-09-24 18:00, Dima Pasechnik wrote:
> >> > Perhaps the most tricky is 2 (or perhaps not anymore, after out
There was a recently fixed bug with doctest parsing. Fixing the bug
also caused some tests that were affected by that bug to suddenly
start failing (rather, because they weren't being run in the first
place). I'm not sure if it's relevant to your case or not:
On Wed, Sep 26, 2018 at 10:54 AM Jeroen Demeyer wrote:
>
> On 2018-09-26 10:10, 'Martin R' via sage-devel wrote:
> > In https://trac.sagemath.org/ticket/26348 a doctest is failing, because
> > apparently the semantics of "..." has changed.
>
> I don't think that anything has changed here. As far
On Mon, Sep 24, 2018 at 8:15 PM William Stein wrote:
>
> On Mon, Sep 24, 2018 at 9:35 AM, Erik Bray wrote:
> > 5) also might be harder than you think--or at least, even if we can
> > come up with an uncontroversial list of names, it's a discussion that
> > invites
Hello,
I have two tickets I'm responsible for that are considered "blockers"
and are somewhat related. The first one I don't personally consider a
blocker, but it should still be fixed. If my proposed fix in that
ticket is acceptable, it would also fix the issue in the second ticket
as a bonus:
On Mon, Sep 24, 2018 at 6:39 PM Dima Pasechnik wrote:
>
> On Mon, Sep 24, 2018 at 5:11 PM William Stein wrote:
> >
> > On Mon, Sep 24, 2018 at 9:00 AM, Dima Pasechnik wrote:
> >
> > > 1, 3, 4 is there or very easy to set up. 5 should not be too hard either.
> > > Perhaps the most tricky is 2
his)
5) also might be harder than you think--or at least, even if we can
come up with an uncontroversial list of names, it's a discussion that
invites questions about project governance. It might be interesting
to follow the recent discussions about Python governance with the BDFL
stepping d
not as messy as the wiki page William points to
(see also my most recent thread on sage-flame).
I was going to suggest, in the process of making that PR, it would be
a good time to re-evaluate and see if there is anything we would like
to update before committing it to the sagema
s for it can be found that way.
> >
> > On Friday, September 21, 2018 at 11:06:47 AM UTC-4, Erik Bray wrote:
> >>
> >> On Fri, Sep 21, 2018 at 4:29 PM Nils Bruin wrote:
> >> >
> >> > On Friday, September 21, 2018 at 1:46:47 AM UTC-7, Erik Bray wrote:
&
On Mon, Sep 24, 2018 at 3:35 PM William Stein wrote:
>
> On Mon, Sep 24, 2018 at 6:12 AM, kcrisman wrote:
> >
> >
> > On Sunday, September 23, 2018 at 1:18:50 AM UTC-4, rjf wrote:
> >>
> >> I assume that other research universities work about the same as at UC
> >> Berkeley. Anyone can donate
On Sun, Sep 23, 2018 at 7:23 PM William Stein wrote:
>
> On Sun, Sep 23, 2018 at 9:57 AM, Simon King wrote:
> > Hi Andy,
> >
> > On 2018-09-23, Andy Howell wrote:
> >> I'd guess the word "tricks" was objectionable. What I meant was
> >> techniques like locating the source using funcName? Now
On Sat, Sep 22, 2018 at 10:30 PM Emmanuel Charpentier
wrote:
> Le samedi 22 septembre 2018 22:19:32 UTC+2, Erik Bray a écrit :
>>
>> Try
>>
>> $ git branch -d origin/u/embray/python3/sage-rings-polynomial-polydict
>
>
> No such luck :
>
> charpent@
Try
$ git branch -d origin/u/embray/python3/sage-rings-polynomial-polydict
You wouldn't have the above branch without "origin" unless you created a
remote tracking branch. It's only remote branches which you're having a
problem with
(note: this happened because I had an older branch named
On Fri, Sep 21, 2018 at 4:29 PM Nils Bruin wrote:
>
> On Friday, September 21, 2018 at 1:46:47 AM UTC-7, Erik Bray wrote:
>>
>> There is a cool module in sage called sage.misc.explain_pickle, which
>> is useful for helping to understand and debug how non-trivial object
On Fri, Sep 21, 2018 at 3:00 PM Jeroen Demeyer wrote:
>
> It must be said that I found this tool quite valuable. When unpickling
> goes wrong, it is typically not easy to find out why and explain_pickle
> does help with that.
>
> That being said, if nobody wants to maintain it, it has to go (with
There is a cool module in sage called sage.misc.explain_pickle, which
is useful for helping to understand and debug how non-trivial objects
in Sage are pickled and unpickled.
However, it's a big, fairly complicated module which carries quite a
bit of technical debt with it, and relatively little
You have some files with the wrong permissions set on them. When you
write "I decided to rebuild the newest version of sage on my new
computer" were you building in the same directory as before, or from
scratch in a new clone of the repository? I ask because it's doubtful
that an upgrade from
On Sat, Sep 15, 2018 at 3:21 PM Eric Gourgoulhon wrote:
>
> Hi Volker,
>
> Le vendredi 14 septembre 2018 22:44:34 UTC+2, Volker Braun a écrit :
>>
>> I don't think there was a deliberate change. Rendering the jmol version
>> requires java, which is an external dependency. There was also a bug in
On Thu, Sep 13, 2018 at 3:08 PM John Cremona wrote:
>
>
>
> On Thu, 13 Sep 2018 at 13:42, Erik Bray wrote:
>>
>> Hi all,
>>
>> This class has a doctest that is failing on Python 3, and it's not
>> clear to me whether the bug is really in the code,
Hi all,
This class has a doctest that is failing on Python 3, and it's not
clear to me whether the bug is really in the code, or the test itself.
The test that's failing is:
sage: R. = QQ[]
sage: V = span(R,[[x,1+x],[x^2,2+x]])
sage: W = RR^2
On Tue, Sep 11, 2018 at 5:30 PM Simon King wrote:
>
> Hi Erik,
>
> On 2018-09-11, Erik Bray wrote:
> > On Tue, Sep 11, 2018 at 9:57 AM Kwankyu Lee wrote:
> >>
> >> Hi,
> >>
> >> I wonder why help on a method does not show the signature:
>
beyond the fact that
zn_poly is currently supported. But thanks!
If others want to look into using NTL to replace zn_poly in Sage they
should work on that and see if the benefits hold up.
> On Friday, September 7, 2018 at 9:53:43 AM UTC-4, Erik Bray wrote:
>>
>> Hi all,
>>
>>
On Tue, Sep 11, 2018 at 9:57 AM Kwankyu Lee wrote:
>
> Hi,
>
> I wonder why help on a method does not show the signature:
It's not because it's a method. It's because it's a Cythonized
built-in method, for which it's not possible to introspect the
signature. This is a known issue not in Sage
On Mon, Sep 10, 2018 at 6:33 AM John H Palmieri wrote:
>
> One thing to try, in case you haven't already: run make once, and if it fails
> with a warning like this, try running make again immediately (without doing
> "make distclean"). (Sage may be using Sage's python in the installation
>
as wrote:
>>
>>
>>
>> El viernes, 7 de septiembre de 2018, 15:53:43 (UTC+2), Erik Bray escribió:
>>>
>>> Hi all,
>>>
>>> Does anyone know what that current status is of the upstream zn_poly
>>> package? According to its website
>
On Fri, Sep 7, 2018 at 6:59 PM Timo Kaufmann wrote:
>
> Great! Please let us know on sage-packaging once you put out a new release
> and switch sage over.
Yes, definitely. I will also update the relevant SPKG.txt.
--
You received this message because you are subscribed to the Google Groups
s repository.
> On Fri, Sep 7, 2018 at 9:53 AM Erik Bray wrote:
>>
>> Hi all,
>>
>> Does anyone know what that current status is of the upstream zn_poly
>> package? According to its website
>> http://cims.nyu.edu/~harvey/zn_poly/ it is "no longer maintained&qu
On Fri, Sep 7, 2018 at 6:27 PM Timo Kaufmann wrote:
>
>
>
> Am Freitag, 7. September 2018 17:56:04 UTC+2 schrieb Erik Bray:
>>
>> On Fri, Sep 7, 2018 at 5:29 PM Timo Kaufmann wrote:
>> >
>> > For what its worth, we currently don't apply any patches i
w home would be
> very good. +1 from me.
Most of the patches are build-related and test-related fixes, many of
which seem to stem from issues on OSX.
> Am Freitag, 7. September 2018 15:53:43 UTC+2 schrieb Erik Bray:
>>
>> Hi all,
>>
>> Does anyone know what that current st
Hi all,
Does anyone know what that current status is of the upstream zn_poly
package? According to its website
http://cims.nyu.edu/~harvey/zn_poly/ it is "no longer maintained",
though it has been re-released under a BSD-compatible license.
Since its last upstream release the package for it in
On Thu, Sep 6, 2018 at 11:40 AM David Coudert wrote:
>
> Comparisons like u < v are used in many places in the code of graphs.
> We can try to use hash(u) < hash(v) instead, but this is certainly not the
> smartest solution.
I have a long-outstanding proposal for a SafeSortable utility that
On Tue, Sep 4, 2018 at 3:02 PM Daniel Krenn wrote:
>
> On 09/04/2018 02:33 PM, Jeroen Demeyer wrote:
> > Let me make one important comment (something that I've said before
> > though): a large part of what makes the current workflow work is not so
> > much Trac itself but our git server and the
Keeping in mind that this is still sort of off-topic, in my mind, from
the subject at hand which is allowing merge request submissions from
GitLab, which still get turned into Trac tickets...
On Tue, Sep 4, 2018 at 2:33 PM Jeroen Demeyer wrote:
>
> Let me make one important comment (something
On Mon, Sep 3, 2018 at 5:04 PM Jeroen Demeyer wrote:
>
> On 2018-09-03 15:53, Erik Bray wrote:
> > P.S. If anyone has additional comments, positive or negative, on
> > https://trac.sagemath.org/ticket/25914 they would be most appreciated
>
> That doesn't seem the r
On Tue, Aug 21, 2018 at 10:43 AM Erik Bray wrote:
>
> Hi all,
>
> Earlier this spring Julian Rüth and I sat down and created a mirror of
> Sage's repository over at GitLab:
>
> https://gitlab.com/sagemath/sage
>
> This is in addition to the existing mirror at
itle when :ref:-ing
that label.
In the meantime I have also opened an upstream issue:
https://github.com/sphinx-doc/sphinx/issues/5382
> On Mon, 3 Sep 2018 at 12:19, Erik Bray wrote:
>>
>> On Mon, Sep 3, 2018 at 1:10 PM Erik Bray wrote:
>> >
>> > On Mon, Sep 3, 20
On Mon, Sep 3, 2018 at 1:10 PM Erik Bray wrote:
>
> On Mon, Sep 3, 2018 at 12:51 PM Samuel Lelièvre
> wrote:
> >
> > In the list of thematic tutorials at
> >
> > http://doc.sagemath.org/html/en/thematic_tutorials/
> >
> > the second tut
On Mon, Sep 3, 2018 at 12:51 PM Samuel Lelièvre
wrote:
>
> In the list of thematic tutorials at
>
> http://doc.sagemath.org/html/en/thematic_tutorials/
>
> the second tutorial in the "Number Theory" section displays as
>
> - Introduction to the -adics
>
> despite the title displaying properly
On Thu, Aug 30, 2018 at 11:04 AM Jeroen Demeyer wrote:
>
> At #26110 we noticed that the --optional option for doctests is really
> strange when you don't specify "sage" as one of the optional packages.
>
> Here is how things currently work: any doctest line which doesn't
> contain any other tag
On Mon, Aug 27, 2018 at 12:21 PM François Bissey wrote:
>
> https://trac.sagemath.org/ticket/26114 should be in the next beta and fix
> this issue.
Do you know if we have any progress on the process of deprecating jmol?
> > On 27/08/2018, at 22:18, Eric Gourgoulhon wrote:
> >
> > Hi,
> >
> >
On Tue, Aug 28, 2018 at 2:36 AM John Cremona wrote:
>
> I could do this for elliptic curves, but not this week as I'm at a meeting.
FWIW for elliptic curves my python3 branch has these failures:
sage -t src/sage/schemes/elliptic_curves/descent_two_isogeny.pyx # 1
doctest failed
sage -t
On Tue, Aug 28, 2018 at 12:05 AM Travis Scrimshaw wrote:
>
>
>
> On Tuesday, August 28, 2018 at 4:41:32 AM UTC+10, John H Palmieri wrote:
>>
>> Is it possible to configure trac.sagemath.org so that
>>
>> - it is not possible to select "Needs review" if the author field is blank?
>> (or it gives
On Sat, Aug 25, 2018 at 3:39 PM Sébastien Labbé wrote:
>
> On one machine, I get this:
>
> $ du -s -h local/share/doc/sage
> 20G/local/share/doc/sage
>
> on the other, I get this:
>
> $ du -s -h local/share/doc/sage
> 1,9Glocal/share/doc/sage
>
> I do not know why the bug affects only
On Sun, Aug 26, 2018 at 5:47 PM Frédéric Chapoton wrote:
>
> Dear all, here is a short python3 status report.
>
> There is a patchbot report with python3 for 8.4.b2 somewhere on the page :
> https://patchbot.sagemath.org/ticket/0/
> (@ patchbot breeders, please update your patchbot so that we
On Thu, Aug 23, 2018 at 10:13 PM John H Palmieri wrote:
>
> I found that my Sage documentation directory was taking up 15GB of hard drive
> space, because of a bug (which I think has been fixed, but I don't remember
> where). The bug was caused by a recursive symlink
>
>
On Wed, Aug 22, 2018 at 10:25 PM Simon King wrote:
>
> Hi Erik,
>
> On 2018-08-22, Erik Bray wrote:
> > Really the workflow is meant to be you create an issue first, and then
> > you create one or more pull requests to resolve that issue. I am also
> > a fan of be
On Thu, Aug 23, 2018 at 8:51 AM Dima Pasechnik wrote:
>
>
>
> On Thursday, August 23, 2018 at 7:13:32 AM UTC+3, Julian Rüth wrote:
>>
>> Hello Jeroen,
>>
>> I agree that fragmentation can be a problem. Then again, I think that
>> sometimes splitting discussion on the issue and the discussion on
On Thu, Aug 23, 2018 at 6:13 AM Julian Rüth wrote:
>
> Hello Jeroen,
>
> I agree that fragmentation can be a problem. Then again, I think that
> sometimes splitting discussion on the issue and the discussion on an actual
> attempt to solve that issue can be useful; at least it doesn't feel
On Wed, Aug 22, 2018 at 8:58 PM Jeroen Demeyer wrote:
>
> For me, the number 1 thing that our Trac server does better than GitHub
> (again, I don't know about GitLab) is that the "branch" field is
> mutable: an issue is just a pull request without a branch and I can
> change the branch on a pull
On Wed, Aug 22, 2018 at 5:38 PM Jeroen Demeyer wrote:
>
> On 2018-08-21 10:43, Erik Bray wrote:
> > A second clarification to make is that we are not currently proposing
> > to do away with Trac for Sage's ticket database
>
> I find this quite important. I really really r
On Wed, Aug 22, 2018 at 11:08 AM Simon King wrote:
>
> Tue 2018-08-21 08:43:19 UTC, Erik Bray:
> > What does everyone think? Is there anyone opposed to going ahead and
> > opening up merge requests?
>
> Is the plan to successively reduce the usage of our current trac syst
On Tue, Aug 21, 2018 at 6:47 PM Eric Gourgoulhon wrote:
>
> Hi,
>
> Le mardi 21 août 2018 10:43:19 UTC+2, Erik Bray a écrit :
>>
>>
>> Why GitLab? In short, we felt it would likely be more acceptable to
>> most members of the Sage community; this
On Tue, Aug 21, 2018 at 5:05 PM William Stein wrote:
>
> On Tue, Aug 21, 2018 at 1:43 AM, Erik Bray wrote:
>
> > Some of you may remember this is not a first for Sage either: some
> > time ago there was a similar experiment done with GitHub, but it fell
> > unmai
On Tue, Aug 21, 2018 at 11:21 AM Daniel Krenn wrote:
>
> On 08/21/2018 10:43 AM, Erik Bray wrote:
> > https://gitlab.com/sagemath/sage
>
> How do I become a member of the SageMath group (or the project) in
> Gitlab? (username: dakrenn)
Just ask, like you just did :)
H
Forgot to attach screenshot.
On Tue, Aug 21, 2018 at 10:43 AM Erik Bray wrote:
>
> Hi all,
>
> Earlier this spring Julian Rüth and I sat down and created a mirror of
> Sage's repository over at GitLab:
>
> https://gitlab.com/sagemath/sage
>
> This is in addition to th
Hi all,
Earlier this spring Julian Rüth and I sat down and created a mirror of
Sage's repository over at GitLab:
https://gitlab.com/sagemath/sage
This is in addition to the existing mirror at GitHub, for which we
have no immediate plans except to have it link to the GitLab mirror.
The reasons
I restarted apache and postgres and it seems fine for now, but from
the log it looks like the site was being scraped by something that
wasn't obeying robots.txt and thus effectively DoS-ing us.
On Mon, Aug 20, 2018 at 11:51 AM Erik Bray wrote:
>
> I'm on it.
> On Mon, Aug 20, 2018 at
I'm on it.
On Mon, Aug 20, 2018 at 11:49 AM Dima Pasechnik wrote:
>
> Is it just me, or it's really down, and should be rebooted?
>
> Dima
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "sagemath-admins" group.
> To unsubscribe from this group and
On Fri, Aug 17, 2018 at 2:02 PM Eric Gourgoulhon wrote:
>
> Hi Erik,
>
> Le jeudi 16 août 2018 13:53:41 UTC+2, Erik Bray a écrit :
>>
>>
>> Love how fork() is even more broken on OSX now than it is on Cygwin =_=
>
>
> Btw, I would be curi
On Fri, Aug 10, 2018 at 9:48 PM Jeroen Demeyer wrote:
>
> On 2018-08-09 14:54, Erik Bray wrote:
> > In principle, if classes had this, one might also want it for
> > functions, but that's a little bit more problematic.
>
> I think that's already a bit problematic: whet
On Thu, Aug 16, 2018 at 2:50 PM Jeroen Demeyer wrote:
>
> On 2018-08-16 14:30, Erik Bray wrote:
> > In the meantime I think we should remove that warning, or at least
> > have a way to disable it, as it's clearly confusing to users.
>
> *NOT* having the warning is also co
On Wed, Aug 8, 2018 at 7:06 PM Erik Bray wrote:
>
> We still have quite a bit of code around for supporting old-style
> packages in .spkg archives, though it is not well tested anymore and
> I'm not even 100% sure installing these still works.
>
> We have also not
On Tue, Aug 14, 2018 at 8:45 PM Michael Orlitzky wrote:
>
> On 08/14/2018 12:54 PM, Erik Bray wrote:
> >
> > Why would they do even that? It's just a data package. For the
> > purposes of upstream packaging it doesn't need a configure.ac. It can
> > just be a
On Wed, Aug 15, 2018 at 11:08 AM Jeroen Demeyer wrote:
>
> On 2018-08-14 23:43, Erik Bray wrote:
> > Isn't that just the normal message when running `sage -sh`?
>
> IIRC, I added that text because people were generally quite confused
> which kind of commands should be
On Thu, Aug 16, 2018 at 10:27 AM Jeroen Demeyer wrote:
>
> On 2018-08-15 17:46, Eric Gourgoulhon wrote:
> > Various Sage users have reported on that parallelization of tensor field
> > computations does not work on macOS.
>
> This might be https://trac.sagemath.org/ticket/25921
>
> Does it help
On Thu, Aug 16, 2018 at 12:07 AM François Bissey wrote:
>
>
>
> > On 16/08/2018, at 10:04, John H Palmieri wrote:
> >
> > On ticket 25382, https://trac.sagemath.org/ticket/25382, the following
> > questions have been raised:
> >
> > - Is the old Sage notebook deprecated?
> >
> > - If not,
Isn't that just the normal message when running `sage -sh`?
I never even read it that closely. Why *does* it say that? I install
packages and run make from within the sage subshell all the time.
Especially when it comes to optional packages (which should maybe be the
only kind actually supported
On Tue, Aug 14, 2018 at 6:41 PM Michael Orlitzky wrote:
>
> On 08/14/2018 12:22 PM, Erik Bray wrote:
> >
> > I'm not sure what you mean in this case by "system package".
> >
>
> Have the upstream authors create a (basically empty) configure.ac file,
> c
On Tue, Aug 14, 2018 at 5:57 PM Emmanuel Charpentier
wrote:
>
>
>
> Le mardi 14 août 2018 17:20:26 UTC+2, Erik Bray a écrit :
>>
>> On Tue, Aug 14, 2018 at 4:20 PM William Stein wrote:
>> >
>> > On Tue, Aug 14, 2018 at 6:57 AM, Emmanuel Charpentier
>
On Sun, Aug 12, 2018 at 1:21 AM Michael Orlitzky wrote:
>
> On 08/10/2018 11:50 AM, Erik Bray wrote:
> >>
> >> While we are at it: it would be awesome if installation of this
> >> package after upgrade was faster. "Installation" just means unpa
On Sat, Aug 11, 2018 at 11:54 PM Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
>
> On 8/11/18 2:00 PM, 'Justin C. Walker' via sage-devel wrote:
> >
> >
> >> On Aug 11, 2018, at 11:43 , Vincent Delecroix <20100.delecr...@gmail.com>
> >> wrote:
> >>
> >> Hello,
> >>
> >> After some effort, I
e're talking about preparsers lately, is
to support a unary division operator just in Sage.
> On Monday, June 6, 2016 at 6:13:19 AM UTC-4, Jeroen Demeyer wrote:
>>
>> On 2016-06-06 10:39, Erik Bray wrote:
>> > But then you have to deal with the usual mess of ensuring that
1 - 100 of 906 matches
Mail list logo
