On Wednesday, April 3, 2019 at 1:56:03 PM UTC-4, John H Palmieri wrote:
>
>
>
> On Wednesday, April 3, 2019 at 10:11:19 AM UTC-7, kcrisman wrote:
>>
>>
>>
>> On Tuesday, April 2, 2019 at 6:03:23 PM UTC-4, Dima Pasechnik wrote:
>>>
>>> On Tue, Apr 2, 2019 at 10:47 PM wrote:
>>> >
>>> > Hello,
On Wed, 3 Apr 2019 at 18:56, John H Palmieri wrote:
>
>
> On Wednesday, April 3, 2019 at 10:11:19 AM UTC-7, kcrisman wrote:
>>
>>
>>
>> On Tuesday, April 2, 2019 at 6:03:23 PM UTC-4, Dima Pasechnik wrote:
>>>
>>> On Tue, Apr 2, 2019 at 10:47 PM wrote:
>>> >
>>> > Hello, Sage community.
>>> >
On Wednesday, April 3, 2019 at 10:11:19 AM UTC-7, kcrisman wrote:
>
>
>
> On Tuesday, April 2, 2019 at 6:03:23 PM UTC-4, Dima Pasechnik wrote:
>>
>> On Tue, Apr 2, 2019 at 10:47 PM >
>> wrote:
>> >
>> > Hello, Sage community.
>> > With the upcoming migration of Sage from Python2 to Python3,
On Tuesday, April 2, 2019 at 6:03:23 PM UTC-4, Dima Pasechnik wrote:
>
> On Tue, Apr 2, 2019 at 10:47 PM wrote:
> >
> > Hello, Sage community.
> > With the upcoming migration of Sage from Python2 to Python3, I was
> wondering if the "print" statement will be changed to the new "print"
>
On Tue, Apr 2, 2019 at 10:47 PM wrote:
>
> Hello, Sage community.
> With the upcoming migration of Sage from Python2 to Python3, I was wondering
> if the "print" statement will be changed to the new "print" function. In any
> case, will there be backwards compatibility with the current
