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, Jeroen Demeyer a écrit :
>>> > On 2019-06-07 16:38, E.
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, 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
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
Tue 2019-05-21 07:09:35 UTC, dantetante:
>
> I'm quite new to sage and just read the installation guide of sage 8.7; I
> found the chapter >>install from conda forge<< and found the command >>source
> activate sage<<; this should be changed to >>conda activate sage<< (see
> e.g. here:
>
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 always *always*
been broken and unusable
What matters for Sage is: was it
