I just set SAGE_CHECK=yes and tried to build Sage on several platforms: OS
X and a virtual machine running Ubuntu. Summary:
Failed on both:
- gap: looks like some sort of string-vs-bytes problem
(https://trac.sagemath.org/ticket/28728)
- cvxopt: fails with a Python 3 build, hangs (at least on
I created https://trac.sagemath.org/ticket/28721 to add documentation for
these to the developer's guide. Needs review.
John
On Thursday, November 7, 2019 at 8:27:32 AM UTC-8, John H Palmieri wrote:
>
> These shell functions are defined and documented in
> SAGE_ROOT/build/bin/
These shell functions are defined and documented in
SAGE_ROOT/build/bin/sage-dist-helpers. In my opinion they should also be
documented in the developer's guide, but they don't seem to be.
On Thursday, November 7, 2019 at 6:35:05 AM UTC-8, Simon King wrote:
>
> Hi Dima,
>
> On 2019-11-06,
Simon, you should look at the json file for p_group_cohomology to see if it
contains all of the installed files, or if indeed some are not listed. If
everything is there, there is no need to split it into two packages, unless
I'm missing something.
On Wednesday, November 6, 2019 at 9:33:04
If you want to build Sage for use with Python 3, you should do
$ make distclean
$ ./configure --with-python=3
$ make
Where does this fail for you?
On Monday, November 4, 2019 at 8:21:04 AM UTC-8, Александр Ватузов wrote:
>
> No, I am building sage only for using it with python3. So I need to
lled xcode from the
> appsrtore I am using the latest versions av I am using:
>
> ProductName:Mac OS X
> ProductVersion:10.15.1
> BuildVersion:19B88
> Xcode 11.2
> Build version 11B52
>
> Andrew
>
>
>
>
> On Saturday, 2 November 2019 05:45:
Since trac #28426 (merged pretty recently), when building with Python 3, we
do not build Python 2. Before that, we always built both.
On Sunday, November 3, 2019 at 12:57:02 PM UTC-8, Dima Pasechnik wrote:
>
> I am surprised we still even build python2 by default. Isn't it an
> optional
/28687: change scons from optional to
experimental. I thought briefly of trying to upgrade it instead, but I
don't really care about the package, so someone else who is actually
interested will have to do that.
John
On Friday, November 1, 2019 at 1:27:34 PM UTC-7, John H Palmieri wrote
Note that "sage --sws2rst ..." relies on sagenb, and therefore will only
work with Sage built with Python 2.
In any case, https://trac.sagemath.org/ticket/28685 upgrades to
beautifulsoup4, which is compatible with Python 3.
On Friday, November 1, 2019 at 3:43:32 AM UTC-7, kcrisman wrote:
>
>
I just upgraded a different machine to Catalina. This one didn't have Xcode
or homebrew installed beforehand, so I installed Xcode, its command-line
tools, and homebrew's gcc. Then I built Sage and it worked. I have now
installed a bunch of other homebrew packages relevant to Sage, and the
If you have the time, could you try uninstalling Xcode and then
reinstalling it? You might also try uninstalling and reinstalling
homebrew's gcc and any other homebrew components that are relevant to Sage.
There may be some remnants of previously installed software that is somehow
interfering.
09:58 Scalar-i40 JobId 28: Spooling data again ...
In my opinion, the fact that the spooler is working and doing it's job
isn't something that needs to be logged. Knowing what file is currently
being read would be nice.
Thanks in Advance,
--
Thanks,
John H. Nyhuis
Desk: (206)-685-8334
jnyh
I tried building several version of gfortran by hand on 10.15, but I
couldn't succeed, whereas I could with 10.14. I didn't try just upgrading
Sage's gfortran/gcc package to 9.x.
On Wednesday, October 30, 2019 at 3:21:58 PM UTC-7, François Bissey wrote:
>
> I suspect gcc/gfortran shipped with
I also had problems with Sage's gfortran package with OS X Catalina. I
instead installed homebrew (https://brew.sh), and used homebrew to install
their gcc package. This should install gfortran, which Sage will find as
part of its configure process, thereby bypassing Sage's gfortran package.
hmmm, I thought := assigned a key just like +=, except := locked it so
it could not be changed later. Am I misunderstanding the man page for udev?
Thanks,
John H. Nyhuis
Desk: (206)-685-8334
jnyh...@uw.edu
Box 359461, 15th floor, 106
On 10/29/2019 4:31 PM, Leon Fauster via CentOS wrote:
>
Thanks, I did catch the mistype (after IU posted). Still no match with
the typo fixed... :-(
Thanks,
John H. Nyhuis
Desk: (206)-685-8334
jnyh...@uw.edu
Box 359461, 15th floor, 106
On 10/29/2019 4:03 AM, Tony Mountifield wrote:
> In article <7025a0a8-1471-530d-dad0-3770e902c...@uw.edu>
On Tuesday, October 29, 2019 at 4:45:53 AM UTC-7, Andrew wrote:
>
> Thanks Dima
>
> On Tuesday, 29 October 2019 17:51:02 UTC+11, Dima Pasechnik wrote:
>>
>> Did you run
>>
>> xcode-select --install
>>
>> after Xcode upgrade?
>>
>
> Yes, the command line tools are correctly installed but, as
Oops, I spoke too soon. Two more files had failures:
- sage -t --long src/sage/databases/stein_watkins.py # 20 doctests failed
- sage -t --long src/sage/interfaces/frobby.py # 12 doctests failed
On Monday, October 28, 2019 at 3:02:23 PM UTC-7, John H Palmieri wrote:
>
> With a Python 3
With a Python 3 build of Sage on OS X 10.14.6, I decided to install as many
optional and experimental packages as I could. The results:
*Optional:*
- the following packages failed to build, and the reason wasn't completely
obvious:
awali
buckygen
cbc
gambit
gdb
mpi4py
- the following
reached}=="0"
ATTRS{device_blocked}=="0"
ATTRS{evt_mode_parameter_change_reported}=="0"
ATTRS{evt_lun_change_reported}=="0"
ATTRS{evt_inquiry_change_reported}=="0"
ATTRS{dh_state}=="detached"
ATTRS{i
+1
On Saturday, October 26, 2019 at 5:27:51 PM UTC-7, vdelecroix wrote:
>
>
> https://trac.sagemath.org/ticket/28660
>
>
> Le 26/10/2019 à 17:20, François Bissey a écrit :
> > +1
> >
> >> On 27/10/2019, at 12:58 PM, Vincent Delecroix <20100.d...@gmail.com
> > wrote:
> >>
> >> +1
> >>
>
On Friday, October 25, 2019 at 2:59:36 AM UTC-7, Dima Pasechnik wrote:
>
> in the Sage 9.0.beta2 I get
>
> [ipython-5.8.0] Successfully installed ipython-5.8.0
> [ipython-5.8.0] Cleaning up...
> [ipython-5.8.0] Removed build tracker '/tmp/pip-req-tracker-h6h22jg5'
> [ipython-5.8.0]
>
On Thursday, October 24, 2019 at 10:57:09 AM UTC-7, Dima Pasechnik wrote:
>
> On Thu, Oct 24, 2019 at 6:48 PM Nils Bruin >
> wrote:
> >
> > On Thursday, October 24, 2019 at 10:29:48 AM UTC-7, Nils Bruin wrote:
> >>
> >>
> >> I guess via ctypes it would be possible too.
> >
> >
> >
On Wednesday, October 23, 2019 at 9:49:56 PM UTC-7, Nils Bruin wrote:
>
> On Wednesday, October 23, 2019 at 2:47:54 PM UTC-7, John H Palmieri wrote:
>>
>>
>>
>> On Wednesday, October 23, 2019 at 1:41:35 PM UTC-7, Nils Bruin wrote:
>>>
>>> On Wedne
On Wednesday, October 23, 2019 at 1:41:35 PM UTC-7, Nils Bruin wrote:
>
> On Wednesday, October 23, 2019 at 1:26:46 PM UTC-7, John Cremona wrote:
>>
>>
>> That all looks very complicated. Before I fixed the eclib source code
>> the previous method did work, namely to flush stdout and stderr
side-library
>
> is it what would work for us?
>
> On Wed, 23 Oct 2019, 20:06 John H Palmieri, > wrote:
>
>>
>>
>> On Monday, September 9, 2019 at 2:06:21 PM UTC-7, Jeroen Demeyer wrote:
>>>
>>> On Mon, Sep 9, 2019 at 7:51 PM John H Palmieri
>&g
On Monday, September 9, 2019 at 2:06:21 PM UTC-7, Jeroen Demeyer wrote:
>
> On Mon, Sep 9, 2019 at 7:51 PM John H Palmieri > wrote:
> > I am writing to ask for help fixing a Python 3 problem. On some
> platforms, there are Python 3 doctest failures in
> >
>
ey have the deprecated behavior in
> a function they've written.
> David
>
> On Sat, Oct 19, 2019 at 2:56 PM John H Palmieri > wrote:
>
>> Here is a doctest from sage/rings/integer.pyx:
>>
>> sage: Integer('012')
>> doctest:...: DeprecationWa
Here is a doctest from sage/rings/integer.pyx:
sage: Integer('012')
doctest:...: DeprecationWarning: use 0o as octal prefix instead of 0
If you do not want this number to be interpreted as octal, remove
the leading zeros.
See http://trac.sagemath.org/17413 for
On Friday, October 18, 2019 at 10:25:07 AM UTC-7, Dima Pasechnik wrote:
>
> Hi John,
>
> On Fri, Oct 18, 2019 at 5:08 PM John H Palmieri > wrote:
> >
> > I have compiled it without any problems. You should not be using gcc
> from homebrew, but rather the ver
I have compiled it without any problems. You should not be using gcc from
homebrew, but rather the version of gcc installed by Xcode or its
command-line tools. That might help. (You should install the homebrew gcc
package to get gfortran, but at least for me, installing homebrew's gcc
, since this past February, you also have to pay in order
to have Groups.IO do the moving of your messages, files and photos. No freebie
for that anymore.
--
John H. Reinhardt
With a Python 3 build of Sage, there are three files which exhibit failures
only (or primarily?) when running the Sage patchbot. This is being tracked
at https://trac.sagemath.org/ticket/28622. Can anyone help figure out the
problem and how to fix it? To see the problem, cd to SAGE_ROOT, run
A few days ago, after the Catalina release, I used Homebrew to build gcc,
and it worked. Well, it built from source, which took a while, but it built
a version of gfortran which worked well enough to build Sage. (As far as I
know, it's completely functional, but the only reason I install
On Wednesday, October 9, 2019 at 4:51:48 AM UTC-7, David Joyner wrote:
>
>
>
> On Wed, Oct 9, 2019 at 7:42 AM Dima Pasechnik > wrote:
>
>>
>>
>> On Wed, Oct 9, 2019 at 6:34 AM David Joyner > > wrote:
>>
>>>
>>>
>>> On Wed, Oct 9, 2019 at 7:14 AM Dima Pasechnik >> > wrote:
>>>
Hi,
On OS X, Sage by default should use the system's "gcc" (which is actually
clang), so it's okay to not have a symlink connecting gcc-9 to gcc in
/usr/local/bin. What you really need is /usr/local/bin/gfortan, and
homebrew should provide that.
John
On Tuesday, October 8, 2019 at 3:56:24 PM
I have been testing new versions of Simon King's p-group cohomology
package. The current version doesn't work with Python 3, and he has been
working (#28414) to fix this. My workflow:
1. check out his git branch
2. run ./sage -f -c p_group_cohomology
3. report any issues
4.
Could you also trying using Homebrew to install gfortran?
On Wednesday, September 25, 2019 at 12:09:55 PM UTC-7, Ben Salisbury wrote:
>
> Ok, I tried the Homebrew route, and still the build failed. First, the
> computer successfully executed the following:
>
> brew install
On Tuesday, September 24, 2019 at 10:12:17 AM UTC-7, Ben Salisbury wrote:
>
> Hi,
>
> I'm attempting to build Sage from the develop branch on a new office
> computer running OS X 10.14.6. I've installed Xcode and Command Line Tools
> (or at least I thought I had), and I'm getting a build
Beautiful build. I've been thinking about running Campy ergo's of that
generation on my Sam. What's the jtek/cassette setup you have? How's it
shifting?
John in Cambridge
On Tuesday, September 24, 2019 at 2:32:36 AM UTC-4, Joe Bernard wrote:
>
> Here's the first shots of my new-to-me A/R sans
Beautiful build. I was thinking of running a similar shimergo setup on my Sam.
What jtek + cassette combo are you running?
--
You received this message because you are subscribed to the Google Groups "RBW
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it,
+1 for threejs
I tried to compare the two: in a single Jupyter notebook, I plotted the
same function with both viewers. threejs produced the plot faster, and it
was snappier when rotating, zooming, etc. (This is with both Firefox and
Safari on OS X.) Same from the command-line: the threejs
On Thursday, September 12, 2019 at 12:30:34 PM UTC-7, Dima Pasechnik wrote:
>
> On Thu, Sep 12, 2019 at 5:55 PM John Cremona > wrote:
> >
> > On ubuntu, upgrade from previous beta, python3 configured: make
> ptestlong succeeds except for
> >
> > sage -t --long --warn-long 81.2
On Friday, September 6, 2019 at 3:13:07 AM UTC-7, E. Madison Bray wrote:
>
> On Fri, Sep 6, 2019 at 11:36 AM E. Madison Bray > wrote:
> >
> > Consistently getting a test failure on Cygwin related to some oddity in
> GAP:
> >
> > sage -t --long --warn-long 109.3 src/sage/tests/cmdline.py
>
On Wednesday, September 11, 2019 at 4:36:46 PM UTC-7, Volker Braun wrote:
>
> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
>
OS X + Python 3: All tests
On Monday, September 9, 2019 at 2:06:21 PM UTC-7, Jeroen Demeyer wrote:
>
> On Mon, Sep 9, 2019 at 7:51 PM John H Palmieri > wrote:
> > I am writing to ask for help fixing a Python 3 problem. On some
> platforms, there are Python 3 doctest failures in
> >
>
I am writing to ask for help fixing a Python 3 problem. On some platforms,
there are Python 3 doctest failures in
- libs/eclib/interface.py (#28454)
- rings/polynomial/polynomial_rational_flint.pyx (#28334)
and both occur for the same reason: warning messages printed by C or C++
libraries are
With a Python 3 build on OS X, I get a sporadic failure in
numerical/linear_tensor_element.pyx — it fails not every time, but at least
half the time. As far as I can tell, this is due to #27587 (that is, I get
failures with 8.9.beta8 + that ticket, but not with 8.9.beta8), but I don't
). For anyone who is interested the code is available at:
<https://github.com/JohnForecast/RaspbianDECnet
<https://github.com/JohnForecast/RaspbianDECnet>>
John.
Thanks! Looking forward to trying it out.
--
John H. Reinhardt
On Thursday, August 29, 2019 at 7:15:51 AM UTC-7, Frédéric Chapoton wrote:
>
> Hello
>
> Somebody (else) should make sure that every single remaining piece of
> python2 is removed from a python3 sage. In particular, we should not build
> python2 at all.
>
See
On Sunday, August 25, 2019 at 3:37:50 PM UTC-7, Volker Braun wrote:
>
> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
>
> It is nearing the end of the 8.9
the EOL of various platforms - VAX is 2011, Alpha is
2017, Integrity is ongoing still but coming to an end soon.
--
John H. Reinhardt
and that happens to all documents as far as I can tell. I
haven't checked with Adobe.
The colors seemed good, too. The covers were good and the red highlights
inside were legible.
--
John H. Reinhardt
On 8/24/2019 4:11 PM, Al Kossow via cctalk wrote:
On 8/24/19 1:38 PM, John H. Reinhardt via cctalk wrote:
On 8/24/2019 3:30 PM, John H. Reinhardt via cctalk wrote:
I'll have to double check, but from the looks of this list I don't need the
VAX/VMS Grey Wall that I acquired a couple
months
s to build the 75 different emulators. It has the latest
updates to Raspbian Buster.
What USB3 thumb drive did you use?
--
John H. Reinhardt
On 8/24/2019 3:30 PM, John H. Reinhardt via cctalk wrote:
I'll have to double check, but from the looks of this list I don't need the
VAX/VMS Grey Wall that I acquired a couple months ago. It's a nearly pristine
set of the V5.0 VAX/VMS documentation set. Some volumes are still sealed
./VMS_5.0_Apr88/aa-lb25a-te_VMS_5.0_Obsolete_Features_Manual_Apr88.tar
./VMS_5.0_Apr88/aa-lb34a-te_VAXstation_2000_Installation_Apr88.tar
./VMS_5.0_Apr88/ey-d209e-sg-0001.tar
--
John H. Reinhardt
PRRT #8909
C HS #11530
N-Trak #7566
On 8/20/2019 11:26 PM, John H. Reinhardt via cctalk wrote:
On 8/20/2019 11:08 PM, John H. Reinhardt wrote:
On 8/20/2019 10:37 PM, Zane Healy wrote:
On Aug 20, 2019, at 5:16 PM, John H. Reinhardt via
cctalk wrote:
On 8/20/2019 1:51 PM, Zane Healy via cctalk wrote:
On Aug 20, 2019, at 11:43
On 8/20/2019 11:08 PM, John H. Reinhardt wrote:
On 8/20/2019 10:37 PM, Zane Healy wrote:
On Aug 20, 2019, at 5:16 PM, John H. Reinhardt via
cctalk wrote:
On 8/20/2019 1:51 PM, Zane Healy via cctalk wrote:
On Aug 20, 2019, at 11:43 AM, Noel Chiappa via cctalk
wrote:
From: Glen Slick
for.
--
John H. Reinhardt
Yes, that fits. Now that I know to look, I see buried in my gap install log
Uninstalling existing 'gap'
Running pre-uninstall script for 'gap'
/Users/jpalmier/Desktop/Sage/git/sage/local/var/lib/sage/scripts/gap/spkg-prerm:
line 13:
In order to try to track down the problem with Python 3 and
polynomial_rational_flint.pyx on Debian (see
https://trac.sagemath.org/ticket/28334 — help wanted!), I installed
VirtualBox and a Debian 10 virtual machine on my iMac. Most doctests pass,
but I am getting some numerical noise. Did I
On Tuesday, August 6, 2019 at 5:55:53 AM UTC-7, E. Madison Bray wrote:
>
> On Tue, Aug 6, 2019 at 2:45 PM Eric Gourgoulhon > wrote:
> >
> > Le vendredi 2 août 2019 18:07:16 UTC+2, John H Palmieri a écrit :
> >>
> >>
> >>
> >> On Fri
https://bugs.kde.org/show_bug.cgi?id=410465
--- Comment #4 from John H ---
Latte-dock has not crashed on subsequent updates.
Clearing the cache made no perceptible difference to performance.
I have never run the dock from the command line.
Since the crash the optional Lock / Logout widget
New failure with Python 3:
sage -t --warn-long 78.7 src/sage/tests/cmdline.py
**
File "src/sage/tests/cmdline.py", line 503, in
sage.tests.cmdline.test_executable
Failed example:
print(err)
Expected:
Cython
On Friday, August 2, 2019 at 1:36:36 PM UTC-7, Nils Bruin wrote:
>
> On Friday, August 2, 2019 at 11:39:47 AM UTC-7, Timo Kaufmann wrote:
>>
>> Hi!
>>
>> As part of my packaging workflow, I find myself pasting error messages
>> into the trac search pretty frequently to discover if something is
On Friday, August 2, 2019 at 9:07:16 AM UTC-7, John H Palmieri wrote:
>
>
>
> On Friday, August 2, 2019 at 3:31:07 AM UTC-7, Eric Gourgoulhon wrote:
>>
>>
>>
>> Le vendredi 2 août 2019 01:00:29 UTC+2, John H Palmieri a écrit :
>>>
>>
On Friday, August 2, 2019 at 3:31:07 AM UTC-7, Eric Gourgoulhon wrote:
>
>
>
> Le vendredi 2 août 2019 01:00:29 UTC+2, John H Palmieri a écrit :
>>
>> Another question: does Flint pass its test suite on these machines?
>>
>
> How could I run this test su
Another question: does Flint pass its test suite on these machines?
On Thursday, August 1, 2019 at 3:52:07 PM UTC-7, John H Palmieri wrote:
>
> Do you get the same failure with Python 2? If not, any ideas why
> "Exception (FLINT memory_manager). Unable to allocate memory
Do you get the same failure with Python 2? If not, any ideas why "Exception
(FLINT memory_manager). Unable to allocate memory" would depend on the
version of Python? Flint doesn't depend on Python, so if it's Python 3
only, is there some issue with the Flint interface?
On Tuesday, July 30,
https://bugs.kde.org/show_bug.cgi?id=410465
John H changed:
What|Removed |Added
Platform|unspecified |Archlinux Packages
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=410465
Bug ID: 410465
Summary: Latte-dock did not close properly on reboot
Product: kde
Version: unspecified
Platform: unspecified
OS: Linux
Status: REPORTED
Keywords:
On Friday, July 26, 2019 at 9:33:25 AM UTC-7, John H Palmieri wrote:
>
>
>
> On Friday, July 26, 2019 at 12:32:06 AM UTC-7, Dima Pasechnik wrote:
>>
>>
>>
>> On Fri, 26 Jul 2019 at 06:26, Samuel Dupree wrote:
>>
>>>
>>>
>>> I
On Friday, July 26, 2019 at 12:32:06 AM UTC-7, Dima Pasechnik wrote:
>
>
>
> On Fri, 26 Jul 2019 at 06:26, Samuel Dupree > wrote:
>
>>
>>
>> I'm attempting to update SageMath-8.7.app on an iMacPro running Mac OS X
>> ver. 10.14.6 tp SageMath-8.8.app. The problem for the moment occurs when I
Hi all,
I recently upgraded a ReviewBoard install from Ubuntu 14.04/RB 1.6.9 to
18.04/3.0.15. I did it by advancing through each final minor release of RB
with pip (starting with 1.7.xx, since that was the earliest available via
pip), and running rb-site upgrade and recommended
See
https://ask.sagemath.org/question/47214/help-doesnt-show-function-call/.
Some of the time when you evaluate
blah?
the signature is not present. Is this a bug or is it intended?
I like this behavior:
sage: A = SteenrodAlgebra()
sage: A.antipode?
Signature: B.antipode(self, *args)
.
--
Will
Just curious, but anything worth scanning (DEC)? Not that I'll make it to
VCFmw this year. I'm in/near Fort Worth, TX so it's a long haul for me. But
they all are from here.
--
John H. Reinhardt
. Apparently some people have had problems with the host
not letting them move the name registration when switching hosting providers.
Or vice versa. I don't have any experience with that. I've either self hosted
or, like now, have co-located hardware.
--
John H. Reinhardt
any do that? For free? Or cheap? I didn't dig
real deep into providers.
--
John H. Reinhardt
estimate?
--
John H. Reinhardt
On 6/25/2019 8:00 PM, Al Kossow via cctalk wrote:
On 6/25/19 5:35 PM, John H. Reinhardt via cctalk wrote:
I hope someone scans that RSTS/E documentation. There isn't a lot of it
available online.
Seriously?
I count 75 manuals under pdp11/rsts on bitsavers
Sounds like a lot, I know
t I'm in Fort Worth, TX
--
John H. Reinhardt
I am writing to follow up on this. The University of Washington has now
stopped accepting donations to the Sage Foundation fund. People looking for
ways to donate in support of Sage will need to find other avenues for that,
and I encourage people to create those avenues if they know how. Of
On Tuesday, June 25, 2019 at 3:10:29 AM UTC-7, Peter Luschny wrote:
>
> Am Di., 25. Juni 2019 um 10:49 Uhr 'luisfe' :
>
> | When n =0, k ranges from 0 to -1 so there is no k and the list
> constructed in ib(n,m)
> | is just the empty list. Not an empty list of polynomials, just an empty
>
This problem is being discussed at https://trac.sagemath.org/ticket/28008.
As François says, you can touch matrix_rational_dense.pyx and do "sage -b",
or you can do "sage -ba" to rebuild all of Sage's library files, in case
other ones are also affected.
On Wednesday, June 19, 2019 at 5:52:19
On Tuesday, June 18, 2019 at 10:12:06 AM UTC-7, Parth Dubal wrote:
>
> I tried to download manually and put it into upstream directory but it is
> already present and the installation didn't even reach to that step. I
> don't understand, if it was already downloaded earlier then why the
>
On Tuesday, June 18, 2019 at 8:47:31 AM UTC-7, Parth Dubal wrote:
>
> Hi,
>
> I tried three times to install sage as described in github on my virtual
> machine (Ubuntu 19) but the installation gets stuck for hours at the point
> of downloading zeromq-4.2.5.tar.gz. I am running ubuntu on
in Thunderbird... I'd
wondered how it happened. ;)
Noel
--
John H. Reinhardt
I am having a problem on a different OS X machine (an iMac Pro):
sage -t
src/doc/en/thematic_tutorials/explicit_methods_in_number_theory/birds_other.rst
Bad exit: 1
**
...
sage: dimension(M.cuspidal_subspace()) ## line 109
d for
me, too.
>
> David.
>
> Le 9 juin 2019 à 23:23, John H Palmieri >
> a écrit :
>
> I performed the incremental build the way I always do: "git pull trac"
> followed by "make". When I ran into problems, I restarted from 8.8.beta7,
> wh
is an incremental build problem.
> Something that should have been rebuilt didn’t and that may be because of
> the way you performed the incremental build.
>
> François
>
> > On 10/06/2019, at 7:46 AM, John H Palmieri > wrote:
> >
> >
> >
> > O
On Sunday, June 9, 2019 at 12:37:52 PM UTC-7, John H Palmieri wrote:
>
> I think the problem is with the openblas upgrade,
> https://trac.sagemath.org/ticket/27847.
>
I opened https://trac.sagemath.org/ticket/27961 (not that I know how to fix
it...)
>
>
> On Sunday, Jun
I think the problem is with the openblas upgrade,
https://trac.sagemath.org/ticket/27847.
On Sunday, June 9, 2019 at 10:19:27 AM UTC-7, David Coudert wrote:
>
> crash with both python 2 and python 3 on osX. I attach the crash report
> with python 3.
>
> Any help is more than welcome.
>
>
On Saturday, June 8, 2019 at 8:56:09 AM UTC-7, Dima Pasechnik wrote:
>
>
>
> On Sat, 8 Jun 2019 16:50 John H Palmieri, > wrote:
>
>>
>>
>> On Saturday, June 8, 2019 at 1:25:11 AM UTC-7, vdelecroix wrote:
>>>
>>> Le 07/06/2019 à 16:44,
On Saturday, June 8, 2019 at 1:25:11 AM UTC-7, vdelecroix wrote:
>
> Le 07/06/2019 à 16:44, Jeroen Demeyer a écrit :
> > On 2019-06-07 16:38, E. Madison Bray wrote:
> >> While I agree it's part of an annoying trend, this is one change I
> >> welcome: The Python interpreter shipped in OSX has
On Friday, June 7, 2019 at 7:44:03 AM UTC-7, Jeroen Demeyer wrote:
>
> On 2019-06-07 16:38, E. Madison Bray wrote:
> > While I agree it's part of an annoying trend, this is one change I
> > welcome: The Python interpreter shipped in OSX has always *always*
> > been broken and unusable
>
>
Oh, and Sage with Python 3 is in pretty good shape these days. Still some
doctest failures, but I think it is mostly very functional.
John
On Thursday, June 6, 2019 at 3:20:25 PM UTC-7, John H Palmieri wrote:
>
> I can confirm that it works for me on OS X with Python 3, gives the
I can confirm that it works for me on OS X with Python 3, gives the error
you described with Python 2.
On Thursday, June 6, 2019 at 2:57:08 PM UTC-7, Emmanuel Charpentier wrote:
>
> According to Serge Lelièvre, the proble doesn't occur when ran under a
> Python3-based Sage. He advises to run
On 6/1/2019 5:24 PM, Mark J. Blair via cctalk wrote:
On Jun 1, 2019, at 14:57, John H. Reinhardt via cctalk
wrote:
Is this the system that was on Reddit?
Yes. I’ll be fetching it next weekend. I’m excited! I wonder if the hard drive
is still usable, and if there is anything interesting
?
--
John H. Reinhardt
PRRT #8909
C HS #11530
N-Trak #7566
601 - 700 of 8727 matches
Mail list logo
