Also addressed in https://github.com/sagemath/binary-pkg/pull/29
On Friday, September 3, 2021 at 10:15:02 AM UTC-7 Matthias Koeppe wrote:
> Thanks, I've noted this in
> https://wiki.sagemath.org/ReleaseTours/sage-9.4#Availability_as_binaries_and_in_distributions
>
> On Friday, September 3,
I believe that most of the traffic these days is on sage-support and
sage-devel, rather than the more specialized groups. Feel free to post
questions about Sage's algebra capabilities here.
On Monday, August 23, 2021 at 8:03:33 PM UTC-7 H wrote:
> On August 23, 2021 7:18:16 PM EDT, David
(I'm not sure where this comes from, since searching for "givaro" on
brew.sh comes up empty.)
On Wednesday, August 18, 2021 at 6:48:10 PM UTC-7 John H Palmieri wrote:
> You could try uninstalling homebrew's givaro and/or use `./configure
> --with-system-givaro=no` to force S
You could try uninstalling homebrew's givaro and/or use `./configure
--with-system-givaro=no` to force Sage to build its own givaro.
On Wednesday, August 18, 2021 at 4:45:54 PM UTC-7 Brian Sun wrote:
> I ran the two commands (and also uninstalled Macaulay2 and the copy of
> fflas-ffpack using
I think that more math of almost any sort would be great to add to Sage.
Improving the knot and link capabilities would be great!
John
On Monday, August 2, 2021 at 12:59:13 PM UTC-7 Calvin Godfrey wrote:
> First of all, I apologize if this isn't the right place to ask this. I
> spent ages
I think that we should prefer tuples to lists when that is appropriate,
lists to tuples when that is appropriate. Python has both types for good
reasons, I think, and I don't see why we should globally recommend one over
the other.
On Wednesday, July 14, 2021 at 7:21:48 PM UTC-7 Kwankyu Lee
Does anyone have experience working with graphic designers? How much would
it cost to get a logo designed by a professional?
On Sunday, July 4, 2021 at 10:27:07 AM UTC-7 Nils Bruin wrote:
> Oh my, those logos are absolutely atrocious! Never mind the translation:
> the text is clipped to
After seeing the message "Pytest is not installed, skip checking tests that
rely on it" a number of times, I decided to install it. There were two
files with resulting doctest failures:
sage -t --long --warn-long 131.5 --random-seed=0 src/sage/doctest/test.py
# 7 doctests failed
sage -t
It builds for me on OS X Big Sur and I see no new doctest failures, but the
PDF documentation doesn't build. When building it/a_tour_of_sage, I see
this error:
! Package inputenc Error: Unicode character リ (U+30EA)
Indeed, the file
As pointed out in another message, ask.sagemath.org is down. Can anyone
help?
--
John
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Another option might have been to preparse separately (using "sage
-preparse matp11n2.sage" at the shell prompt) and then load the resulting
Python file.
John
On Friday, April 2, 2021 at 12:02:38 PM UTC-7 Luis Finotti wrote:
> The solution I found was to increase the recursion limit: I did
What happens if you install into another location, for example the Desktop?
On Sunday, March 28, 2021 at 9:26:28 AM UTC-7 Anscari wrote:
> I installed the app you suggested but when I open jupyter I find too many
> bugs. I am not even able to access the jupyter folder created using
> previous
Dear all,
You should be aware that ticket #31409
(https://trac.sagemath.org/ticket/31409) intends to downgrade R to an
optional package because of difficulties building it on Cygwin. Just
letting you know in case you care about R being part of Sage and/or you
have ideas about how to fix the
I just noticed something which has been happening for all of the 9.3 beta
releases, maybe before that. In the dochtml.log file, I see the message
Help file /Applications/usr/share/giac/doc/fr/aide_cas not found
(This is on OS X.) That's a strange path — there is no /Applications/usr —
so
finally :-) (not sure bug or feature)
>>
>> well,
>>
>> make build
>>
>> works
>>
>> On Wed, 3 Feb 2021, 17:05 John H Palmieri, wrote:
>>
>>> I'm not sure when it happened, but with the latest beta, I see
>>>
>>>
I'm not sure when it happened, but with the latest beta, I see
% ./sage -b
Makefile:25: *** This Makefile needs to be invoked by build/make/install.
Stop.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop
ket/30589
>
> On Monday, February 1, 2021 at 9:45:37 PM UTC-5 John H Palmieri wrote:
>
>> On OS X Big Sur (intel), as of the most recent Xcode and homebrew, I am
>> currently unable to build Sage with either homebrew's Python or with
>> `./configure --with-system-python3
On OS X Big Sur (intel), as of the most recent Xcode and homebrew, I am
currently unable to build Sage with either homebrew's Python or with
`./configure --with-system-python3=no`.
- With homebrew's Python, actually Sage builds but the documentation does
not (similar problems on both Big Sur
ot;This Makefile needs to be invoked by 'build/make/install'". If I set the
> parameter
> SAGEPKGCONFIG then it works, but I shouldn't need to do that.
>
> Dan
>
> On Friday, January 22, 2021 at 5:16:28 PM UTC-8 John H Palmieri wrote:
>
>> Great, I'm glad to
t; On Friday, January 22, 2021 at 3:21:10 PM UTC-8 John H Palmieri wrote:
>
>> I literally meant "merge that [the branch from #31183] into the develop
>> branch" (or vice versa), not just use the branch from #31183. The develop
>> branch has some crucial pieces for bu
y)
> into
> the scipy-big-sur branch and that fails to build in scipy again.
>
> Dan
>
> On Thursday, January 21, 2021 at 8:09:14 PM UTC-8 John H Palmieri wrote:
>
>> Ticket 31183 (https://trac.sagemath.org/ticket/31183) should fix that.
>> Merging that into the develop b
Ticket 31183 (https://trac.sagemath.org/ticket/31183) should fix that.
Merging that into the develop branch works for me.
--
John
On Thursday, January 21, 2021 at 8:03:55 PM UTC-8 dwb...@gmail.com wrote:
> I'm unable to build the develop branch since upgrading my iMac to Big Sur.
> I have
h an
error that I don't know how to fix, as reported at
https://trac.sagemath.org/ticket/30651.
On Monday, December 28, 2020 at 11:10:36 AM UTC-8 John H Palmieri wrote:
> I've been having problems with computers running Mac OS for several Sage
> releases now. With OS X 10.15.7
I've been having problems with computers running Mac OS for several Sage
releases now. With OS X 10.15.7 and a pretty full homebrew installation,
cypari fails:
cypari2/gen.c:23742:70: error: too many arguments to function call,
expected 3, have 4
__pyx_v__ret = asympnum0(__pyx_v__expr,
The short answer is that Sage is designed for (among others) research
mathematicians, who may not have the interest or inclination to learn how
to install lots of system packages. So from the beginning it included as
many components as possible. Years ago the presence of MacPorts and other
For what it's worth, I was able to build Sage on 11.0 using homebrew, but
since the upgrade to 11.1, the build fails for me. Discussion at #30651
(started at #30589, but should be continued at #30651).
On Monday, December 21, 2020 at 2:46:00 PM UTC-8 Samuel Lelievre wrote:
> Supporting macOS
, 2020 at 4:02:49 PM UTC-8 John H Palmieri wrote:
> Maybe something is going wrong with using the homebrew version of Python —
> some conflict somewhere — so could you try
>
> make distclean
> ./configure --with-system-python3=no
> make
>
> (I'm having different problems with t
Maybe something is going wrong with using the homebrew version of Python —
some conflict somewhere — so could you try
make distclean
./configure --with-system-python3=no
make
(I'm having different problems with the system python: see my posts about
MACOSX_DEPLOYMENT_TARGET.)
--
John
On
I am having problems building Sage with a recently updated homebrew Python
3.9 on OS X Big Sur, apparently because it sets MACOSX_DEPLOYMENT_TARGET to
11. (Insert Spinal Tap joke here.) If you run `brew update` on Big Sur, I'm
guessing that you will run into this.
- There is a problem because
Dima is suggesting the command locale.setlocale(locale.LC_ALL,''), where
just before the parenthesis should be two single quotes. No quotes after
the parenthesis. Or if you prefer: locale.setlocale(locale.LC_ALL,"") with
two double quotes just before the parenthesis.
On Thursday, November 26,
Is it possible to create a binary distribution that relies on a system
Python 3? Those may already be built with ssl support.
On Sunday, November 22, 2020 at 11:24:45 AM UTC-8 watso...@gmail.com wrote:
>
> Right now pip doesn't work in the binary distributions due to the absence
> of the ssl
I was hoping that it might be missing dependencies when building sagenb,
but when I tried this, it didn't help. Maybe something this will work:
./configure --with-python=2 --enable-sagenb=yes
--enable-flask_autoindex=yes --enable-flask_babel=yes --enable-flask=yes
You can probably eliminate some of the doctest errors with the following
hack, which may not be the right way to proceed, but at least for me it
allows doctesting to complete. Some of your other errors may be caused by
using Python 3.9, and people are working on fixing those.
diff --git
n, Nov 16, 2020 at 6:19 PM John H Palmieri
> wrote:
> >
> > In my experience, homebrew's "ntl" package can lead to problems when
> building Sage, so if possible, try deleting it.
>
> Why?! It all works, if you install the recommended by ./configure
> list
In my experience, homebrew's "ntl" package can lead to problems when
building Sage, so if possible, try deleting it. I have these packages:
% brew list
autoconfghcjanssonmpcppl
automakeghostscriptjpegmpfipython@3.8
bdw-gcgit
On the latest "release candidate" for OS X Big Sur + corresponding Xcode
and command line tools, Sage now builds for me. With various homebrew
packages installed, I can run "./configure" and "make", and the build
succeeds. There are a number of doctest failures with the message
ld:
I don't think it's a Python problem, but rather a Jupyter problem. It used
to be the case, and perhaps still is, that we could not distribute ssl
because of licensing issues, so when we build our own Python, it may have
broken ssl support. This has been true for a long time, so I think that
;>>>>
>>>>>>
>>>>>> Thank you for helping me.
>>>>>>
>>>>>> I followed the instructions at the end of ./configure output (brew
>>>>>> install ...)
>>>>>>
>>>>>> I get l
On Tuesday, November 3, 2020 at 11:30:54 PM UTC-8, Dima Pasechnik wrote:
>
> As far as building from source is concerned, I'd recommend using
> Homebrew, instead of trying
> to build most packages from scratch (as it is the case if you don't use
> it).
> Please pay attention that you need to
On Monday, November 2, 2020 at 1:38:37 PM UTC-8, Dima Pasechnik wrote:
>
>
>
> On Mon, 2 Nov 2020, 21:36 David Coudert, > wrote:
>
>> So should we open a ticket to add it and hope it will be included in next
>> beta or is there a trick to force the installation of giac ?
>>
>
"make giac"
On Sunday, November 1, 2020 at 7:29:31 AM UTC-8, David Coudert wrote:
>
> Hello,
>
> I’m unable to build beta0 on macOS 10.15.7 :(
>
> I did:
> $ make distclean
> $ ./bootstrap
> $ source .homebrew-build-env
> $ ./configure
>
> Then, I followed the recommandation and did:
> $ brew install pandoc
The relevant ticket is https://trac.sagemath.org/ticket/30720, which has
not yet been applied. (I'm guessing that this is because the problem was
fixed recently and gap_packages is an optional package, so the ticket did
not have super high priority.)
--
John
On Tuesday, October 27, 2020 at
No, I do not believe so.
On Thursday, October 15, 2020 at 10:22:36 AM UTC-7, Linden Disney wrote:
>
> I am just starting a project involving persistent homology, did anything
> end up happening with this?
>
> On Wednesday, September 13, 2017 at 1:55:30 AM UTC+1 slelievre wrote:
>
>> Tue
.
On Wednesday, October 7, 2020 at 12:55:50 PM UTC-7, David Joyner wrote:
>
>
>
> On Wed, Oct 7, 2020 at 1:06 PM John H Palmieri > wrote:
>
>> Building Sage on Big Sur is being tracked at
>> https://trac.sagemath.org/ticket/30651; see also
>> https://trac.sagemath.or
Building Sage on Big Sur is being tracked at
https://trac.sagemath.org/ticket/30651; see also
https://trac.sagemath.org/ticket/30494. Do you have homebrew installed, and
if so, which packages? You could try forcing Sage to build its own zlib,
for example, to try to get Sage's Python to find
That's funny, I just hit the same problem. The solution is to run 'make
toolchain' first. (This should happen automatically when you run make,
which is why that succeeds.) See https://trac.sagemath.org/ticket/30721.
On Sunday, October 4, 2020 at 8:01:18 PM UTC-7, Zachary Scherr wrote:
>
> In
Please also provide the top-level config.log.
On Thursday, October 1, 2020 at 5:11:01 AM UTC-7, Kenji Iohara wrote:
>
> On OS X.15.7 with Xcode 12, I couldn’t compile
>
>pynac-0.7.26.sage-2020-04-03.p0
>
> . Here is its log-file.
>
--
You received this message because you are
Builds for me on OS X 10.15.7 (Catalina) with Xcode 12, both with a full
homebrew installation, and then also using only some homebrew packages:
./configure --with-system-readline=no --with-system-openblas=no
--with-system-r=no --with-system-gsl-no --with-system-suitesparse=no
On
On Monday, September 21, 2020 at 10:32:05 PM UTC-7, John H Palmieri wrote:
>
> For openblas and readline, I suggest using homebrew's versions of those
> packages. For symmetrica, there is an upgrade at
> https://trac.sagemath.org/ticket/29061 which seems to fix the problem.
> F
For openblas and readline, I suggest using homebrew's versions of those
packages. For symmetrica, there is an upgrade at
https://trac.sagemath.org/ticket/29061 which seems to fix the problem. For
scipy (which you probably haven't reached in your build and which will
probably fail when you do),
-k, I get the failure building
>
> gf2x
> openblas
> readline
> ecm
> symmetrica
> rubiks
>
>
>
>
>
> 2020/09/17 19:54、John H Palmieri >のメール:
>
> See also https://trac.sagemath.org/ticket/30494
>
>
> On Thursday, September 17, 2020 at 10:36:06
See also https://trac.sagemath.org/ticket/30494
On Thursday, September 17, 2020 at 10:36:06 AM UTC-7, John H Palmieri wrote:
>
> With the newly released Xcode 12, if I run "make -k", I get failures
> building
>
> ecl
> ecm
> gf2x
> rubiks (which is about to be
With the newly released Xcode 12, if I run "make -k", I get failures
building
ecl
ecm
gf2x
rubiks (which is about to be downgraded to optional, so I don't care)
scipy
symmetrica
The good news is that 141 other packages built successfully. See also the
thread
I have a Sage policy proposal:
- For any new standard Sage package PKG, we strongly recommend, require if
at all possible, that the package comes with an spkg-configure.m4 script in
build/pkgs/PKG. There should also be a directory build/pkgs/PKG/distros.
Neither the spkg-configure.m4 file nor
; It would be nice to have a different entry point to Sage that has
> *dramatically* less imported by default. By I don't think it should be the
> default, just because of backward compatibility.
>
> William
>
> On Tuesday, September 8, 2020 at 12:35:38 AM UTC-7 Nils Bruin
clean is necessary. I tried both to no
> avail. Thank you anyway!
>
> John H Palmieri schrieb am Montag, 7. September 2020 um 20:29:07 UTC+2:
>
>>
>>
>> On Monday, September 7, 2020 at 11:27:15 AM UTC-7, John H Palmieri wrote:
>>>
>>> You coul
On Monday, September 7, 2020 at 11:27:15 AM UTC-7, John H Palmieri wrote:
>
> You could do
>
> ./configure --enable-openssl=yes
> make
>
> or atlernatively
>
> make openssl
> make
>
And the second of these (make openssl; make) might be better because it
sh
You could do
./configure --enable-openssl=yes
make
or atlernatively
make openssl
make
On Monday, September 7, 2020 at 11:09:07 AM UTC-7, Martin R wrote:
>
> unfortunately, no.
>
> What I don't quite understand: I can do sage -i openssl only *after* I
> built sage, but python3 is built at the
On Friday, September 4, 2020 at 9:23:30 AM UTC-7, Dima Pasechnik wrote:
>
> On Fri, Sep 4, 2020 at 4:31 PM John H Palmieri > wrote:
> >
> >
> >
> > On Friday, September 4, 2020 at 7:14:24 AM UTC-7, Dima Pasechnik wrote:
> >>
> >>
> &g
On Friday, September 4, 2020 at 7:02:27 AM UTC-7, tobia...@gmx.de wrote:
>
>
> Hi everybody,
>
> I'm currently in the progress of cleaning up my code implementing
> symplectic structures in sage. While doing so, I noticed that there are a
> lot of doctests in the existing code that test rather
On Friday, September 4, 2020 at 7:14:24 AM UTC-7, Dima Pasechnik wrote:
>
>
>
> On Fri, Sep 4, 2020 at 12:55 PM Szabolcs Horvát > wrote:
>
> > Thanks for the response. I do have boost installed in
> /opt/local/include, through MacPorts, but I remove MacPorts from the PATH
> before building
indicate that the configure script is confused about cross compiling
> to a different architecture.
>
>
> On Tuesday, September 1, 2020 at 9:59:59 PM UTC-7, John H Palmieri wrote:
>>
>>
>>
>> On Tuesday, September 1, 2020 at 9:52:37 PM UTC-7 Matthias Koeppe wrote:
On Tuesday, September 1, 2020 at 9:52:37 PM UTC-7 Matthias Koeppe wrote:
> On Tuesday, September 1, 2020 at 8:59:14 PM UTC-7, John H Palmieri wrote:
>
>> If I do install Python 3.7, then gf2x and ecm both fail to build. The
>> gf2x log file says "configure: error: Can
There is a ticket (https://trac.sagemath.org/ticket/25383) about removing
some Sage functions from the global namespace, which I think is a good
idea. But Sage also imports some Python modules:
- os
- sys
- operator
- math
- warnings
Should we keep all of these? Remove all? Keep some?
--
hout underscore."
On Tuesday, September 1, 2020 at 8:38:47 PM UTC-7 John H Palmieri wrote:
> I've been trying to build on Big Sur, too. I removed the
> MACOSX_DEPLOYMENT_TARGET lines from sage-env, but the Python build still
> fails. The log file is attached. Any suggestions (besi
I've been trying to build on Big Sur, too. I removed the
MACOSX_DEPLOYMENT_TARGET lines from sage-env, but the Python build still
fails. The log file is attached. Any suggestions (besides installing a
different system version of Python)?
John
On Saturday, August 22, 2020 at 3:44:01 PM UTC-7
See
https://math.stackexchange.com/questions/3802874/does-isomorphic-mathbb-q-cohomology-implies-isomorphic-mathbb-z-cohomology/3803623#3803623
Can someone who knows the mathematics decide whether this is an issue that
needs to be fixed, or whether the documentation could be clarified?
--
On Friday, August 21, 2020 at 1:37:21 PM UTC-7, Markus Wageringel wrote:
>
> With Neovim as editor, the same warning appears in its builtin terminal,
> followed by some error messages that break the REPL. Luckily, upgrading
> Neovim from 0.2.2 to 0.4.3 fixed it on my end.
>
Does
On Thursday, August 13, 2020 at 12:24:05 PM UTC-7, Dima Pasechnik wrote:
>
>
>
> On Thu, 13 Aug 2020, 20:03 John H Palmieri, > wrote:
>
>>
>>
>> On Thursday, August 13, 2020 at 11:44:59 AM UTC-7, Samuel Lelievre wrote:
>>>
>>> I opened
On Thursday, August 13, 2020 at 11:44:59 AM UTC-7, Samuel Lelievre wrote:
>
> I opened a ticket for the issue reported by John:
>
> - Fix building html documentation on macOS
> https://trac.sagemath.org/ticket/30351
>
> I tried applying #30345 but the problem persisted.
> Then I realised Dima
What happens if you do "make doc-clean; make"?
On Thursday, August 13, 2020 at 12:36:42 AM UTC-7, David Coudert wrote:
>
> on my side, incremental build from beta7 (including documentation) on OSX
> went well.
>
> Le 13 août 2020 à 07:35, John H Palmieri > a écri
ert > wrote:
> >
> > on my side, incremental build from beta7 (including documentation) on
> OSX went well.
> >
> > Le 13 août 2020 à 07:35, John H Palmieri > a écrit :
> >
> > I'm having a problem with this on OS X: both with an incremental u
I'm having a problem with this on OS X: both with an incremental upgrade
(after doing "make doc-clean") and a build from scratch, the build hangs
during the docbuilding stage. If I manually build "constructions" and
"thematic_tutorials" with "sage --docbuild constructions html" etc., the
build
:38:00 UTC+2, John H Palmieri a écrit :
>>
>> It's version 26.3. I also just quit emacs and restarted, and now I'm
>> having the same problems you were having. Modifying 'src/bin/sage' to
>> accept a '--simple-prompt'
>>
>
> How do you do that ? Care
; John, what is your current emacs version ?
>
>
>
> Le mardi 11 août 2020 18:26:04 UTC+2, John H Palmieri a écrit :
>>
>> I had no experience with sage-shell-mode until about 5 minutes ago, but
>> it works for me, except for some weird artifacts when it reprints
I had no experience with sage-shell-mode until about 5 minutes ago, but it
works for me, except for some weird artifacts when it reprints what I typed
at the command line:
┌┐
│ SageMath version 9.2.beta8, Release Date:
Running "make build" should be a good replacement.
On Saturday, August 1, 2020 at 2:13:02 PM UTC-7, Chase Meadors wrote:
>
> Is there an easy workaround for this on until the fix is merged? e.g. how
> can I accomplish the same thing as "sage -b"? I'm on beta6 by the way.
>
> On Saturday, July
On Thursday, July 23, 2020 at 9:31:07 AM UTC-7, Matthias Koeppe wrote:
>
> On Thursday, July 23, 2020 at 3:13:22 AM UTC-7, Emmanuel Charpentier wrote:
>>
>> The install-script() utility did install gap and maxima scripts invoking
>> sage with the relevant switches and arguments. However, it did
r the user, this means in particular that when
>> constructing the zero element, its degree must be given:
>>
>> sage: A = SteenrodAlgebra(p=2)
>> sage: z = A.zero(degree=2)
>> sage: Sq(1)*Sq(1) == z
>> True
>> sage: Sq(2)*Sq(1
a to zero elements, and
> change the behaviour of degree() such that it raises an exception only for
> inhomogeneous elements.
>
> I hope I have clearified that I am not seeking a strange new definition of
> graded module or algebra, and that I am merely wanting to discuss the
> possibi
allow nonhomogeneous elements? That could be another way
to simplify things.
- John
On Saturday, July 18, 2020 at 3:28:56 PM UTC-7, Sverre Lunøe-Nielsen wrote:
>
>
> On Saturday, July 18, 2020 at 11:31:43 PM UTC+2, John H Palmieri wrote:
>>
>> In any case where the degre
On Saturday, July 18, 2020 at 2:31:01 AM UTC-7, Sverre Lunøe-Nielsen wrote:
>
> Dear list,
>
> I have been involved in preparing a package by M. Catanzaro and R. Bruner
> lately, which implements finitely presented modules over the mod `p`
> Steenrod algebra.
>
> We have encountered a conflict
Does IPython have a preparser?
On Thursday, July 9, 2020 at 11:43:36 PM UTC-7, Kwankyu wrote:
>
> Because of the preparser?
>
> On Thursday, July 2, 2020 at 9:19:58 AM UTC+9 John H Palmieri wrote:
>
>>
>>
>> On Wednesday, July 1, 2020 at 4:39:1
On Tuesday, June 30, 2020 at 11:13:11 AM UTC-7, John H Palmieri wrote:
>
>
>
> On Tuesday, June 30, 2020 at 4:01:48 AM UTC-7, Matthias Geier wrote:
>>
>> Hi John and Jörg (and everyone else).
>>
>> This appeared in version 3.1.0 and has already been reported
On Wednesday, July 1, 2020 at 4:39:12 PM UTC-7, John H Palmieri wrote:
>
>
>
> On Wednesday, July 1, 2020 at 2:22:49 PM UTC-7, Antonio Rojas wrote:
>>
>>
>>
>> El miércoles, 1 de julio de 2020, 21:06:43 (UTC+2), John H Palmieri
>> escribió:
>>>
On Wednesday, July 1, 2020 at 2:22:49 PM UTC-7, Antonio Rojas wrote:
>
>
>
> El miércoles, 1 de julio de 2020, 21:06:43 (UTC+2), John H Palmieri
> escribió:
>>
>>
>> Why so many deprecation warnings? I think they're coming from plain
>> Python
This puzzles me: evaluating '\i' in Python 3 just gives '\i'. Same with
IPython. Evaluating it in Sage prints many warning messages: the following
is from a fresh Sage session, and I only evaluated '\i' once, despite the
appearance:
% sage
On Tuesday, June 30, 2020 at 4:01:48 AM UTC-7, Matthias Geier wrote:
>
> Hi John and Jörg (and everyone else).
>
> This appeared in version 3.1.0 and has already been reported at
> https://github.com/sphinx-doc/sphinx/issues/7838.
>
> > I had postponed the task of debugging that particular
It looks to me like spacing for bulleted lists changed in html builds:
there is more space between lines in bulleted lists with 3.1.1 as compared
to 3.0.4. I didn't see anything in the change log about it; does anyone
else see this? I see this with `sphinx-quickstart` and a file `index.rst`
According to wikipedia, graphs.CirculantGraph(n, [j_1, j_2, ...]) is
connected if and only if gcd(n, j_1, j_2, ...) = 1. In this case, the gcd
is 2. If Sage's definition is correct, it's defined as having 10 vertices,
and vertex i is connected to vertices i+2, i-2, i+4, i-4, then even
vertices
Don't use SAGE_CHECK=yes, or at least disable testing for the nose package:
it is known to fail its test suite. (See
https://trac.sagemath.org/ticket/28727, for example.) If you want to keep
SAGE_CHECK=yes in general, then temporarily turn it off, install nose (with
`sage -i nose`), and then
When I follow the directions at
https://doc.sagemath.org/html/en/installation/conda.html#sec-installation-conda
for installing via conda, it seems that the Sage documentation is not
built, and furthermore, it is not clear to me how to build it. Am I missing
something?
See also
Hi Travis,
Can you add a command to `latex_elements['preamble']` in
src/sage/docs/conf.py`? There are a lot of unicode characters defined there
already. \DeclareUnicodeCharacter{26AC}{\circ} or something like that?
On Tuesday, June 2, 2020 at 8:24:52 PM UTC-7, Travis Scrimshaw wrote:
>
> Hi
On Monday, June 1, 2020 at 6:39:11 PM UTC-7, Zachary Scherr wrote:
>
> Hi Dima,
>
>It looks like both were already linked but I ended up reinstalling them
> and everything worked, thank you so much.
>
> In general, do you recommend installing libraries like flint from
>
Did you follow the suggestion at the end of running 'configure'?
# To automatically take care of homebrew messages regarding
# keg-only packages for the current shell session:
$ source /Applications/sage/.homebrew-build-env
The plan, by the way, is to eventually require running `./configure`
It seems that over 80% of the files in the Sage library have lines longer
than 80 characters, and about 50% of files have lines in doctests which are
longer than 80 characters.
On Saturday, May 30, 2020 at 9:14:59 AM UTC-7, John H Palmieri wrote:
>
> Lines should be shorter than 80 char
Just for kicks, I counted the number of .py and .pyx files in the Sage
library, and then counted the ones with lines longer than 80 characters in
their docstrings/doctests. 84% of them had such lines.
On Saturday, May 30, 2020 at 9:14:59 AM UTC-7, John H Palmieri wrote:
>
> Lines
Lines should be shorter than 80 characters when possible. If it isn't
possible because it will cause confusion, break a doctest, make a doctest
unhelpful, etc., then you can make an exception. There are plenty of
exceptions in the Sage library already, for example
The glpk test failures are being discussed at
https://trac.sagemath.org/ticket/29493.
On Friday, May 29, 2020 at 1:19:51 PM UTC-7, Andy Howell wrote:
>
> I originally sent this to sage-release when 9.1 was released. I see the
> same test failures under 9.2.beta0. I didn't see a way to make
The particular ticket in question deals with matplotlib, which has Python
as a dependency, so I think we can safely build with "Sage's Python 3",
which should be at least 3.6. If we can accommodate older version of Python
for the rest of the Sage build — and I think we can, given the current
301 - 400 of 2201 matches
Mail list logo
