[sage-devel] Re: EMBEDDED_MODE - what, where, and what for

I agree that the whole EMBEDDED_MODE hack is terrible and should go away. I'm working on fixing this in #17234 by providing an interface for hooking into the Sage output. Instead of sprinkling global variables everywhere. On Monday, January 26, 2015 at 12:47:07 AM UTC+1, Andrey Novoseltsev wrot

Re: [sage-devel] gcd vs xgcd

All right #17671 (xgcd for FractionFields) needs review. -- 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 post to this g

[sage-devel] EMBEDDED_MODE - what, where, and what for

Hello, EMBEDDED_MODE is currently set in a few places (e.g. sage.plot.plot and sage.misc.latex independently have EMBEDDED_MODE = False), with other places importing them. For SageCell Jason Grout has changed it to a dictionary living in sage.misc.misc and this change is responsible for most o

Re: [sage-devel] gcd vs xgcd

2015-01-25 23:08 UTC+01:00, Jeroen Demeyer : > On 2015-01-25 22:07, John Cremona wrote: >> I would say that this is undefined since the ideal generated by x+2 >> and x+4 is (2,x) which is not principal. I think that the most useful >> definition of gcd is a generator of the ideal generated by the

Re: [sage-devel] gcd vs xgcd

On 2015-01-25 22:07, John Cremona wrote: I would say that this is undefined since the ideal generated by x+2 and x+4 is (2,x) which is not principal. I think that the most useful definition of gcd is a generator of the ideal generated by the two objects *if* that ideal is principal. I disagree.

Re: [sage-devel] gcd vs xgcd

2015-01-25 22:07 UTC+01:00, John Cremona : > > I would say that this is undefined since the ideal generated by x+2 > and x+4 is (2,x) which is not principal. I think that the most useful > definition of gcd is a generator of the ideal generated by the two > objects *if* that ideal is principal. A

Re: [sage-devel] Re: git trac push error

Should be fixed as well now... On Sunday, January 25, 2015 at 7:37:05 PM UTC+1, Nathann Cohen wrote: > > I still get the same problem with git push :-/ > > Nathann > > ~/sage/misc$ git push trac HEAD:public/17615 > Counting objects: 14, done. > Delta compression using up to 4 threads. > Compr

Re: [sage-devel] gcd vs xgcd

Bonsoir again, 2015-01-25 21:48 UTC+01:00, Bruno Grenet : > Le 25/01/2015 21:26, Vincent Delecroix a écrit : >> Hello Bruno, >> >> Thanks for your answer. >> PS: On a related note, the following looks very wrong to me {{{ sage: x = polygen(ZZ) sage: (x+2).gcd(x+4) 1 }

Re: [sage-devel] gcd vs xgcd

On 25 January 2015 at 20:48, Bruno Grenet wrote: > Le 25/01/2015 21:26, Vincent Delecroix a écrit : >> >> Hello Bruno, >> >> Thanks for your answer. >> PS: On a related note, the following looks very wrong to me {{{ sage: x = polygen(ZZ) sage: (x+2).gcd(x+4) 1 }}} >>>

Re: [sage-devel] gcd vs xgcd

Le 25/01/2015 21:26, Vincent Delecroix a écrit : Hello Bruno, Thanks for your answer. PS: On a related note, the following looks very wrong to me {{{ sage: x = polygen(ZZ) sage: (x+2).gcd(x+4) 1 }}} Why does it look wrong to you? In ZZ[x], (x+2) and (x+4) are two irreducible monic polynomials

Re: [sage-devel] gcd vs xgcd

Hello Bruno, Thanks for your answer. >> PS: On a related note, the following looks very wrong to me >> {{{ >> sage: x = polygen(ZZ) >> sage: (x+2).gcd(x+4) >> 1 >> }}} > > Why does it look wrong to you? In ZZ[x], (x+2) and (x+4) are two > irreducible monic polynomials, so their GCD is 1. Or I am

Re: [sage-devel] gcd vs xgcd

Hello, Le 25/01/2015 21:04, Vincent Delecroix a écrit : Hello, On sage-support somebody reported the following strange behavior sage: gcd(6/1,2/1) 2 sage: xgcd(6/1,2/1) (1, 1/6, 0) I opened #17671 for that and it comes from the fact that there is a custom gcd for QuotientFields but no associat

[sage-devel] gcd vs xgcd

Hello, On sage-support somebody reported the following strange behavior sage: gcd(6/1,2/1) 2 sage: xgcd(6/1,2/1) (1, 1/6, 0) I opened #17671 for that and it comes from the fact that there is a custom gcd for QuotientFields but no associated xgcd. I did it and it work fine. But, in order to get t

Re: [sage-devel] Re: git trac push error

I still get the same problem with git push :-/ Nathann ~/sage/misc$ git push trac HEAD:public/17615 Counting objects: 14, done. Delta compression using up to 4 threads. Compressing objects: 100% (14/14), done. Writing objects: 100% (14/14), 1.27 KiB | 0 bytes/s, done. Total 14 (delta 12), reused

[sage-devel] Re: help with merge conflict resolution

Yes, it does appear to resolve the merge conflict when done this way. The only difference was using git commit instead of committing via the dev scripts (sage -dev commit). It's nice to know it wasn't me not understanding the conflict resolution process, but some issue with the script. On Sun

[sage-devel] Re: help with merge conflict resolution

Yes, my master does have the lastest develop on it. There is a ticket closed between beta5 and beta6 that conflicts with 17067. So the old master merges fine in any case. OK. I'll reset and commit via git and see if that fixes the issue. btw, the 'sagetest -dev commit' is doing the commit via t

[sage-devel] Re: help with merge conflict resolution

Just to be clear, reset master *after* checking it out: git checkout master git fetch trac master git reset --hard FETCH_HEAD On Sunday, January 25, 2015 at 6:01:04 PM UTC+1, Volker Braun wrote: > > old or unrelated to our master branch. You should first update/reset it: > > git fetch trac maste

[sage-devel] Re: help with merge conflict resolution

I don't know what "sagetest -dev commit" does but if it produced the branch that you pushed to 17067 then you should never use it again as that is seriously messed up. Also, your branch merges automatically with the current master. It seems that your local copy of "master" is old or unrelated t

[sage-devel] Re: help with merge conflict resolution

Here are the commands and output. You can see after I complete the commit, I try to merge again, and the conflicts remain. {{{ $ git merge master Removing src/sage/server/nodoctest.py Removing src/sage/server/misc.py Auto-merging src/sage/schemes/projective/projective_point.py CONFLICT (content):

Re: [sage-devel] Re: Error in Building Sage (particularly ecm-6.4)

On 25 January 2015 at 15:49, Dima Pasechnik wrote: > On 2015-01-25, John Cremona wrote: >> On 25 January 2015 at 13:49, Jeroen Demeyer wrote: >>> On 2015-01-25 14:37, Vincent Delecroix wrote: All right. Thanks for your report. That being said, it is sad that Sage fails to bui

[sage-devel] Re: git trac push error

Thank you ! On Sunday, January 25, 2015 at 4:38:38 PM UTC+1, Volker Braun wrote: > > Ok, this should be fixed now 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

[sage-devel] Re: Error in Building Sage (particularly ecm-6.4)

On 2015-01-25, John Cremona wrote: > On 25 January 2015 at 13:49, Jeroen Demeyer wrote: >> On 2015-01-25 14:37, Vincent Delecroix wrote: >>> >>> All right. Thanks for your report. >>> >>> That being said, it is sad that Sage fails to build on Ubuntu 12.04 >>> which is an LTS running until 2017...

[sage-devel] Re: help with merge conflict resolution

If you try to merge a commit that is already in your branch history then git will do nothing (it'll say: Already up-to-date). So you are not doing what you think you are doing at one point. Post the commands that you are using with their full output. On Sunday, January 25, 2015 at 4:08:27 PM

[sage-devel] Re: git trac push error

Ok, this should be fixed now as well. On Sunday, January 25, 2015 at 3:16:33 PM UTC+1, david@inria.fr wrote: > > On Sunday, January 25, 2015 at 1:48:42 PM UTC+1, Volker Braun wrote: >> >> Should be fixed now! >> > > Thanks to what you did I have been able to push my commits, but now when I

Re: [sage-devel] Error in Building Sage (particularly ecm-6.4)

On 25 January 2015 at 13:49, Jeroen Demeyer wrote: > On 2015-01-25 14:37, Vincent Delecroix wrote: >> >> All right. Thanks for your report. >> >> That being said, it is sad that Sage fails to build on Ubuntu 12.04 >> which is an LTS running until 2017... This cannot be right -- until a couple of

[sage-devel] help with merge conflict resolution

I'm working on #17067 to fix a merge conflict. I have fixed a number of merge conflicts in the past with no issues, but every once in awhile I run into the issues I'm having with 17067. I figured it is time to figure out what I'm doing wrong here. - I merge in the lastest beta to my ticket - us

[sage-devel] Re: git trac push error

On Sunday, January 25, 2015 at 1:48:42 PM UTC+1, Volker Braun wrote: > > Should be fixed now! > Thanks to what you did I have been able to push my commits, but now when I got to page http://trac.sagemath.org/ticket/17665 I get: Oops… *Trac detected an internal error:* OSError: Failed to ren

Re: [sage-devel] Error in Building Sage (particularly ecm-6.4)

On 2015-01-25 14:37, Vincent Delecroix wrote: All right. Thanks for your report. That being said, it is sad that Sage fails to build on Ubuntu 12.04 which is an LTS running until 2017... We could blacklist their GCC... (Debian/Ubuntu has a long history of shipping broken versions of GCC, the De

Re: [sage-devel] Error in Building Sage (particularly ecm-6.4)

All right. Thanks for your report. That being said, it is sad that Sage fails to build on Ubuntu 12.04 which is an LTS running until 2017... 2015-01-25 14:34 UTC+01:00, Shadab Zafar : > Well, previously I was trying to build using the latest source (fetched > from git repo) on Ubuntu 12.04 > > W

Re: [sage-devel] Error in Building Sage (particularly ecm-6.4)

Well, previously I was trying to build using the latest source (fetched from git repo) on Ubuntu 12.04 While this time, I updated Ubuntu to 14.04, downloaded the source tarball from the sage site (v6.4.1) and just ran 'make' In short, I didn't do anything special. On Sunday, January 25, 2015

Re: [sage-devel] Error in Building Sage (particularly ecm-6.4)

2015-01-25 13:35 UTC+01:00, Shadab Zafar : > I did succeed in compiling (on Ubuntu 14.04 with GCC 4.9.2) Great! Congratulations. If you have time, could you describe what did you do? It might be useful for other users to know how to face the same situation. Vincent -- You received this message

Re: [sage-devel] Re: git trac push error

2015-01-25 13:48 UTC+01:00, Volker Braun : > Should be fixed now! Thanks Volker. What happened? -- 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+unsubsc

[sage-devel] Re: git trac push error

Should be fixed now! On Sunday, January 25, 2015 at 1:30:57 PM UTC+1, Volker Braun wrote: > > This is a permission error, part of the git repo is now owned by the wrong > user. I'm trying to figure out where the change comes from... > > >> -- You received this message because you are subscribe

Re: [sage-devel] Error in Building Sage (particularly ecm-6.4)

I did succeed in compiling (on Ubuntu 14.04 with GCC 4.9.2) Thanks for your help. On Sunday, January 25, 2015 at 4:59:27 AM UTC+5:30, vdelecroix wrote: > > Hello, > > Strange. It seems that your compiler produced instructions that your > processor does not understand... did you succeed in compi

[sage-devel] Re: git trac push error

This is a permission error, part of the git repo is now owned by the wrong user. I'm trying to figure out where the change comes from... On Sunday, January 25, 2015 at 10:23:49 AM UTC+1, Jeroen Demeyer wrote: > > I get the following error and I have no idea what's going wrong: > > $ git trac p

[sage-devel] Unable to upload changes with 'git trac push'

Hi! I've worked on ticket without any issues. After some work, I've successfully created new git branch and uploaded my fix. Today I decided to upload new stuff, but I've encountered the following issue: [crady@CradyLap sage]$ git trac push Pushing to Trac

Re: [sage-devel] Re: git trac push error

Same without 'git trac': ~/sage/misc$ git push trac HEAD:public/17615 Counting objects: 14, done. Delta compression using up to 4 threads. Compressing objects: 100% (14/14), done. Writing objects: 100% (14/14), 1.27 KiB | 0 bytes/s, done. Total 14 (delta 12), reused 0 (delta 0) error: insufficient

[sage-devel] Re: git trac push error

The same here. -- 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 post to this group, send email to sage-devel@googlegrou

[sage-devel] git trac push error

I get the following error and I have no idea what's going wrong: $ git trac push Pushing to Trac #17583... Guessed remote branch: u/jdemeyer/ticket/17583 Traceback (most recent call last): File "/home/jdemeyer/local/bin/git-trac", line 18, in cmdline.launch() File "/home/jdemeyer/local/s