Re: [sage-devel] Updates or hints on "latex Function Prevent Simplification"?

2017-01-26 Thread Qian Hong
Dear Deyan, Thanks a lot for the sharing, I enjoy the Math-rich NLP introduction very much, I'll contact with you and see if there is any task I can do in the future :) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this grou

Re: [sage-devel] Re: Updates or hints on "latex Function Prevent Simplification"?

2017-01-26 Thread Qian Hong
Hi Robert, Sorry for long delay, I was troubled by other things. Thanks a lot for the great solution, I tried your code and it works well for most cases, except some corner cases, which is not caused by your function actually: 1. Greek letters Most Greek letters do not work: tex(%beta); $${\it

Re: [sage-devel] Re: how to check zip, map, range, print for Python3

2017-01-26 Thread David Roe
On Thu, Jan 26, 2017 at 8:13 PM, Nils Bruin wrote: > On Thursday, January 26, 2017 at 12:02:07 PM UTC-8, Frédéric Chapoton > wrote: >> >> >> Please, tell me how to change the zip behaviour in the code. Or just >> change the branch if you know how. >> >> If I understand correctly, part of your qu

[sage-devel] Re: how to check zip, map, range, print for Python3

2017-01-26 Thread Nils Bruin
On Thursday, January 26, 2017 at 12:02:07 PM UTC-8, Frédéric Chapoton wrote: > > > Please, tell me how to change the zip behaviour in the code. Or just > change the branch if you know how. > > If I understand correctly, part of your question is "how do I get zip to behave line Py3 in the doctest

Re: [sage-devel] how to check zip, map, range, print for Python3

2017-01-26 Thread David Roe
On Thu, Jan 26, 2017 at 3:47 PM, Frédéric Chapoton wrote: > h, I was hoping for a simpler solution, like putting this in a single > well-chosen file... > I don't see how to do that, just because of the way Python works (though I'd be happy to hear a trick to do this!). When we import code f

Re: [sage-devel] how to check zip, map, range, print for Python3

2017-01-26 Thread Frédéric Chapoton
h, I was hoping for a simpler solution, like putting this in a single well-chosen file... Frederic Le jeudi 26 janvier 2017 21:30:08 UTC+1, David Roe a écrit : > > Don't you just need to add > from six.moves import zip > at the top of every file where zip is used? > David > > On Thu, Jan 26

Re: [sage-devel] how to check zip, map, range, print for Python3

2017-01-26 Thread David Roe
Don't you just need to add from six.moves import zip at the top of every file where zip is used? David On Thu, Jan 26, 2017 at 3:02 PM, Frédéric Chapoton wrote: > Hello, > > your help is required for some Python3-related question, please. > > I would like to have a branch which activates the fut

[sage-devel] how to check zip, map, range, print for Python3

2017-01-26 Thread Frédéric Chapoton
Hello, your help is required for some Python3-related question, please. I would like to have a branch which activates the future behaviour of zip (for example, but range or map are also candidates) both in code and doctests. Here is my tentative for zip, that only change zip behaviour in the d

Re: [sage-devel] patchbot error: HTTP Error 413: Request Entity Too Large

2017-01-26 Thread Daniel Krenn
On 2017-01-26 10:40, Thierry wrote: > the patchbot server is regularly maintained and seems healthy (i just > rebooted it to be sure that the issue does not come from that side). > Apparently, the reason is that your patchbot client sends a log that is > too big. I already met that issue once, the

Re: [sage-devel] Problem building GSL in cygwin64

2017-01-26 Thread Erik Bray
On Thu, Jan 26, 2017 at 5:04 AM, Frank Garvan wrote: > As suggested I did the following: > > cd sage > export SAGE_ATLAS_ARCH=base > ./configure --with-blas=atlas > make > > Go the following error: > > Error building Sage. > > The following package(s) may have failed to build (not necessar

Re: [sage-devel] patchbot error: HTTP Error 413: Request Entity Too Large

2017-01-26 Thread Thierry
Hi, the patchbot server is regularly maintained and seems healthy (i just rebooted it to be sure that the issue does not come from that side). Apparently, the reason is that your patchbot client sends a log that is too big. I already met that issue once, the reason was that i ran a client on a fre

[sage-devel] Re: Bug report: Incorrect json representation for graphics.

2017-01-26 Thread J Soto
I stand corrected. Not Jmol, but canvas3d. Sorry for the mix-up. For the record, this problem bit me when I exported the json representation for processing outside sagemath. It seems that canvas3d is more forgiving with incorrect json input that python own's json module. El jueves, 26 de enero

[sage-devel] patchbot error: HTTP Error 413: Request Entity Too Large

2017-01-26 Thread Daniel Krenn
Starting a patchbot results in the error below. Any ideas? ... [2017-01-26 09:15:56] #0: init phase REPORT {'base': '7.6.beta1', 'deps': [], 'git_base': 'ac31f23ba52013c7aa6cc83660c50bfe9aab952a', 'git_base_human': '7.6.beta1', 'git_branch': 'develop', 'git_commit': 'ac31f23ba52013c7aa6cc8366