Re: [sage-devel] Unable to build sage after git trac config

[Eric Gourgoulhon]

Hi, 

Le jeudi 30 janvier 2020 04:06:02 UTC+1, Vipul Gupta a écrit :
>
>
> Yeah Sage works fine after that. But I wanted to contribute to sage and 
> therefore config my git trac account as mentioned in the this link 
> https://doc.sagemath.org/html/en/developer/git_trac.html
>
>
Welcome to Sage development!
I would  recommend not to use the git-trac commands, but plain git. 
There are regularly some issues with git-trac and using plain git is much 
more robust than git-trac. 
I would even vote for removing the git-trac section from the developer 
manual. 

Best wishes,

Eric. 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/4d1db62f-9355-49f2-ad66-5c8675b359db%40googlegroups.com.

[sage-devel] Re: Unable to build sage after git trac config

[Simon King]

Hi Eric,

On 2020-01-30, Eric Gourgoulhon  wrote:
> I would even vote for removing the git-trac section from the developer 
> manual. 

-1

I do use "git trac".

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/r0uihu%24c5e%241%40ciao.gmane.io.

Re: [sage-devel] Re: Unable to build sage after git trac config

[David Roe]

On Thu, Jan 30, 2020 at 7:35 AM Simon King  wrote:

> Hi Eric,
>
> On 2020-01-30, Eric Gourgoulhon  wrote:
> > I would even vote for removing the git-trac section from the developer
> > manual.
>
> -1
>
> I do use "git trac".
>

Agreed.  I would absolutely not advocate removing git-trac from the
manual.  I find that it makes some tasks easier than using plain git.

For the original poster, what problems are you having with git-trac?
David


> Best regards,
> Simon
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/r0uihu%24c5e%241%40ciao.gmane.io
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAChs6_nMkQC4-0sP%2BZd9E6K39kx42ZZ%3DZQ%2BM%2B3MN0yx5Svcz%2Bw%40mail.gmail.com.

Re: [sage-devel] Re: Unable to build sage after git trac config

[Dima Pasechnik]

I think git-trac should not be mentioned in the manual as the preferred way
to use git.

Imho the majority of devs here use plain git...

On Thu, 30 Jan 2020, 14:07 David Roe,  wrote:

>
>
> On Thu, Jan 30, 2020 at 7:35 AM Simon King  wrote:
>
>> Hi Eric,
>>
>> On 2020-01-30, Eric Gourgoulhon  wrote:
>> > I would even vote for removing the git-trac section from the developer
>> > manual.
>>
>> -1
>>
>> I do use "git trac".
>>
>
> Agreed.  I would absolutely not advocate removing git-trac from the
> manual.  I find that it makes some tasks easier than using plain git.
>
> For the original poster, what problems are you having with git-trac?
> David
>
>
>> Best regards,
>> Simon
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-devel+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sage-devel/r0uihu%24c5e%241%40ciao.gmane.io
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/CAChs6_nMkQC4-0sP%2BZd9E6K39kx42ZZ%3DZQ%2BM%2B3MN0yx5Svcz%2Bw%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq39FWD7rG0K8i09NT_R4aYuj554OFDHfGbJ_zH0sHGM4Q%40mail.gmail.com.

Re: [sage-devel] Re: Unable to build sage after git trac config

[Vipul Gupta]

Can someone help me with guidelines to make contribution using only git?
Regards
Vipul Gupta

On Thu, 30 Jan, 2020, 7:45 pm Dima Pasechnik,  wrote:

> I think git-trac should not be mentioned in the manual as the preferred
> way to use git.
>
> Imho the majority of devs here use plain git...
>
> On Thu, 30 Jan 2020, 14:07 David Roe,  wrote:
>
>>
>>
>> On Thu, Jan 30, 2020 at 7:35 AM Simon King 
>> wrote:
>>
>>> Hi Eric,
>>>
>>> On 2020-01-30, Eric Gourgoulhon  wrote:
>>> > I would even vote for removing the git-trac section from the developer
>>> > manual.
>>>
>>> -1
>>>
>>> I do use "git trac".
>>>
>>
>> Agreed.  I would absolutely not advocate removing git-trac from the
>> manual.  I find that it makes some tasks easier than using plain git.
>>
>> For the original poster, what problems are you having with git-trac?
>> David
>>
>>
>>> Best regards,
>>> Simon
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "sage-devel" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to sage-devel+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/sage-devel/r0uihu%24c5e%241%40ciao.gmane.io
>>> .
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-devel+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sage-devel/CAChs6_nMkQC4-0sP%2BZd9E6K39kx42ZZ%3DZQ%2BM%2B3MN0yx5Svcz%2Bw%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/CAAWYfq39FWD7rG0K8i09NT_R4aYuj554OFDHfGbJ_zH0sHGM4Q%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CA%2BSFJRcQAti7EX%3D-BO9mMYVXdLtUSiJP%2BoB%3DfW0HVJ476Z%2Bejw%40mail.gmail.com.

Re: [sage-devel] Re: Unable to build sage after git trac config

[Dima Pasechnik]

Are you familiar with using github server and  CLI to checkout specific
branches and pushing into a github repo?
(there are excellent tutorials on this).

In fact, you can create your own fork of sagemath on github and practice
there.
Our workflow is similar, except that it has a much cruder web interface.

There is also a description on this in our development manual, but it is a
bit too terse.



On Thu, 30 Jan 2020, 15:16 Vipul Gupta,  wrote:

> Can someone help me with guidelines to make contribution using only git?
> Regards
> Vipul Gupta
>
> On Thu, 30 Jan, 2020, 7:45 pm Dima Pasechnik,  wrote:
>
>> I think git-trac should not be mentioned in the manual as the preferred
>> way to use git.
>>
>> Imho the majority of devs here use plain git...
>>
>> On Thu, 30 Jan 2020, 14:07 David Roe,  wrote:
>>
>>>
>>>
>>> On Thu, Jan 30, 2020 at 7:35 AM Simon King 
>>> wrote:
>>>
 Hi Eric,

 On 2020-01-30, Eric Gourgoulhon  wrote:
 > I would even vote for removing the git-trac section from the
 developer
 > manual.

 -1

 I do use "git trac".

>>>
>>> Agreed.  I would absolutely not advocate removing git-trac from the
>>> manual.  I find that it makes some tasks easier than using plain git.
>>>
>>> For the original poster, what problems are you having with git-trac?
>>> David
>>>
>>>
 Best regards,
 Simon

 --
 You received this message because you are subscribed to the Google
 Groups "sage-devel" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to sage-devel+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/sage-devel/r0uihu%24c5e%241%40ciao.gmane.io
 .

>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "sage-devel" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to sage-devel+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/sage-devel/CAChs6_nMkQC4-0sP%2BZd9E6K39kx42ZZ%3DZQ%2BM%2B3MN0yx5Svcz%2Bw%40mail.gmail.com
>>> 
>>> .
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-devel+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sage-devel/CAAWYfq39FWD7rG0K8i09NT_R4aYuj554OFDHfGbJ_zH0sHGM4Q%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/CA%2BSFJRcQAti7EX%3D-BO9mMYVXdLtUSiJP%2BoB%3DfW0HVJ476Z%2Bejw%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq2L%2B9bxsj__0NoQMhqU9oO7wJAR9K0KHtQ1yq7hjq%3DQ7Q%40mail.gmail.com.

[sage-devel] Re: Unable to build sage after git trac config

[Simon King]

Hi Dima,

On 2020-01-30, Dima Pasechnik  wrote:
> I think git-trac should not be mentioned in the manual as the preferred way
> to use git.

OK. Stating that "being able to use plain git is a useful skill" is
fine, and of course elaborating how to use plain git to work with trac
is fine, too. But please do not remove the customised scripts or their
documentation.

Best regards,
Simon

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/r0ut4p%24mle%241%40ciao.gmane.io.

Re: [sage-devel] Re: Unable to build sage after git trac config

[Vipul Gupta]

Yeah I am familiar with github and its features. But I am not sure how to
incorporate ticket features of sage issues and contribute to them?
Briefly, I want to ask how to work with tickets using git only. There are
no clear manuals for this also.
Regards
Vipul Gupta

On Thu, 30 Jan, 2020, 9:01 pm Dima Pasechnik,  wrote:

> Are you familiar with using github server and  CLI to checkout specific
> branches and pushing into a github repo?
> (there are excellent tutorials on this).
>
> In fact, you can create your own fork of sagemath on github and practice
> there.
> Our workflow is similar, except that it has a much cruder web interface.
>
> There is also a description on this in our development manual, but it is a
> bit too terse.
>
>
>
> On Thu, 30 Jan 2020, 15:16 Vipul Gupta, 
> wrote:
>
>> Can someone help me with guidelines to make contribution using only git?
>> Regards
>> Vipul Gupta
>>
>> On Thu, 30 Jan, 2020, 7:45 pm Dima Pasechnik,  wrote:
>>
>>> I think git-trac should not be mentioned in the manual as the preferred
>>> way to use git.
>>>
>>> Imho the majority of devs here use plain git...
>>>
>>> On Thu, 30 Jan 2020, 14:07 David Roe,  wrote:
>>>


 On Thu, Jan 30, 2020 at 7:35 AM Simon King 
 wrote:

> Hi Eric,
>
> On 2020-01-30, Eric Gourgoulhon  wrote:
> > I would even vote for removing the git-trac section from the
> developer
> > manual.
>
> -1
>
> I do use "git trac".
>

 Agreed.  I would absolutely not advocate removing git-trac from the
 manual.  I find that it makes some tasks easier than using plain git.

 For the original poster, what problems are you having with git-trac?
 David


> Best regards,
> Simon
>
> --
> You received this message because you are subscribed to the Google
> Groups "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/r0uihu%24c5e%241%40ciao.gmane.io
> .
>
 --
 You received this message because you are subscribed to the Google
 Groups "sage-devel" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to sage-devel+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/sage-devel/CAChs6_nMkQC4-0sP%2BZd9E6K39kx42ZZ%3DZQ%2BM%2B3MN0yx5Svcz%2Bw%40mail.gmail.com
 
 .

>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "sage-devel" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to sage-devel+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/sage-devel/CAAWYfq39FWD7rG0K8i09NT_R4aYuj554OFDHfGbJ_zH0sHGM4Q%40mail.gmail.com
>>> 
>>> .
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-devel+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sage-devel/CA%2BSFJRcQAti7EX%3D-BO9mMYVXdLtUSiJP%2BoB%3DfW0HVJ476Z%2Bejw%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/CAAWYfq2L%2B9bxsj__0NoQMhqU9oO7wJAR9K0KHtQ1yq7hjq%3DQ7Q%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CA%2BSFJRedg31hOdKhXM8t35WP-apLR%2BokaLe0eU6tVEiNTDQoWw%40mail.gmail.com.

Re: [sage-devel] Re: Unable to build sage after git trac config

[Dima Pasechnik]

On Thu, 30 Jan 2020, 15:37 Vipul Gupta,  wrote:

> Yeah I am familiar with github and its features. But I am not sure how to
> incorporate ticket features of sage issues and contribute to them?
> Briefly, I want to ask how to work with tickets using git only. There are
> no clear manuals for this also.
>

there is not much to document.

You create/update named branches and push them to the trac git repository
for reviewing. The branch name is entered into a field on the ticket form,
and so it (more precisely, the diff against the current develop branch)
gets displayed nicely. Reviewers look at it, test it, there is also some CI
happening.

Once it gets a positive review, the release manager will merge it into the
main branches.

Details like how to name branches, and how to set "git remote" are
documented.





Regards
> Vipul Gupta
>
> On Thu, 30 Jan, 2020, 9:01 pm Dima Pasechnik,  wrote:
>
>> Are you familiar with using github server and  CLI to checkout specific
>> branches and pushing into a github repo?
>> (there are excellent tutorials on this).
>>
>> In fact, you can create your own fork of sagemath on github and practice
>> there.
>> Our workflow is similar, except that it has a much cruder web interface.
>>
>> There is also a description on this in our development manual, but it is
>> a bit too terse.
>>
>>
>>
>> On Thu, 30 Jan 2020, 15:16 Vipul Gupta, 
>> wrote:
>>
>>> Can someone help me with guidelines to make contribution using only git?
>>> Regards
>>> Vipul Gupta
>>>
>>> On Thu, 30 Jan, 2020, 7:45 pm Dima Pasechnik,  wrote:
>>>
 I think git-trac should not be mentioned in the manual as the preferred
 way to use git.

 Imho the majority of devs here use plain git...

 On Thu, 30 Jan 2020, 14:07 David Roe,  wrote:

>
>
> On Thu, Jan 30, 2020 at 7:35 AM Simon King 
> wrote:
>
>> Hi Eric,
>>
>> On 2020-01-30, Eric Gourgoulhon  wrote:
>> > I would even vote for removing the git-trac section from the
>> developer
>> > manual.
>>
>> -1
>>
>> I do use "git trac".
>>
>
> Agreed.  I would absolutely not advocate removing git-trac from the
> manual.  I find that it makes some tasks easier than using plain git.
>
> For the original poster, what problems are you having with git-trac?
> David
>
>
>> Best regards,
>> Simon
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to sage-devel+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sage-devel/r0uihu%24c5e%241%40ciao.gmane.io
>> .
>>
> --
> You received this message because you are subscribed to the Google
> Groups "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/CAChs6_nMkQC4-0sP%2BZd9E6K39kx42ZZ%3DZQ%2BM%2B3MN0yx5Svcz%2Bw%40mail.gmail.com
> 
> .
>
 --
 You received this message because you are subscribed to the Google
 Groups "sage-devel" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to sage-devel+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/sage-devel/CAAWYfq39FWD7rG0K8i09NT_R4aYuj554OFDHfGbJ_zH0sHGM4Q%40mail.gmail.com
 
 .

>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "sage-devel" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to sage-devel+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/sage-devel/CA%2BSFJRcQAti7EX%3D-BO9mMYVXdLtUSiJP%2BoB%3DfW0HVJ476Z%2Bejw%40mail.gmail.com
>>> 
>>> .
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-devel+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sage-devel/CAAWYfq2L%2B9bxsj__0NoQMhqU9oO7wJAR9K0KHtQ1yq7hjq%3DQ7Q%40mail.gmail.com
>> 

[sage-devel] Problem with multiple substitutions

[Ties Laarakker]

There's a probem with multiple substitutions in Sage 9.0.



sage: var('x,y')

(x, y)

sage: (*1*/x)(x=*1*/y, y =*42*)

42



Sage 8.1 gives the following, which is the correct behavior



sage: var('x,y')

(x, y)

sage: (*1*/x)(x=*1*/y, y =*42*)

y

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/180de0eb-c7f3-44cf-bdba-9a6a5b0fdd61%40googlegroups.com.

[sage-devel] Re: Problem with multiple substitutions

[Nils Bruin]

On Thursday, January 30, 2020 at 8:54:56 AM UTC-8, Ties Laarakker wrote:
>
> There's a probem with multiple substitutions in Sage 9.0.
>
>
>
> sage: var('x,y')
>
> (x, y)
>
> sage: (*1*/x)(x=*1*/y, y =*42*)
>
> 42
>
>
> That is indeed very strange an worrisome. For further diagnostics: this 
also happens with a straight "subs":

(1/x).subs({x:1/y, y:42})

This calls straight into Pynac, so a change there must have caused this 
(8.9 has the same problem).

It seems to depend on the actual substitution:

(1/x).subs({x:y,y:42})

works fine. This should definitely be filed as a bug and reported 
"upstream" (I'm not so sure pynac gets much usage outside sage).

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/271ee9f0-0ae6-40bb-8696-49777f3bb3ae%40googlegroups.com.

[sage-devel] Re: Unable to build sage after git trac config

[John H Palmieri]

On Wednesday, January 29, 2020 at 3:04:12 PM UTC-8, Vipul Gupta wrote:
>
> Hello,
> I am using Ubuntu 18.04.3 LTS with sage version 9.1 beta 2
>  After using below command
> git clone git://github.com/sagemath/sage.git
> cd sage
> git checkout develop
> make
>

Okay up to here. Before doing the next command, cd to a different 
directory: there is no reason to clone the git-trac-command repository 
within the Sage directory, and I suppose it could cause problems.
 

> git clone https://github.com/sagemath/git-trac-command.git
> source git-trac-command/enable.sh
> echo $PATH
> cd git-trac-command
>

Rather than the following command, I would recommend the directions in the 
file README.md, included with git-trac-command.
 

> ln -s `pwd`/git-trac ~/bin/
>

git trac config --user USERNAME --pass 'PASSWORD'
> ssh-add
> I was unable to build sage
>

What went wrong? Just installing git-trac-command should not interfere with 
building Sage. Could you provide the file `logs/install.log`? (Maybe delete 
that file first, then run `make`, which will produce a new log file, and 
attach the new one.)
 

> I tried using './sage -br' and 'make' also.
> But it is still not working 
> I am attaching the log file here.
>

The file output.txt has strange entries at the top, and the official log 
file might be more helpful.
 

> Kindly help me with this I am new here.
> Regards 
> Vipul  Gupta
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/68397413-bb47-4b4f-960b-c35833c03c7e%40googlegroups.com.

[sage-devel] Re: emacs sage-shell mode and hs-mode

['Martin R' via sage-devel]

On the stackexchange site there is now an initial attempt to fix this, 
which is unfortunately not working on my computers.  However, maybe others 
are luckier

Martin

Am Sonntag, 26. Januar 2020 09:07:10 UTC+1 schrieb Martin R:
>
> I asked the same question at 
> https://emacs.stackexchange.com/questions/55129/hs-minor-mode-and-sage-shell-mode-derived-from-python-mode,
>  
> but without any response so far.
>
> Martin
>
> Am Samstag, 25. Januar 2020 12:58:46 UTC+1 schrieb Martin R:
>>
>> Dear sage n emacs users!
>>
>> I would like to use emacs' hide-show mode (to collapse class and function 
>> definitions) with Sho Takemori's sage-shell mode.
>>
>> hs-mode works with python mode, but not (out of the box) with sage-shell 
>> mode, although it is derived from python-mode
>>
>> Has anybody tried or even achieved that yet?
>>
>> Martin
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/eea8b38a-85d3-491e-986f-524f6fd5a184%40googlegroups.com.

Re: [sage-devel] How to deal with unsorted output of dictionaries in doctests

[Markus Wageringel]

Am Dienstag, 28. Januar 2020 00:41:55 UTC+1 schrieb Michael Orlitzky:
>
> The insertion order is part of the language as of python-3.7, and can't 
> be changed: 
>
> * https://mail.python.org/pipermail/python-dev/2017-December/151283.html 
> * https://docs.python.org/3.7/tutorial/datastructures.html#dictionaries 
>
> So while it sucks, I guess we should update all of the doctests to print 
> in that order. It was always a bad idea to rely on them being sorted, 
> and I don't think I agree with making the order part of the language, 
> but that's what we've got. 
>

While the order of dictionaries is insertion order now, functions in Sage 
or in libraries that return dictionaries usually do not make any promise 
about the order in which elements are inserted into the dictionary. Thus, 
when doctesting such a function, the order of the result is not specified 
and might easily change by a seemingly unrelated change in our code base. 
This is not a huge problem, as we can update any failing doctests, but we 
could also make the doctests more robust in the first place, by sorting the 
output.



>From the different options mentioned here, my preferred choices are

2c) `pretty_print(D, sort=True)` for clarity, or

2d) `dict(sorted(D.items()))` for simplicity, as this makes use of 
well-known functions and does not require any other changes.

As Nils explained, for 2c (and even independently) it would make sense to 
change the default display mode from `None` to `plain` in the command line, 
but this would lead to a small dichotomy between the command line and the 
notebook, which is why I am slightly hesistant about this. It would make it 
a bit more difficult to doctest the notebook behavior. Therefore, I am 
leaning toward 2d, which should be an uncontroversial change and is similar 
to the `sorted(...)` idiom already used in the doctests.
 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/01d7ee8c-7e7c-4426-be3f-24d9161bd58f%40googlegroups.com.

Re: [sage-devel] How to deal with unsorted output of dictionaries in doctests

[Nils Bruin]

On Thursday, January 30, 2020 at 12:52:06 PM UTC-8, Markus Wageringel wrote:
>
> From the different options mentioned here, my preferred choices are
>
> 2c) `pretty_print(D, sort=True)` for clarity, or
>
> 2d) `dict(sorted(D.items()))` for simplicity, as this makes use of 
> well-known functions and does not require any other changes.
>
> As Nils explained, for 2c (and even independently) it would make sense to 
> change the default display mode from `None` to `plain` in the command line, 
> but this would lead to a small dichotomy between the command line and the 
> notebook, which is why I am slightly hesistant about this. It would make it 
> a bit more difficult to doctest the notebook behavior.
>

I do not think that's an issue at all. Presently, on the command line we 
*literally* get

sage: pretty_print({1:2})
\newcommand{\Bold}[1]{\mathbf{#1}}\left\{1 : 2\right\}

I don't think that satisfies anybody's idea of "pretty" printing. If you do 
the same thing in the notebook, you get a nicely mathjax typeset 
expression. We can't replicate that behaviour on the command line anyway, 
so going with "plain" wouldn't break anything: commandline and notebook 
already behave very differently.

It is the case that

  get_display_manager().preferences.text is None

holds in both at the moment, but we have that 

  get_display_manager()

prints as 'The Sage display manager using the IPython command line backend' 
and 'The Sage display manager using the IPython notebook backend' 
respectively, so they're already distinguishable. Setting different 
defaults in these different cases doesn't seem like a problem to me.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/ac84bf60-ed0c-46a1-9092-9e47b9970295%40googlegroups.com.

Re: [sage-devel] How to deal with unsorted output of dictionaries in doctests

[Nils Bruin]

On Thursday, January 30, 2020 at 1:17:14 PM UTC-8, Nils Bruin wrote:
>
> prints as 'The Sage display manager using the IPython command line 
> backend' and 'The Sage display manager using the IPython notebook backend' 
> respectively, so they're already distinguishable. Setting different 
> defaults in these different cases doesn't seem like a problem to me.
>
> Oops, and as the documentation of display_manager says, in doctests, you 
get back: 'The Sage display manager using the doctest backend', so there's 
a third one! Perhaps we should try and keep that one aligned with the 
command line, since those both communicate through character streams 
(whereas the notebook one communicates through a message passing interface) 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/4d1404b7-4c87-4d34-bfdf-b08f2285abe5%40googlegroups.com.

Re: [sage-devel] How to deal with unsorted output of dictionaries in doctests

[Michael Orlitzky]

On 1/30/20 3:52 PM, Markus Wageringel wrote:
> 
> While the order of dictionaries is insertion order now, functions in
> Sage or in libraries that return dictionaries usually do not make any
> promise about the order in which elements are inserted into the
> dictionary. Thus, when doctesting such a function, the order of the
> result is not specified and might easily change by a seemingly unrelated
> change in our code base. This is not a huge problem, as we can update
> any failing doctests, but we could also make the doctests more robust in
> the first place, by sorting the output.

This is a good point, but it's a problem we already have. We don't make
any promises about the precise message contained in e.g. a ValueError,
but we still frequently test the contents. You just update it when you
change the message. The doctest is more of a sanity check here, telling
you that you've got two different answers and to go figure out which one
is right. If the code is right, you update the doctest.

The downside to sorting everything in the tests it that running the
tests already takes several hours (8+ here). How many CPU hours do we
collectively burn by sorting something 1293752893 times instead of
updating the test once?

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/093109f2-575e-fd71-616d-0d82e7aa1949%40orlitzky.com.

Re: [sage-devel] How to deal with unsorted output of dictionaries in doctests

[Markus Wageringel]

Rather than distinguishing the different backends, I was more worried about how 
to keep what related doctests currently give us. For example, in 
src/doc/fr/tutorial/latex.rst, pretty_print is advertised as a way to obtain 
nicely formatted MathJax output:

sage: pretty_print(x^12)
\newcommand{\Bold}[1]{\mathbf{#1}}x^{12}

I suppose this is exactly what is used in the notebook to format the output. If 
the default display mode was `plain`, I would not know how to rephrase this 
doctest other than changing the display mode before and after the test, which 
is suboptimal in the tutorials.

Admittedly though, with the command line backend, the same command outputs

sage: pretty_print(x^12)
\newcommand{\Bold}[1]{\mathbf{#1}}x^{12}

so arguably a dichotomy is already there. With display mode `plain`, we get

sage: pretty_print(x^12)
x^12

which is the same as just printing the object.

It seems generally difficult, if not impossible, to write tests for different 
backends, as we only use the doctest backend during doctests. Though, I assume 
that the MathJax output is sufficiently tested elsewhere, so changing the 
default behavior of pretty_print for the commandline and doctests should not be 
a problem after all.


> Am 30.01.2020 um 22:21 schrieb Nils Bruin :
> 
> On Thursday, January 30, 2020 at 1:17:14 PM UTC-8, Nils Bruin wrote:
> prints as 'The Sage display manager using the IPython command line backend' 
> and 'The Sage display manager using the IPython notebook backend' 
> respectively, so they're already distinguishable. Setting different defaults 
> in these different cases doesn't seem like a problem to me.
> 
> Oops, and as the documentation of display_manager says, in doctests, you get 
> back: 'The Sage display manager using the doctest backend', so there's a 
> third one! Perhaps we should try and keep that one aligned with the command 
> line, since those both communicate through character streams (whereas the 
> notebook one communicates through a message passing interface) 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/B3C05557-4D6F-4B5F-9ABA-4493A5CDBB2E%40gmail.com.

Re: [sage-devel] How to deal with unsorted output of dictionaries in doctests

[Markus Wageringel]

> Am 30.01.2020 um 23:10 schrieb Michael Orlitzky :
> 
> This is a good point, but it's a problem we already have. We don't make
> any promises about the precise message contained in e.g. a ValueError,
> but we still frequently test the contents. You just update it when you
> change the message. The doctest is more of a sanity check here, telling
> you that you've got two different answers and to go figure out which one
> is right. If the code is right, you update the doctest.

I agree a doctest is easily updated when things change, but errors could easily 
be introduced as well. Ideally a test is written in a way that it does not test 
more than necessary – and the iteration order of dictionaries usually does not 
need to be tested.

> The downside to sorting everything in the tests it that running the
> tests already takes several hours (8+ here). How many CPU hours do we
> collectively burn by sorting something 1293752893 times instead of
> updating the test once?

Although there are many tests outputting dictionaries, these are usually very 
small, so I do not expect this to have a big impact on running times. Besides, 
dictionaries are currently sorted via IPython during testing as well.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/5318CC36-7274-4849-9CDF-616405786930%40gmail.com.

[sage-devel] Error building Sage 9.0 on CentOS 7.5

[Josh Bevan]

Hello,

I'm trying to build Sage 9.0 from source on CentOS 7.5.1804 and it fails 
with:
"Error installing package sqlite-329"
Here is the ".../sage-9.0/logs/pkgs/sqlite-329.log" log file that the 
error message says to include:
https://pastebin.com/SCy98UXK

The two main messages that jump out to me are:
"configure: WARNING: unrecognized options: --disable-maintainer-mode" I had 
seen that option listed in a post from a decade ago as a solution to a Sage 
Sqlite build error, although I doubt that is still relevant
and
" WARNING: 'aclocal-1.15' is missing on your system." Which seems 
unimportant since it's followed with the text "You only need it if..." with 
reasons that don't pertain to me.

For some additional context:
This is being built on a cluster with SGE (Sun Grid Engine) and uses Lmod 
for a module system. I have gcc 8.3.0, python 3.6.9, and blis 0.6.0 
(OpenBLAS alternative with better performance) modules loaded, any other 
dependencies (e.g. Perl) I've left as the system defaults and they have not 
been overridden by the module system. I unpacked the zip and simply ran 
"make" with no additional messing with config or modifications.

If there is any additional info I should supply that would prove helpful 
feel free to let me know.

Thanks!
Josh

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/98041908-f9f6-47d6-9885-6126dffab1d9%40googlegroups.com.

Re: [sage-devel] Error building Sage 9.0 on CentOS 7.5

[Isuru Fernando]

> " WARNING: 'aclocal-1.15' is missing on your system." Which seems
unimportant since it's followed with the text "You only need it if..." with
reasons that don't pertain to me.

One possible reason is that somehow the timestamps for the files got messed
up. Easiest solution would be to install automake 1.15. You can also do a
make clean and try again.

Isuru

On Thu, Jan 30, 2020 at 9:00 PM Josh Bevan  wrote:

> Hello,
>
> I'm trying to build Sage 9.0 from source on CentOS 7.5.1804 and it fails
> with:
> "Error installing package sqlite-329"
> Here is the ".../sage-9.0/logs/pkgs/sqlite-329.log" log file that the
> error message says to include:
> https://pastebin.com/SCy98UXK
>
> The two main messages that jump out to me are:
> "configure: WARNING: unrecognized options: --disable-maintainer-mode" I
> had seen that option listed in a post from a decade ago as a solution to a
> Sage Sqlite build error, although I doubt that is still relevant
> and
> " WARNING: 'aclocal-1.15' is missing on your system." Which seems
> unimportant since it's followed with the text "You only need it if..." with
> reasons that don't pertain to me.
>
> For some additional context:
> This is being built on a cluster with SGE (Sun Grid Engine) and uses Lmod
> for a module system. I have gcc 8.3.0, python 3.6.9, and blis 0.6.0
> (OpenBLAS alternative with better performance) modules loaded, any other
> dependencies (e.g. Perl) I've left as the system defaults and they have not
> been overridden by the module system. I unpacked the zip and simply ran
> "make" with no additional messing with config or modifications.
>
> If there is any additional info I should supply that would prove helpful
> feel free to let me know.
>
> Thanks!
> Josh
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/98041908-f9f6-47d6-9885-6126dffab1d9%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CA%2B01voNFFxY7CzwPgbOUHQ6_m%2Bp-DCCECTy6hMDSZhZbrqywZQ%40mail.gmail.com.