I see that there has been work on converting print statements and simple stuff
like that to be python 3 compatible. What are the other steps involved in fully
supporting python 3 that are still underway (or haven't been started)?
--
You received this message because you are subscribed to the Go
Pz1oBkJ71xET+xTmecBHB2c9OwlgPjB70AB8=
>
>
> as a single line at the end of .ssh/know_hosts
>
> François
>
> > On 31/10/2016, at 20:52, Marco Cognetta > wrote:
> >
> > There is no longer a line with trac.sagemath.org but when I try to
> connect I do not get the option
ançois
>
> > On 31/10/2016, at 20:27, Marco Cognetta > wrote:
> >
> > I have done that but I still get the same error. How do I get the
> correct information to put in known_hosts?
> >
> > On Monday, October 31, 2016 at 4:14:23 PM UTC+9, François wrot
ink it would be the 4th line but it could be
> another one. It will almost certainly be another one
> for other people.
>
> François
>
> > On 31/10/2016, at 20:10, Marco Cognetta > wrote:
> >
> > What is the fix for this? I have tried getting the updated tra
What is the fix for this? I have tried getting the updated trac and testing
my rsa keys.
On Saturday, October 29, 2016 at 2:33:05 AM UTC+9, Dima Pasechnik wrote:
>
>
>
> On Friday, October 28, 2016 at 5:01:54 PM UTC, jhonrubia6 wrote:
>>
>> Is not 104.197.143.230?
>>
>>
>> OnoSendaiII:sage J_Honr
Ive had the same problem with pari. Even if I make clean and then checkout an
older branch where only cython files have been changed, ./sage -br fails due to
pari.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group an
It seems there are some differences that were not showing up when I was
checking status.
On Saturday, September 10, 2016 at 1:17:31 AM UTC+9, Marco Cognetta wrote:
>
> One public branch is the trac ticket #21423. I just tested the turning on
> and off again and it happened and then f
ecipe for target 'sage' failed
On Friday, September 9, 2016 at 8:20:16 PM UTC+9, Jeroen Demeyer wrote:
>
> On 2016-09-09 12:56, Marco Cognetta wrote:
> > It has happened to me where I build sage, turn off my computer, turn it
> > back on, and build it again. The
rebuilt) which will also go through this cythonizing step (first when I
switch to the branch, and then again when I switch back to master and try
to build it again).
On Friday, September 9, 2016 at 4:12:40 PM UTC+9, Jeroen Demeyer wrote:
>
> On 2016-09-09 08:43, Marco Cognetta wrote:
>
Hello,
I have been writing some code for sage and have encountered the following
problem. When running ./sage -br, it goes through a long cythonizing step
every time, even on files that have not been changed. I have played around
with it a little and if I run ./sage -br, wait for it to finish (
Ok, I went back and basically tried to start over and have successfully
pushed my code. I set the ticket to needs review.
On Thursday, March 3, 2016 at 7:29:10 PM UTC-5, Marco Cognetta wrote:
>
> I have used git, but I am not entirely familiar with working with code
> bases that I do
:09 PM UTC-5, David Roe wrote:
>
> Have you used git before? Have you made a branch yet for your code?
>
> If you have specific questions, you're welcome to ask them here; it may
> help others!
> David
>
> On Thu, Mar 3, 2016 at 5:32 PM, Marco Cognetta > wrote
Hi all,
I created a ticket to add Turan Graphs
(https://en.wikipedia.org/wiki/Tur%C3%A1n_graph) to Sage's graph
generators. I have complete and tested code that completes this patch, but
since this is my first patch with Sage I am looking for a little bit of
help getting it approved and merged
Hi,
I would like to implement some of the closure operations that are missing
from the finite state machine code. Since there are several that are not
implemented (intersection, difference, reversal, homomorphism, and inverse
homomorphism; with only intersection being currently included in the
14 matches
Mail list logo
