> On Mar 15, 2019, at 21:46 , Ai Bo wrote:
>
> I am running a long running program. I would like to log the output.
> I have tried:
> ../sage-8.6/sage test.sage > test.log &
>
> There is nothing written in test.log before the program finishes.
> I tried to use tee, same problem.
>
> I trie
I am running a long running program. I would like to log the output.
I have tried:
../sage-8.6/sage test.sage > test.log &
There is nothing written in test.log before the program finishes.
I tried to use tee, same problem.
I tried to add:
f = open('test.log', 'w')
in my test.sage program, sti
On Fri, Mar 15, 2019 at 10:17 PM Dima Pasechnik wrote:
>
>
>
> On Friday, March 15, 2019 at 5:58:15 PM UTC, John H Palmieri wrote:
>>
>>
>>
>> On Friday, March 15, 2019 at 3:31:33 AM UTC-7, Dima Pasechnik wrote:
>>>
>>> On Thu, Mar 14, 2019 at 7:51 PM John H Palmieri wrote:
>>> >
>>> > I'm seeing
On Friday, March 15, 2019 at 5:58:15 PM UTC, John H Palmieri wrote:
>
>
>
> On Friday, March 15, 2019 at 3:31:33 AM UTC-7, Dima Pasechnik wrote:
>>
>> On Thu, Mar 14, 2019 at 7:51 PM John H Palmieri
>> wrote:
>> >
>> > I'm seeing the same failure on a Mac running the most recent OS X. I
>> h
On Fri, Mar 15, 2019 at 02:59:05PM -0700, Kwankyu Lee wrote:
>
> If the determinant is obviously zero, then you don't need to run the
> computation. If a preprocessing to check zero rows or columns is added,
> then the determinant computation would become slower for usual nontrivial
> cases.
I
Hi,
If the determinant is obviously zero, then you don't need to run the
computation. If a preprocessing to check zero rows or columns is added,
then the determinant computation would become slower for usual nontrivial
cases.
Cheers.
On Saturday, March 16, 2019 at 2:15:06 AM UTC+9, Maximili
On Friday, March 15, 2019 at 3:31:33 AM UTC-7, Dima Pasechnik wrote:
>
> On Thu, Mar 14, 2019 at 7:51 PM John H Palmieri > wrote:
> >
> > I'm seeing the same failure on a Mac running the most recent OS X. I
> have openssl 1.1.1a installed on this machine, and I see the error in Sage.
> Then
PS: The openssl master branch is already Apache
licensed:
https://github.com/openssl/openssl/commit/151333164ece49fdba3fe5c4bbdccd9ae66d.
Though no release yet.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group
On Friday, March 15, 2019 at 5:12:59 PM UTC+1, Dima Pasechnik wrote:
>
> 1) As Python.org now ships 2.7.16 with pre-build openssl, then why
> don't we do the same?
>
Because Python is not GPL licensed, of course
> (IMHO Sage should not try to out-saint the pope, and stick to "we
> don't ship
Hello,
I'm using the current developer version of sage and noticed that when
computing determinants of matrices over polynomial rings and rational
functions, cases where the determinant is easily seen to be zero due to
zero rows or columns can take an unreasonable long time to compute. I
comp
On Fri, Mar 15, 2019 at 3:55 PM E. Madison Bray wrote:
>
> On Fri, Mar 15, 2019 at 4:47 PM Dima Pasechnik wrote:
> >
> > On Fri, Mar 15, 2019 at 3:35 PM E. Madison Bray
> > wrote:
> > >
> > > On Fri, Mar 15, 2019 at 3:31 PM Dima Pasechnik wrote:
> > > >
> > > > It appears that Sage's openssl p
On Fri, Mar 15, 2019 at 4:47 PM Dima Pasechnik wrote:
>
> On Fri, Mar 15, 2019 at 3:35 PM E. Madison Bray wrote:
> >
> > On Fri, Mar 15, 2019 at 3:31 PM Dima Pasechnik wrote:
> > >
> > > It appears that Sage's openssl package is broken on MacOS nowadays.
> > > Should this be a blocker?
> >
> > H
On Fri, Mar 15, 2019 at 3:35 PM E. Madison Bray wrote:
>
> On Fri, Mar 15, 2019 at 3:31 PM Dima Pasechnik wrote:
> >
> > It appears that Sage's openssl package is broken on MacOS nowadays.
> > Should this be a blocker?
>
> How is SSL support currently handled in MacOS? I have not kept up
> with
On Fri, Mar 15, 2019 at 3:31 PM Dima Pasechnik wrote:
>
> It appears that Sage's openssl package is broken on MacOS nowadays.
> Should this be a blocker?
How is SSL support currently handled in MacOS? I have not kept up
with that issue. Are OSX users still not able to do something as
simple as
On Thu, Mar 07, 2019 at 07:12:29AM -0800, kcrisman wrote:
> >
> > http://doc.sagemath.org/html/en/reference/repl/sage/repl/ipython_kernel/interact.html
> > http://doc.sagemath.org/html/en/prep/Quickstarts/Interact.html
> >
> >
> Thanks; I knew about the second one, since I wrote it :-) but the firs
Is openssl compiled into the macos binary? Technically we wouldn't be
allowed to distribute that
On Friday, March 15, 2019 at 3:58:17 PM UTC+1, Dima Pasechnik wrote:
>
> On Fri, Mar 15, 2019 at 2:53 PM Volker Braun > wrote:
> >
> > We don't build it by default, so imho the answer is no. N
On Fri, Mar 15, 2019 at 2:53 PM Volker Braun wrote:
>
> We don't build it by default, so imho the answer is no. Not every optional
> package works on every supported platform, even if we strive for that.
Are we going to ship broken MacOS binaries then?
>
> On Friday, March 15, 2019 at 3:31:36
We don't build it by default, so imho the answer is no. Not every optional
package works on every supported platform, even if we strive for that.
On Friday, March 15, 2019 at 3:31:36 PM UTC+1, Dima Pasechnik wrote:
>
> It appears that Sage's openssl package is broken on MacOS nowadays.
> Should
It appears that Sage's openssl package is broken on MacOS nowadays.
Should this be a blocker?
On Thu, Mar 14, 2019 at 4:49 PM Volker Braun wrote:
>
> Feel free to fix the Cygwin-related bugs, but some of these are longstanding
> issues that should be discussed with upstream first; Realistically
The bug seems to be triggered by the use of a symbolic function (the one
created by function('chi')).
It is now tracked at
https://trac.sagemath.org/ticket/27492
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group an
> I see a different but I guess related error, arising like this:
>
I wonder if this is what causes our errors to be different:
This is XeTeX, Version 3.14159265-2.6-0.9 (TeX Live 2018) (preloaded
format=xelatex)
Also, my error in command line only occurs once - I guess because it's a
wa
As another data point from Mac, with a DIFFERENT set of errors,
see https://groups.google.com/d/msg/sage-release/KYiD_QSJjBs/ApfxGOXjBwAJ
and the there-attached failures which look like this:
File
"/Users/Sage/sage-8.7.beta7/local/lib/python2.7/site-packages/sage/databases/oeis.py",
line
On Thu, Mar 14, 2019 at 7:51 PM John H Palmieri wrote:
>
> I'm seeing the same failure on a Mac running the most recent OS X. I have
> openssl 1.1.1a installed on this machine, and I see the error in Sage. Then I
> did './sage -i openssl' and './sage -f python2', and I still see the error.
> Th
Thanks for the report. I confirm the bug in Sage 8.7.beta7.
What is strange is that ddChi seems a perfectly valid symbolic expression:
sage: ddChi = ddChi.expand(); ddChi
2*diff(chi(r, theta, phi), r)/r + cos(theta)*diff(chi(r, theta, phi), theta
)/(r^2*sin(theta)) + diff(chi(r, theta, phi), theta
24 matches
Mail list logo
