Closed strogdon closed 3 years ago
This is strange I don't get that failure. I cannot think of what would truncate the output like this.
I have it on both gentoo and prefix. The indicated files were touched at https://trac.sagemath.org/ticket/30587
Can you try it like this
fbissey@moonloop ~ $ sage
┌────────────────────────────────────────────────────────────────────┐
│ SageMath version 9.3.beta3, Release Date: 2020-12-06 │
│ Using Python 3.8.6. Type "help()" for help. │
└────────────────────────────────────────────────────────────────────┘
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Warning: this is a prerelease version, and it may be unstable. ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
sage: from sage.features import PythonModule
sage: lazy_import('foo', 'not_there', feature=PythonModule('foo', spkg='non-existing-package'))
sage: not_there
Failed lazy import:
foo is not available.
Importing not_there failed: No module named 'foo'
No equivalent system packages for pip are known to Sage.
and see what it says? While my sage says 9.3.beta3, the only commit missing from beta4 is the version number change.
steven@hp-envy ~ $ sage
┌────────────────────────────────────────────────────────────────────┐
│ SageMath version 9.3.beta4, Release Date: 2020-12-14 │
│ Using Python 3.8.6. Type "help()" for help. │
└────────────────────────────────────────────────────────────────────┘
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Warning: this is a prerelease version, and it may be unstable. ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
sage: from sage.features import PythonModule
sage: lazy_import('foo', 'not_there', feature=PythonModule('foo', spkg='non-existing-package'))
sage: not_there
Failed lazy import:
foo is not available.
Importing not_there failed: No module named 'foo'
I bet it's because I do not have pip
installed.
That sounds like a good explanation.
That was it. I don't need pip
. There is one other doctest that fails if pip
is not installed.
I have this somewhat odd doctest failure
It seems cosmetic but what is the source?