an isolated upgrade to 0.18 probably won't fly.
And indeed, jedi is used in ipython, not only in jupyter. Perhaps one
can update only ipython, and leave jupyter for later?
I don't know.
On Tue, Feb 9, 2021 at 8:23 PM 'jonatha...@googlemail.com' via
sage-devel wrote:
>
> Downgrading to jedi
Downgrading to jedi 0.15, I instead get the error (after long wait time)
/usr/lib/python3.7/inspect.py:718: DeprecationWarning:
sage.interacts.debugger is deprecated because it is meant for the
deprecated Sage Notebook
See https://trac.sagemath.org/27531 for details.
if hasattr(object,
The jedi upgrade (to 0.18.0) does not fix the error, but does change the
log:
jonatha...@googlemail.com schrieb am Dienstag, 9. Februar 2021 um 21:05:20
UTC+1:
> Actually the error is reproducible:
>
> def foo(): return 2
> foo()
> foo()
>
> What makes it crash is hitting TAB
Actually the error is reproducible:
def foo(): return 2
foo()
foo()
What makes it crash is hitting TAB after opening the parenthesis and then
completing it and hitting enter.
Matthias Koeppe schrieb am Dienstag, 9. Februar 2021 um 17:56:31 UTC+1:
> A Jupyter upgrade is in
On Tuesday, February 9, 2021 at 9:09:32 AM UTC-8 zsc...@gmail.com wrote:
> I see that the link I posted to the installation from source documentation
> doesn't mention autoconf/automake, but I would have thought some other
> package would have already installed them. Probably since homebrew is
I see that the link I posted to the installation from source documentation
doesn't mention autoconf/automake, but I would have thought some other
package would have already installed them. Probably since homebrew is all
bottles now they don't automatically get installed anymore if you are not
A Jupyter upgrade is in https://trac.sagemath.org/ticket/31280 - which
needs some help
On Tuesday, February 9, 2021 at 6:52:51 AM UTC-8 Dima Pasechnik wrote:
> it looks like https://github.com/davidhalter/jedi/issues/1615
> and our version of jedi is older than the fix there.
> Upgrade jedi (if
On Tue, Feb 9, 2021 at 3:32 PM Trevor Karn wrote:
>
> I uninstalled and reinstalled homebrew and that got rid of the brew doctor
> warnings. I then brewed the suggested packages from the Sage link Zachary
> provided and the packages listed at the end of the output of configure.
>
> Then from
I uninstalled and reinstalled homebrew and that got rid of the brew doctor
warnings. I then brewed the suggested packages from the Sage link Zachary
provided and the packages listed at the end of the output of configure.
Then from SAGE_ROOT I ran
make distclean
source .homebrew-build-env
it looks like https://github.com/davidhalter/jedi/issues/1615
and our version of jedi is older than the fix there.
Upgrade jedi (if this is possible without a full ipython/jupyter
upgrade, don't know) ?
On Tue, Feb 9, 2021 at 1:56 PM 'jonatha...@googlemail.com' via
sage-devel wrote:
>
>
> Dear
Le 09/02/2021 à 02:22, Matthias Koeppe a écrit :
On Monday, February 8, 2021 at 10:42:59 AM UTC-8 Matthias Koeppe wrote:
I think it should be the responsibility of the downstream package to
define a versioning policy - define when they plan to drop support for a
particular Sage version.
Dear all,
sage crashes once in a while hard with some strange error.
Does anyone know what is going on? This is somewhat new. Not reproducible.
Happened to me maybe 3 or 4 times now at various occasions.
Jonathan
--
You received this message because you are subscribed to the Google Groups
This year is difficult for all of us and we lack motivation for this
edition of GSoC.
On the other end, it is more important than ever to push/motivate/help
students.
Other Sagemath contributors than the usual could be involved in mentoring
activity.
I think many contributors are not really
Thank you for reporting this problem. I have opened
https://trac.sagemath.org/ticket/31367 for it and will provide a fix there
shortly.
Akos M schrieb am Montag, 8. Februar 2021 um 11:42:59 UTC+1:
> It seems that unfortunately the problem persists for multivariate rings as
> well:
>
> A. =
On Tue, Feb 9, 2021 at 4:07 AM Zachary Scherr wrote:
>
> I need to sign off for the night, but the numpy error is definitely related
> to gfortran. If you have gcc installed via homebrew then it should come with
> the latest version of gfortran. You can see from your config.log file that
>
15 matches
Mail list logo
