Suggestions?
On Sunday, September 17, 2023 at 11:25:02 AM UTC-7 John H Palmieri wrote:
> Similar problem for me on OS X. I don't understand something: the
> dependencies for scipy include meson_python, but that package is not
> installed before scipy attempts to build, and fails. Runn
When running Sage, if I look at some docststrings by doing foo.bar?, I see
at the top
WARNING: the enclosing module is marked 'needs sage.graphs', so doctests
may not pass.
Of course my copy of Sage has (as far as I know!) a working copy of
sage.graphs. Should this warning only be printed
e function field. You
> may consult the code there.
>
> On Wednesday, September 20, 2023 at 6:08:15 PM UTC+9 Kwankyu wrote:
>
>> Is you element in the cohomology ring an instance of ModuleElement?
>>
>> On Wednesday, September 20, 2023 at 8:34:05 AM UTC+9 John H P
The mod 2 cohomology of a simplicial complex has the structure of a module
over the mod 2 Steenrod algebra. I would like to be able to do this in Sage:
sage: x = (some element in a cohomology ring)
sage: a = (some element of SteenrodAlgebra(2))
sage: a * x
I have tried telling Sage
Similar problem for me on OS X. I don't understand something: the
dependencies for scipy include meson_python, but that package is not
installed before scipy attempts to build, and fails. Running "make
meson_python" and then "make scipy" succeeds, as does "make".
On Saturday, September 16,
That helped, thank you.
On Monday, September 11, 2023 at 8:36:29 AM UTC-7 Gonzalo Tornaría wrote:
> Please try: https://github.com/sagemath/sage/pull/36235
>
> On Monday, September 11, 2023 at 2:59:12 AM UTC-3 John H Palmieri wrote:
>
>> And now I see a similar failure with 10
And now I see a similar failure with 10.2.beta1. It could be the latest OS
X upgrade.
On Sunday, September 10, 2023 at 10:29:32 PM UTC-7 John H Palmieri wrote:
> The Sage library doesn't build for me on two OS X 13.5.2 (+ homebrew)
> machines. The tail end of the log:
>
>
The Sage library doesn't build for me on two OS X 13.5.2 (+ homebrew)
machines. The tail end of the log:
building 'sage.libs.ecl' extension
INFO: C compiler: gcc -Wsign-compare -Wunreachable-code -fno-common
-dynamic -DNDEBUG -g -fwrapv -O3 -Wall -isysroot
I tried using mypy, and I also just ran "sage --tox -e pyright", and
neither seems to flag the conflict between the signature "def
signature(self) -> Integer:" and the output, which is some arithmetic with
"len(...)" and hence a Python int. (And both mypy and pyright produce a ton
of warnings,
For a while now, Python has allowed return types to be specified in
signatures:
def f() -> int:
It is my understanding that this doesn't actually do any error-checking or
type-checking — see https://docs.python.org/3/library/typing.html. So this
works without error:
def f() -> float:
On OS X, if I run `./configure && make ptestlong`, I now only see one or
two doctest failures (old ones):
sage -t --long --random-seed=131365868289497726973344316901453636879
src/sage/rings/polynomial/multi_polynomial_ideal.py # Killed due to
segmentation fault
sage -t --long
In principle it seems okay, but to be honest, I don't think I understand
Sage's polynomial rings. It seems like anything goes:
sage: R. = GF(2)[]
sage: S. = R[]
sage: S
sage: R.0 + S.0
x + x
Why am I allowed to construct S?
With your proposed changes, what happens in the
On 8/20/2023 6:55 PM, Tony Jones via cctalk wrote:
On Sun, Aug 20, 2023, 3:44 PM John H. Reinhardt via cctalk <
cctalk@classiccmp.org> wrote:
And so on. Am I looking in the wrong spot?
No but you need to look longer and as I said prices are all over the
place. I see resellers
On 8/20/2023 3:45 PM, Tony Jones via cctalk wrote:
On Sun, Aug 20, 2023, 12:05 PM John H. Reinhardt via cctalk <
cctalk@classiccmp.org> wrote:
I've seen a lot of posts at the EEVblog and it seems I missed possibly the
golden age of 16700 LA by a few years price-wise.
Also unsure wh
://en.wikipedia.org/wiki/MicroVAX#MicroVAX_3800_and_MicroVAX_3900
John H. Reinhardt
On 8/20/2023 3:18 PM, devin davison via cctalk wrote:
Hello All,
I am working to get my two microvax systems working, I have a couple of
microvax 3800 systems.
While I am waiting to get the real hardware going, I would like
On 8/20/2023 2:43 PM, Glen Slick via cctalk wrote:
On Sun, Aug 20, 2023, 12:05 PM John H. Reinhardt via cctalk <
cctalk@classiccmp.org> wrote:
Hello all. I looking around for a Logic Analyzer for doing (mostly) DEC
QBus/UniBus stuff. Being the way I am I want something with enough
wondering is if there is something specific I should be looking for,
or opinions on which LA is more suitable. Or even if there is a different make
of LA to look for.
Thanks in advance for your help
John H. Reinhardt
For what it's worth, the `alarm` function (provided by the cysignals
package) allows for interrupting a command after a given amount of time.
sage: alarm?
Signature: alarm(seconds)
Call signature: alarm(*args, **kwargs)
Type: cython_function_or_method
String form:
File:
> developer's guide -
> https://sagemath-tobias.netlify.app/developer/doctesting.html#the-doctest-fixer
>
> On Friday, August 4, 2023 at 2:45:21 PM UTC-7 John H Palmieri wrote:
>
>> I appreciate the description of the changes in `sage --fixdoctests` in
>> the releas
I appreciate the description of the changes in `sage --fixdoctests` in the
release tour, but are these features described anywhere in Sage's
documentation? I didn't see anything at #35749 or #36024.
On Thursday, August 3, 2023 at 11:31:25 AM UTC-7 Matthias Koeppe wrote:
> On Thursday, August
Looks like it's skipping the files with tags at the top like
# sage.doctest: optional - sage.rings.finite_rings
That is: cardinality.py, ell_number_field.py, heegner.py, hom_frobenius.py,
isogeny_class.py, saturation.py. When I run `./sage -t
src/sage/schemes/elliptic_curves/`, it says
I get the same error when evaluating this integral in Sage with its own
Maxima. (version 5.46.0).
On Sunday, July 16, 2023 at 10:30:53 AM UTC-7 Matthias Koeppe wrote:
> On Sunday, July 16, 2023 at 5:48:00 AM UTC-7 Nasser M. Abbasi wrote:
>
> After some struggle, build sagemath with maxima
IPython comes with various "magic" commands, for example "%ls" which runs
the shell command "ls". The default mode in Sage is "Automagic is ON, %
prefix IS NOT needed for line magics." This means that running "ls" within
Sage does the same thing as running "%ls". So far so good. There are,
I just found this the other day, but I see the update date in in 2014 so it may
not be of use.
http://ftp.zx.net.nz/cgi-bin/archive-mirror
There is some info about libraries under the Storageworks folder.
https://ftp.zx.net.nz/pub/archive/ftp.compaq.com/pub/products/storageworks/
--
John H
nce those are basically the only things I have tinkered
> with.
>
> Can you verify that you do not see any image files in the top level of,
> say:
> local/share/doc/sage/html/en/reference/manifolds/sage/manifolds ?
>
> - Marc
>
> On Wed, Jun 28, 2023 at 3:23 PM John H
By the way, on my machine, local/share/doc/sage are almost identical sizes
in 10.1.beta3 and 10.1.beta4. I don't know what explains the difference
you're seeing.
On Wednesday, June 28, 2023 at 12:51:38 PM UTC-7 John H Palmieri wrote:
> This change should produce only the .svg files:
>
This change should produce only the .svg files:
diff --git a/src/sage_docbuild/conf.py b/src/sage_docbuild/conf.py
index 9b6b37480b..b5d6815c76 100644
--- a/src/sage_docbuild/conf.py
+++ b/src/sage_docbuild/conf.py
@@ -128,7 +128,7 @@ from sage.all_cmdline import *
"""
plot_html_show_formats
I tried making this change (which would affect each ".. PLOT:" directive)
but the documentation failed to build:
diff --git a/src/sage_docbuild/conf.py b/src/sage_docbuild/conf.py
index 9b6b37480b..db33c4b1d6 100644
--- a/src/sage_docbuild/conf.py
+++ b/src/sage_docbuild/conf.py
@@ -115,7 +115,7
I think this should be discussed at sage-devel.
On Wednesday, June 28, 2023 at 8:49:51 AM UTC-7 vdelecroix wrote:
> I agree with Marc that svg is almost always preferable than png for
> graphics : it scales and compresses. Thanks for raising the issue.
>
> Do you have a concrete proposal for
Just do a global search-and-replace: change ".vertices()" to
".vertices(sort=True, key=id)" or ".vertices(sort=True, key=str)".
This is not a new change; the deprecation warning has been in place almost
a year, and there was discussion leading up to it. See
By the way, I see this error message:
TypeError: Vertex labels are not comparable. You must specify an
ordering using parameter ``vertices``
Indeed, this works:
g.adjacency_matrix(vertices=['A', 1])
On Monday, June 26, 2023 at 11:32:56 AM UTC-7 John H Palmieri wrote:
> Please r
Please read the help message for adjaceny_matrix.
g = Graph([('A',1)])
g.adjacency_matrix?
prints, among other things:
* "vertices" -- list (default: "None"); the ordering of the
vertices defining how they should appear in the matrix. By
default, the ordering given by
to you whatever is unclear in
> https://doc.sagemath.org/html/en/developer/index.html in this regard.
> It's also not hard to set up the corresponding tools on cocalc, if for
> one or another reason you can't do the necessary steps on your "real"
> computers.
>
>
>
at 9:28:05 PM UTC-7 Ezra Akresh wrote:
> We have provided an example inside this Cocalc notebook:
> https://cocalc.com/share/public_paths/9a10e579b445d6b489fe88dd6ad4e4375d4f5fba
>
> On Friday, June 16, 2023 at 5:50:24 PM UTC-5 John H Palmieri wrote:
>
>> Can you please pro
Can you please provide an example where things do not work? Are you talking
about manifolds or cell complexes or some other classes?
On Friday, June 16, 2023 at 1:14:32 PM UTC-7 Ezra Akresh wrote:
> In a recent project, my team and I developed functions for the cup product
> and wedge product
On Tuesday, May 30, 2023 at 12:59:54 PM UTC-7 G. M.-S. wrote:
Dima and Matthias,
I completely agree with Nils.
Could you (both of you) take a short vacation from SageMath, please?
More globally, I propose to stop this discussion completely for a few days.
+100
It's time for this
> shouldn't be there
>
> On Sunday, May 28, 2023 at 10:10:23 PM UTC+2 John H Palmieri wrote:
>
>> On OS X: after running `./configure`, I see
>>
>> % git status
>> On branch develop
>> Your branch is up to date with 'upstream/develop'.
>>
&
On OS X: after running `./configure`, I see
% git status
On branch develop
Your branch is up to date with 'upstream/develop'.
Untracked files:
(use "git add ..." to include in what will be committed)
stdin.info
nothing added to commit but untracked files present (use "git add" to track)
On
There was a problem with Singular, but that should have been fixed in
#34851, merged into 10.0.beta0 in February.
(https://github.com/sagemath/sage/issues/34851)
On Tuesday, May 23, 2023 at 1:11:50 PM UTC-7 matthia...@gmail.com wrote:
> On Monday, May 22, 2023 at 11:39:09 PM UTC-7 tdumont
Thank you, Guillermo. I should have said: I'm using OS X 13.3.1 on both
machines where I'm seeing these failures. I created
https://github.com/sagemath/sage/issues/35646 for this.
On Tuesday, May 16, 2023 at 3:35:15 PM UTC-7 list...@gmail.com wrote:
>
> This is on Apple Silicon Macs ("M"
I see the same failures on a laptop with an M2 chip.
On Tuesday, May 16, 2023 at 12:58:56 PM UTC-7 John H Palmieri wrote:
> On an iMac Pro (some Intel chip), the first failure
> (rings/polynomial/multi_polynomial_ideal.py) is also related to giac:
>
> sage: A9=PolynomialRing(QQ,9,
# line 17 ##
sage: B = gb_giac(I.gens()) # random ## line 18 ##
On Monday, May 15, 2023 at 6:05:25 PM UTC-7 Kwankyu Lee wrote:
> On Tuesday, May 16, 2023 at 6:13:03 AM UTC+9 John H Palmieri wrote:
>
> I consistently see these failures on various OS X machines:
>
I consistently see these failures on various OS X machines:
sage -t --long --random-seed=244618093388694547212515065258622925284
src/sage/rings/polynomial/multi_polynomial_ideal.py # 1 doctest failed
sage -t --long --random-seed=244618093388694547212515065258622925284
In principle this should work. See
https://github.com/sagemath/sage/issues/31505 for some relevant
information. Others might have direct experience with it.
On Friday, May 5, 2023 at 11:24:07 AM UTC-7 Louis Deaett wrote:
> I'm interested in Sage development (and contributing some enhancements)
Dear US-based Sage developers,
The Simons Foundation has announced a Scientific Software Research Faculty
Award —
https://www.simonsfoundation.org/grant/scientific-software-research-faculty-award/
— and it might be appropriate for Sage development.
--
John
--
You received this message
On Thursday, April 27, 2023 at 2:54:47 PM UTC-7 Isuru Fernando wrote:
I guess there are several requirements we need
1. Support for all major OS/architecture combinations
2. Easy to build for rare OS/architecture combinations
3. Possible to install as a non-root user
4. Binaries are available
In an attempt to make this less of a religious war and more akin to
something like a rational discussion:
- The status quo is that we include Python3 and gcc. If you want to argue
for their removal, you need to provide evidence that this will not cause
problems for people on supported
While
sage_eval('sin(x)')
does not work,
sage_eval('sin(x)', {'x': x})
does work. sage_eval needs to know the context (which variables have been
defined, etc.) in which to evaluate. I am not an expert, but
sage_eval('sin(x)', locals=locals())
might work pretty reliably, without
This looks like the issue reported at
https://github.com/sagemath/sage/issues/34233.
--
John
On Thursday, April 13, 2023 at 2:13:44 PM UTC-7 Fernando Gouvea wrote:
> That seems right. Plotting x^6/(1-x)^7 shows the error, but x^5/(1-x)^6
> does not. And
>
> .9^6/.1^7 = 5.314411e6
>
"2*1.1" is not a float literal. Note that RR(2.2) does what you want.
On Monday, April 10, 2023 at 1:42:21 PM UTC-7 aw wrote:
> sage version: 9.4
> operating system: fedora 35
>
> float literals passed to realfield can yield wrong answers
>
> example:
>
> RR=RealField(200)
>
> print(RR(1.1))
>
I have found the instructions at
https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md
useful for me, as someone used to the old trac interface.
On Saturday, April 8, 2023 at 1:23:06 PM UTC-7 G. M.-S. wrote:
>
> Thanks Dima and Drew.
>
> I had the very same
Some recent versions of Singular don't seem to work with Sage. You could
try "make distclean" (to start over) and "./configure
--with-system-singular=no" to force Sage to build its own Singular. Then
"make".
On Friday, April 7, 2023 at 2:22:20 PM UTC-7 Eric Majzoub wrote:
> Following the
In lengthy code, you could start with a line like
OnSets = libgap.OnSets
and then in the rest of the code, you could do `g.Stabilizer([1,2],
OnSets)`. That is, predefine whatever you want from libgap, giving each
item a meaningful name, and then use that name in the rest of the code.
On
Would it be a good idea for Sage tarballs, at least the development
versions, to come with `upstream` defined already? With a fresh 10.0.beta6
tarball:
% git remote -v
trac https://github.com/sagemath/sagetrac-mirror.git (fetch)
trac ssh://g...@trac.sagemath.org:/sage.git (push)
Should
they went through
with
>
> make -j1
>
> The usual macOS parallel docbuilder blues, it seems.
>
>
>
> On Tue, 28 Mar 2023, 19:35 John H Palmieri, wrote:
>>
>> I ran "brew upgrade" recently on two different Macs, one Intel and one
Apple
I ran "brew upgrade" recently on two different Macs, one Intel and one
Apple Silicon, and now the Sage documentation fails to build:
[hyperboli] from
>From the ask.sagemath.org answers:
[m.minors(k) for k in range(5)]
is pretty close to what you want: you just have to flatten the list.
On Monday, March 20, 2023 at 3:09:07 PM UTC-7 William Stein wrote:
> This is
>
>
>
Thank you for the reference.
On Tuesday, March 14, 2023 at 3:25:16 PM UTC-7 list...@gmail.com wrote:
>
> This is mentioned here:
> https://github.com/sagemath/sage/issues/35273
>
> Guillermo
>
> On Tue, 14 Mar 2023 at 23:09, John H Palmieri wrote:
>
>> OS X wi
OS X with homebrew packages installed and very recently updated. I'm seeing
some doctest failures: errors with mathematically equivalent answers but
not in the correct form. This is for the following files:
sage -t --long --random-seed=247900869917442955840282482235981848821
See also the installation manual:
https://doc.sagemath.org/html/en/installation/source.html#macos-package-installation.
On Tuesday, March 14, 2023 at 3:45:17 AM UTC-7 Dima Pasechnik wrote:
> Assuming you are on macOS with homebrew installed, get Sage source and run
> ./bootstrap
>
> and then
>
It looks like the graph failures have been reported at
https://github.com/sagemath/sage/issues/35157. Emanuel, are those the ones
you're seeing?
On Sunday, March 5, 2023 at 8:20:30 AM UTC-8 emanuel.c...@gmail.com wrote:
> The resulting 10.0.beta3 passes ptestlong witrh the two permanent
>
e stack...
>
> Le mercredi 1 mars 2023 à 04:24:36 UTC+1, John H Palmieri a écrit :
>
>> I think it's due to https://github.com/sagemath/sage/issues/34547. That
>> ticket was created because with the old behavior in Sage, instance of
>> Octave(), Mathematica(), etc. were cre
I think it's due to https://github.com/sagemath/sage/issues/34547. That
ticket was created because with the old behavior in Sage, instance of
Octave(), Mathematica(), etc. were created when Sage started up, regardless
of the availability of the corresponding software. Once those became lazy
I have been setting MAKE and MAKEFLAGS for a long time, and I have not seen
any difference in the behavior of "make build". If I unset MAKE and
MAKEFLAGS, then it takes longer to build sagelib, as it should.
On Saturday, February 11, 2023 at 11:44:43 AM UTC-8 Nils Bruin wrote:
> On Saturday,
For what it's worth, every now and then I create a virtual linux machine
and build Sage from source using the instructions in the installation
guide, including installing the recommended prerequisite software. It
typically goes smoothly, and it's definitely worth trying on Ubuntu. (I've
done
An ‘interesting’ aside is that in Monterey (12.6.2), a blank window
appears when I click on ‘PDF’ from within the RStudio help system.
Within the R GUI, there is not a problem. In either case, typing
vignette('concordance', package='survival’)
in the command line window works fine. Kevin, does
Some people have had an issue with Singular: the system version is too new.
Using "./configure --with-system-singular=no" (probably after "make
distclean"?) would help, if that's the problem. There is an upgrade ticket
for Singular that has had many isses, but last time I checked, it had a
Can we be proactive and request membership somewhere through GitHub, or do
we have to receive an invitation?
On Wednesday, February 1, 2023 at 3:57:51 PM UTC-8 Andrew wrote:
> Thank you for all of your work on this!
> Andrew
>
> On Thursday, 2 February 2023 at 10:10:01 am UTC+11 Matthias Koeppe
Is there going to be one more round of (presumably automatic) additions to
trac, providing a link from each trac ticket to the corresponding GH issue?
On Monday, January 30, 2023 at 2:06:34 PM UTC-8 dim...@gmail.com wrote:
> On Mon, Jan 30, 2023 at 9:56 PM Kwankyu Lee wrote:
> >
> > On
Patch available: https://trac.sagemath.org/ticket/34935
On Tuesday, January 24, 2023 at 2:47:15 PM UTC-8 John H Palmieri wrote:
> I think Matthias found the answer in the emacs-lisp code (discussion at
> https://trac.sagemath.org/ticket/34547#comment:56).
>
> On Tuesday, January 2
effort to
> understand and *comment* it might be worthwile…
>
> Le mardi 24 janvier 2023 à 23:15:40 UTC+1, John H Palmieri a écrit :
>
>> For reasons I really don't understand, removing these lines from
>> sage.interfaces.all seem to have caused this:
>>
>> -interf
ry 2023 at 17:47:29 UTC+1 John H Palmieri wrote:
>
>> This was one of my guesses because that ticket could have changed global
>> behavior of Sage by changing some imports — most of the tickets made more
>> focused changes. Can you start with 9.8.beta6 and just apply some of
4 January 2023 at 10:21:11 UTC+1 axio...@yahoo.de wrote:
>>
>>> Thank you for this suggestion! I will try with 9.8.beta6 + #33842. I
>>> hope that all dependencies are in the branch.
>>>
>>> Martin
>>>
>>> On Monday, 23 January 2023 at 21:32:
sue indeed. But losing the Emacs interface
>>> is a big hit for me, so I revert to 9.6.beta6 for now.
>>>
>>> Thank you nevertheless !
>>>
>>> Le vendredi 20 janvier 2023 à 22:58:53 UTC+1, John H Palmieri a écrit :
>>>
>>>> In the hope
In the hopes that this will fix it, I opened
https://trac.sagemath.org/ticket/34927.
On Friday, January 20, 2023 at 1:46:02 PM UTC-8 John H Palmieri wrote:
> Does this change fix the fricas.py failure?
>
> diff --git a/src/sage/interfaces/fricas.py b/src/sage/interfaces/fricas.p
Does this change fix the fricas.py failure?
diff --git a/src/sage/interfaces/fricas.py b/src/sage/interfaces/fricas.py
index dc2ce71f26..ceba6f90dc 100644
--- a/src/sage/interfaces/fricas.py
+++ b/src/sage/interfaces/fricas.py
@@ -891,7 +891,7 @@ http://fricas.sourceforge.net.
"""
All of the *_console commands should be fixed by ticket #34547.
On Thursday, January 19, 2023 at 11:45:59 PM UTC-8 trevor...@gmail.com
wrote:
> Something similar seems to happen with `gap_console()` and `gap.console()`.
>
> On Thursday, January 19, 2023 at 5:22:23 PM UTC-6 John H
If you have installed Singular via homebrew, it may be too new for Sage to
handle properly. Try "./configure --with-system-singular=no". (I think this
would be fixed by https://trac.sagemath.org/ticket/34851.)
--
John
On Friday, January 20, 2023 at 7:24:52 AM UTC-8 david@gmail.com wrote:
"mathematica_console()" is available (or at least it should be) when using
Sage from the command-line but not from the notebook. There was a bug, now
fixed in https://trac.sagemath.org/ticket/34547, that meant that this
command was not available when it should have been.
On Thursday, January
"palmieri" and "palmiery" and "jpalmieri" appear (probably from mistakes
with cc entries), and they should all be changed to match my correct trac
name "jhpalmieri" (same as my github id).
On Wednesday, January 18, 2023 at 6:14:16 PM UTC-8 Kwankyu Lee wrote:
> Dear readers,
>
> Attached
It may be (as pointed out on a similar thread in the group sage-devel) that
some of the Debian packages have versions that are too new to be used with
Sage. You could tell Sage to build its own Python, its own Gap, perhaps its
own Singular (if the system one is causing problems):
./configure
any space to improve the computation of MPFR which is used by
> RealField?
>
> John H Palmieri 在 2023年1月6日 星期五凌晨3:01:37 [UTC+8] 的信中寫道：
>
>> One way to speed it up might be to work with RDF or QQ or RLF. The
>> documentation for the generic determinant method says, "Note
One way to speed it up might be to work with RDF or QQ or RLF. The
documentation for the generic determinant method says, "Note that for
matrices over most rings, more sophisticated algorithms can be used."
sage: %time ones_matrix(RDF, 600, 600).determinant()
CPU times: user 78.6 ms, sys: 7.6
ill unable to proceed. Any idea how
> to fix the issue? I have attached logs, config.log, and a text file with
> the 4 packages with errors.
>
> Thank you!
> Alex
>
> On Wednesday, January 4, 2023 at 11:35:39 AM UTC-8 John H Palmieri wrote:
>
>> Many of the errors are discus
Maybe you also need to do "make flit_core" before "make typing_extension".
On Wednesday, January 4, 2023 at 11:35:39 AM UTC-8 John H Palmieri wrote:
> Many of the errors are discussed at https://trac.sagemath.org/ticket/34838.
> You can probably avoid those by runni
Many of the errors are discussed at https://trac.sagemath.org/ticket/34838.
You can probably avoid those by running "make typing_extensions" before
running "make".
The most recent error seems to be for sagelib:
ld: library not found for -lopenblas
I assume that you followed the directions
Your current code has fragments like this:
weighted_load = load_obj(f'./sym.sobj')
print(f'weighted == weighted_load {weighted == weighted_load}')
save(weighted, f'./sym.sobj')
In particular, "sym.sobj" is read before it is written, so 'weighted_load'
will be None. If I put the "save" lines
parallel docbuilding code...)
>
> On Thu, Dec 22, 2022 at 6:06 AM John H Palmieri
> wrote:
> >
> > And it would be great if we could fix it, but I don't know what the
> problem is. I've seen it on both Apple Silicon and on Apple Intel. On the
> Intel machine, when runn
December 21, 2022 at 9:37:48 PM UTC-8 John H Palmieri wrote:
> I've seen this before, and I haven't been able to figure out what triggers
> it. It seems random: try "make doc-clean doc-uninstall && make" and it
> might succeed after a few attempts.
>
> On We
I've seen this before, and I haven't been able to figure out what triggers
it. It seems random: try "make doc-clean doc-uninstall && make" and it
might succeed after a few attempts.
On Wednesday, December 21, 2022 at 3:13:10 PM UTC-8 list...@gmail.com wrote:
>
> Help needed.
>
> This is on
What OS? I'm guessing Mac OS, in which case you need the fix at
https://trac.sagemath.org/ticket/34658, or build 9.8.beta3 or wait for a
later beta release that includes the fix.
--
John
On Saturday, November 26, 2022 at 12:40:30 PM UTC-8 beingn...@gmail.com
wrote:
> Dear SageMath,
>
>
, November 22, 2022 at 7:36:28 PM UTC-8 Kenji Iohara wrote:
>
>> With my Mac OS 13.0.1, with Intel Core i5, and several packages with
>> Homebrew, I have a problem with downloading
>>
>>
>> * package: numpy-1.23.5
>> last build time: Nov 23 04:33
&
th.org/ticket/34658, please test
>
>
> On Tuesday, November 22, 2022 at 10:34:52 AM UTC-8 John H Palmieri wrote:
>
>> scipy fails to build for me (OS X 13.0.1, Intel, with various homebrew
>> packages, Sage built from a new tarball):
>>
>> Successfu
scipy fails to build for me (OS X 13.0.1, Intel, with various homebrew
packages, Sage built from a new tarball):
Successfully built scipy
WARNING: Skipping scipy as it is not installed.
Using pip 22.3 from
You can also do `list(S)`, or depending on what you're doing it might be
better to iterate over its elements, as Emmanuel wrote: `for u in S...`
On Sunday, November 20, 2022 at 8:54:25 AM UTC-8 gauri...@gmail.com wrote:
> Oh wow! That was easy!
>
> Thanks so much!
> G
>
> On Sun, Nov 20,
Please check whether https://trac.sagemath.org/ticket/34741 fixes the
problem.
On Saturday, November 5, 2022 at 2:47:41 PM UTC-7 Kenji Iohara wrote:
> It might be better adding test.log
>
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To
I think the use of Tachyon instead of Jmol must be particular to that
setup. When I build the docs with #34730, it looks the same as in the
develop branch, same as on sagemath.org.
On Wednesday, November 9, 2022 at 1:24:38 PM UTC-8 Eric Gourgoulhon wrote:
> PS: the loss of text3d is
Brunswick
that might want it for themselves?
Ebay listing https://www.ebay.com/itm/334615827742?
--
John H. Reinhardt
Are these failures because of warning messages like
ld: warning: dylib (...) was built for newer macOS version (13.0) than
being linked (12.3)
On Friday, November 4, 2022 at 5:08:27 AM UTC-7 Kenji Iohara wrote:
> I have recompiled it with Mac OS 13.0, with Intel Core i5, Xcode 14.1 with
markings on the other side, on the top was only the X2 and the value.
You might have to remove it just to be certain that it is a RIFA, but the top
lettering and the overall look point in that direction.
--
John H. Reinhardt
101 - 200 of 8727 matches
Mail list logo
