In the terminal output, it looks like you are installing sagemath-standard
10.2 in an environment with sage-conf 10.3.beta7. Try forcing
sagemath-standard==10.3.beta7 (or use the switch "--pre" with pip install).
(In https://github.com/sagemath/sage/pull/37261 I am updating the
instructions; yo
Description of RunTimeError from docs.python.org: "Raised when an error is
detected that doesn’t fall in any of the other categories. The associated
value is a string indicating what precisely went wrong."
It is for exceptions that cannot be categorized, so I believe it is indeed
just a catch-a
On Thu, Feb 8, 2024 at 8:18 PM 'Travis Scrimshaw' via sage-devel <
sage-devel@googlegroups.com> wrote:
> For RuntimeError, I would make it sound like it tells you there is serious
> error occurring as it doesn't fall into any other error categories. This
> actually makes it the opposite of a catch
Martin's solution is the correct one as it should be preparsing the input
before it gets to the __init__(), which is then used as the key. This also
is needed for HallLittlewood and Macdonald.
Best,
Travis
PS - Sorry for not responding sooner about this.
On Tuesday, February 6, 2024 at 4:16:21
I would be vague about a TypeError versus a ValueError. These are used in
various ways by different authors over different periods. It can also be
very hard to make this rigorous. For example, for something accepting
integer inputs, then 2/2 fails the isinstance() check but shouldn't throw
an e
You can try if 'export MAKE="make -j4"' fixes this
On Thursday, February 8, 2024 at 1:21:32 PM UTC-8 Sai Chandhrasekhar wrote:
> When running python3 -m pip install --no-build-isolation
> sagemath-standard I got this error message:
>
> clang -bundle -undefined dynamic_lookup -g
> -L/Users/user/
When running python3 -m pip install --no-build-isolation sagemath-standard
I got this error message:
clang -bundle -undefined dynamic_lookup -g
-L/Users/user/.sage/sage-10.3.beta7-Darwin-x86_64/local/lib
-Wl,-rpath,/Users/user/.sage/sage-10.3.beta7-Darwin-x86_64/local/lib
build/temp.macosx-10.
I was able to get it to work. I found out I added the wrong location to
PATH. I fixed it and got the command to work.
On Thursday, February 8, 2024 at 1:00:52 PM UTC-6 Sai Chandhrasekhar wrote:
> I did get a warning about that and added it to my PATH before running the
> command, but I still g
I did get a warning about that and added it to my PATH before running the
command, but I still got the result. I did what you suggested and still got
the same error message.
On Thursday, February 8, 2024 at 12:27:29 PM UTC-6 Matthias Koeppe wrote:
> That's great progress.
>
> Did pip issue an
That's great progress.
Did pip issue any warnings when you installed sage_conf?
In particular, it may have warned that the installation location for
scripts is not in your PATH.
If so, you can fix it as follows:
export PATH="$(python3 -c 'import sysconfig;
print(sysconfig.get_path("scripts", "
I was able to install sage_conf successfully, but when I run, "python3 -m
pip install $(sage-config SAGE_SPKG_WHEELS)/*.whl sage_setup", I get the
following error messages:
zsh: command not found: sage-config
zsh: no matches found: /*.whl
On Wednesday, February 7, 2024 at 3:13:27 PM UTC-6 Mat
On Thu, 2024-02-08 at 11:30 +, Dima Pasechnik wrote:
>
> We should not try to compete, in effect, with Conda etc, yet we do. This is
> the primary reason for slowness.
>
My personal stats for the year 2023-02-08 through 2024-02-08:
Commits: 423
Reviews: 38
Zero of those have anything t
1. We have a low development velocity. For example, some simple PRs sit for
weeks or months before receiving any review comments. What can we do to
improve this?
There have always been PRs or trac tickets with no comment for long time. I
guess most of us had such tickets in trac era. I doubt
13 matches
Mail list logo