[sage-devel] Re: python3 status report (mi-april of last python2 year)

2019-04-19 Thread 'Martin R' via sage-devel
Sorry: "Should we do this?" should be "Should I do this?" Martin Am Samstag, 20. April 2019 06:31:20 UTC+2 schrieb Martin R: > > In my opinion, `Set` should not be used in library code. It is slow, > unnecessary, and can hide subtle bugs when the underlying object is not > hashable.

[sage-devel] Re: python3 status report (mi-april of last python2 year)

2019-04-19 Thread 'Martin R' via sage-devel
In my opinion, `Set` should not be used in library code. It is slow, unnecessary, and can hide subtle bugs when the underlying object is not hashable. (https://trac.sagemath.org/ticket/23324) For the concrete issue at hand, the use of `Set` could be easily removed in all methods except

Re: [sage-devel] problem compiling the latest development version

2019-04-19 Thread Anne Schilling
Hi Dima, I reinstalled xcode and now sage compiles again. Thanks for your help! Anne On Friday, April 19, 2019 at 12:09:35 PM UTC-7, Dima Pasechnik wrote: > > On Fri, Apr 19, 2019 at 7:20 PM Anne Schilling > > wrote: > > > > Thank you all for your suggestions! Dima's suggestion did not seem

Re: [sage-devel] Re: building doc: u'\xe9' in position 19: ordinal not in range(128)

2019-04-19 Thread Vincent Delecroix
Indeed, this is due to french settings and the offending line is a good news stated in a funny mix of english and french: "build réussi". Changing the offending line to Volker's suggestion does work. I opened ticket [#27706] for that purpose but I am not sure about the Python3 compatible way to

[sage-devel] Re: python3 status report (mi-april of last python2 year)

2019-04-19 Thread Nils Bruin
On Friday, April 19, 2019 at 5:25:13 PM UTC-7, John H Palmieri wrote: > > What does > > sage: C > Set partitions of {'a', 'c', 'b'} > > > reveal? Is it helpful, or can it be omitted? > > Adding to that: perhaps it reveals something for the documentation reader. But in that case the output doesn't

[sage-devel] Re: python3 status report (mi-april of last python2 year)

2019-04-19 Thread John H Palmieri
What does sage: C Set partitions of {'a', 'c', 'b'} reveal? Is it helpful, or can it be omitted? Maybe it's good enough to do sage: C = SetPartitions(["a", "b", "c"]) sage: C.cardinality() 5 sage: sorted(C) [{{'a'}, {'b'}, {'c'}}, {{'a'}, {'b', 'c'}}, {{'a', 'b'}, {'c'}}, {{'a', 'b', 'c'}},

[sage-devel] Re: python3 status report (mi-april of last python2 year)

2019-04-19 Thread Andrew
What the accepted best practice for fixing the failing python3 doc-tests? For example, in `combinat/tutorial.py` I can fix one of the failing doc-tests with: sage: C = SetPartitions(["a", "b", "c"]) sage: C #py2 Set partitions of {'a', 'c', 'b'} sage: C #py3 Set partitions

Re: [sage-devel] problem compiling the latest development version

2019-04-19 Thread Dima Pasechnik
On Fri, Apr 19, 2019 at 9:09 PM Dima Pasechnik wrote: > > On Fri, Apr 19, 2019 at 7:20 PM Anne Schilling > wrote: > > > > Thank you all for your suggestions! Dima's suggestion did not seem to fix > > my problem. > > I did pull from develop again and now the elliptic problem is gone. But the >

Re: [sage-devel] problem compiling the latest development version

2019-04-19 Thread Dima Pasechnik
On Fri, Apr 19, 2019 at 7:20 PM Anne Schilling wrote: > > Thank you all for your suggestions! Dima's suggestion did not seem to fix my > problem. > I did pull from develop again and now the elliptic problem is gone. But the > pillow problem > is still there: do you actually have

Re: [sage-devel] problem compiling the latest development version

2019-04-19 Thread Anne Schilling
Thank you all for your suggestions! Dima's suggestion did not seem to fix my problem. I did pull from develop again and now the elliptic problem is gone. But the pillow problem is still there: [sagelib-8.8.beta3] byte-compiling

Re: [sage-devel] problem compiling the latest development version

2019-04-19 Thread E. Madison Bray
On Fri, Apr 19, 2019 at 8:30 AM Dima Pasechnik wrote: > > On Fri, Apr 19, 2019 at 7:33 AM Anne Schilling > wrote: > > > > This was after I ran 'make distclean'. You can view the logs here: > > > > https://www.math.ucdavis.edu/~anne/elliptic_curves-0.8.p0.log > > ImportError: No module named

[sage-devel] Re: building doc: u'\xe9' in position 19: ordinal not in range(128)

2019-04-19 Thread Volker Braun
Can you change the offending line to self._stream.write(line.encode('utf-8')) On Friday, April 19, 2019 at 4:09:00 PM UTC+2, vdelecroix wrote: > > Dear all, > > I freshly cloned and compile SageMath. Everything went fine until the > documentation where each time sphinx tries to write

Re: [sage-devel] building doc: u'\xe9' in position 19: ordinal not in range(128)

2019-04-19 Thread Dima Pasechnik
French locale settings, no? (other reports of this error come from France, too, IIRC) On Fri, Apr 19, 2019 at 4:09 PM Vincent Delecroix <20100.delecr...@gmail.com> wrote: > > Dear all, > > I freshly cloned and compile SageMath. Everything went fine until the > documentation where each time sphinx

[sage-devel] Automatic Differentiation - Taylor Arithmetics

2019-04-19 Thread Nisoli Isaia
Dear all, I was planning in doing a Cython implementation of Forward automatic differentiation and Taylor arithmetics as in https://press.princeton.edu/titles/9488.html to use to implement a library for Sage with rigorous quadrature and integration of ODE. I'm trying to understand which

Re: [sage-devel] problem compiling the latest development version

2019-04-19 Thread Dima Pasechnik
On Fri, Apr 19, 2019 at 7:36 AM Anne Schilling wrote: > > > > On Thursday, April 18, 2019 at 10:09:20 PM UTC-7, François Bissey wrote: >> >> And it has to be 8.8.beta2 or lower not beta3 which is the latest. >> elliptic_curves has been >> bumped to 0.8.1 in beta3. > > > I did > > git pull > make

Re: [sage-devel] problem compiling the latest development version

2019-04-19 Thread Dima Pasechnik
On Fri, Apr 19, 2019 at 7:33 AM Anne Schilling wrote: > > This was after I ran 'make distclean'. You can view the logs here: > > https://www.math.ucdavis.edu/~anne/elliptic_curves-0.8.p0.log ImportError: No module named _sqlite3 This look like a silent failure in building sqlite3, which is a