Re: [sage-devel] Re: Sage on Cygwin status update

More updates, I've been able to install and use most of the packages that I normally would except: - libhomfly won't compile its corresponding pyx file: https://trac.sagemath.org/ticket/22856 - gap3 installed fine but won't run (but this is currently an experimental package, so slightly less

Re: [sage-devel] Re: Sage on Cygwin status update

Okay, I can't get it to run tests: $ ./sage -t src/sage no stored timings available Running doctests with ID 2017-04-22-01-14-29-566bb225. 0 [main] python2.7 5280 child_info_fork::abort: unable to map C:\ cygwin64\home\Travis\sage\local\lib\python2.7\site-packages\psutil\

Re: [sage-devel] Re: RR, coercion of numpy.float32() and clang - coercion experts needed

On Fri, Apr 21, 2017 at 11:29 AM, Dima Pasechnik wrote: > > > On Friday, April 21, 2017 at 3:46:03 PM UTC+1, David Roe wrote: >> >> Quick guess (don't have time to look at this soon): the issue could be in >> the action discovery code, which may try creating elements of

Re: [sage-devel] Re: Sage on Cygwin status update

I also used atlas as my blas, using gcc 6.3, did it in parallel, and did not build the docs. Best, Travis On Friday, April 21, 2017 at 8:03:32 PM UTC-5, Travis Scrimshaw wrote: > > I was able to build and run Sage with the positively reviewed Cygwin > tickets plus: > > >-

Re: [sage-devel] Re: Sage on Cygwin status update

I was able to build and run Sage with the positively reviewed Cygwin tickets plus: - https://trac.sagemath.org/ticket/21459 - https://trac.sagemath.org/ticket/21399 (I'm not sure if this was necessary) - https://trac.sagemath.org/ticket/22628 -

Re: [sage-devel] Re: Sage on Cygwin status update

Great! I am in favor of having cygwin as another main goal for 8.0. On 21/04/2017 14:45, Jean-Pierre Flori wrote: Good job! -- 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,

Re: [sage-devel] Re: Sage on Cygwin status update

On Fri, Apr 21, 2017 at 7:24 PM, Travis Scrimshaw wrote: > Ah, I missed https://trac.sagemath.org/ticket/22761. Looks like I didn't include that one in the "Porting: Cygwin" category since it also has a few non-Cygwin-specific changes--oops -- You received this message

Re: [sage-devel] Re: Sage on Cygwin status update

Ah, I missed https://trac.sagemath.org/ticket/22761. Best, Travis -- 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

Re: [sage-devel] Re: Sage on Cygwin status update

On Fri, Apr 21, 2017 at 5:49 PM, Travis Scrimshaw wrote: > That's great to hear. > > What about the latest version of R? This is where I'm currently stuck on my > Cygwin64 build. What about it? It works for me... -- You received this message because you are subscribed to

[sage-devel] Re: can't upload slides of SageDays86 on the wiki

> I am currently at https://wiki.sagemath.org/days86 where we had great > presentations during the week by James Mitchell (GAP libsemigroup), > Jennifer Balakrishnan (Three problems in number theory), François Bergeron > (experimental mathematics) and Thierry Monteil (gems of

Re: [sage-devel] SageNB -> Jupyter conversion needs testers

> Let me remind that there are various tickets regarding the > SageNB->Jupyter conversion which need review: > > #22668: HTML widget without description > #22654: Implement %%fortran in Jupyter > #22636: Make the Sage interact library work in Jupyter > > And please anyone who can test the

Re: [sage-devel] can't upload slides of SageDays86 on the wiki

Hi, i am not admin on the wiki, but setting client_max_body_size variable to a larger number (or 0 for infinity) should fix the issue. Ciao, Thierry On Fri, Apr 21, 2017 at 08:16:10AM -0700, Sébastien Labbé wrote: > Bonjour to all, > > I am currently at https://wiki.sagemath.org/days86 where

[sage-devel] Re: Sage on Cygwin status update

That's great to hear. What about the latest version of R? This is where I'm currently stuck on my Cygwin64 build. Best, Travis -- 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,

Re: [sage-devel] Re: RR, coercion of numpy.float32() and clang - coercion experts needed

On Friday, April 21, 2017 at 3:46:03 PM UTC+1, David Roe wrote: > > Quick guess (don't have time to look at this soon): the issue could be in > the action discovery code, which may try creating elements of numpy.float32 > using weird inputs. This could cause a difference between right and left

[sage-devel] can't upload slides of SageDays86 on the wiki

Bonjour to all, I am currently at https://wiki.sagemath.org/days86 where we had great presentations during the week by James Mitchell (GAP libsemigroup), Jennifer Balakrishnan (Three problems in number theory), François Bergeron (experimental mathematics) and Thierry Monteil (gems of

Re: [sage-devel] Re: RR, coercion of numpy.float32() and clang - coercion experts needed

Quick guess (don't have time to look at this soon): the issue could be in the action discovery code, which may try creating elements of numpy.float32 using weird inputs. This could cause a difference between right and left multiplication. One way to check if this is the source is to try converting

[sage-devel] Re: Sage on Cygwin status update

Good job! -- 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] Sage on Cygwin status update

Hi all, I'd like to report a positive status of the Cygwin port of Sage. As of this week, I *finally* have a custom branch based on top of Sage's develop branch building successfully on Cygwin again, with all tests passing (excluding any optional packages). This was previously the case for Sage

Re: [sage-devel] Re: How about moving the AUTHORS section to the last?

> > > Question: Do you suggest to *manually* move the AUTHORS: section of > > *all* affected docstrings? Or do you merely suggest to modify Sage's > > doc builder I merely suggest the official location of the AUTHORS section, as done in the ticket. > Having more structured docstring would

Re: [sage-devel] Re: How about moving the AUTHORS section to the last?

On Fri, 21 Apr 2017, Simon King wrote: On 2017-04-21, Jori Mantysalo wrote: On Thu, 20 Apr 2017, Kwankyu Lee wrote: I propose to move the AUTHORS section to the last of the heading: +1. Question: Do you suggest to *manually* move the AUTHORS: section of *all*

[sage-devel] Re: How about moving the AUTHORS section to the last?

On 2017-04-21, Jori Mantysalo wrote: > On Thu, 20 Apr 2017, Kwankyu Lee wrote: > >> I propose to move the AUTHORS section to the last of the heading: > > +1. Question: Do you suggest to *manually* move the AUTHORS: section of *all* affected docstrings? Or do you merely

Re: [sage-devel] Re: Trac slow

On Thu, Apr 20, 2017 at 9:10 PM, Dima Pasechnik wrote: > > > On Thursday, April 20, 2017 at 4:04:19 PM UTC+1, Erik Bray wrote: >> >> On Thu, Apr 20, 2017 at 4:54 PM, Dima Pasechnik wrote: >> > >> > >> > On Thursday, April 20, 2017 at 3:38:12 PM UTC+1, Erik

[sage-devel] Re: RR, coercion of numpy.float32() and clang - coercion experts needed

On Friday, April 21, 2017 at 9:11:37 AM UTC+1, Marc Mezzarobba wrote: > > Dima Pasechnik wrote: > > but it looks as if it might be a coercion problem. > > Any ideas where to look? > > Not really, but it does look like the common parent > discovered by the coercion system is incorrect: > >

[sage-devel] Re: RR, coercion of numpy.float32() and clang - coercion experts needed

Dima Pasechnik wrote: > but it looks as if it might be a coercion problem. > Any ideas where to look? Not really, but it does look like the common parent discovered by the coercion system is incorrect: sage: import numpy as np sage: a = np.float('1.5') sage: b = np.float32('1.5') sage:

Re: [sage-devel] How about moving the AUTHORS section to the last?

On Thu, 20 Apr 2017, Kwankyu Lee wrote: I propose to move the AUTHORS section to the last of the heading: +1. -- Jori Mäntysalo