On Tue, Mar 19, 2019 at 3:50 PM kcrisman wrote:
>
>
>> >
>> > sage: w = oeis(7540) ; w
>> >
>> > A007540: Wilson primes: primes p such that (p-1)! == -1 (mod p^2).
>>
>> Thanks, so this works, right? I've opened
>
>
> Correct! I can't speak for the two other slightly different errors - you
> ma
> >
> > sage: w = oeis(7540) ; w
> >
> > A007540: Wilson primes: primes p such that (p-1)! == -1 (mod p^2).
>
> Thanks, so this works, right? I've opened
>
Correct! I can't speak for the two other slightly different errors - you
may want to reply to Justin Walker's report on sage-release
On Mon, Mar 18, 2019 at 11:56 AM kcrisman wrote:
>
>
>> Can someone (Karl?) with this issue (broken access to oeis()) try
>>
>> mkdir local/openssl
>> cd local/openssl
>> ln -s ../lib/python2.7/site-packages/pip/_vendor/certifi/cacert.pem cert.pem
>>
>> to see if this is a simpler fix?
>>
>
> sage
> Can someone (Karl?) with this issue (broken access to oeis()) try
>
> mkdir local/openssl
> cd local/openssl
> ln -s ../lib/python2.7/site-packages/pip/_vendor/certifi/cacert.pem
> cert.pem
>
> to see if this is a simpler fix?
>
>
sage: w = oeis(*7540*) ; w
A007540: Wilson primes: primes
On Sat, Mar 16, 2019 at 12:26 AM Dima Pasechnik wrote:
>
> 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 Sat, Mar 16, 2019 at 06:05:35AM -0700, kcrisman wrote:
> This is all very helpful. Hopefully I'll not miss if there is a beta or rc
> version of Sage implementing this - if I fix this with the script now, I
> won't be able to test "vanilla"-ish Sage.
well, to break it back it suffices to rem
This is all very helpful. Hopefully I'll not miss if there is a beta or rc
version of Sage implementing this - if I fix this with the script now, I
won't be able to test "vanilla"-ish Sage.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To uns
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 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
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
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
Perhaps it's some sort of certificate issue.
> If an up to date openssl has its certs improperly set up, it won't work,
> IMHO.
>
>>
>>
Give the error message, this seems plausible. Any ideas on where to go
from here? Is it user error for me to try to use the OEIS through Sage?
Volker is
Perhaps it's some sort of certificate issue.
If an up to date openssl has its certs improperly set up, it won't work,
IMHO.
On Thu, 14 Mar 2019 19:51 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, an
15 matches
Mail list logo
