[sage-devel] rpy2 fails to build when adding openssl to MacOS prebuilt sage 9 binary

2020-01-09 Thread Zachary Scherr
Hi, I recently tried adding openssl to the app.dmg prebuilt sage 9 binary via: sage -i openssl && sage -f python3. During the rebuild, rpy2 failed with the message: [rpy2-2.8.2.p1] dyld: lazy symbol binding failed: Symbol not found: _timespec_get [rpy2-2.8.2.p1] Referenced from:

[sage-devel] Re: drop python2 compatibility in 9.1 ?

2020-01-09 Thread Volker Braun
* I think its not too difficult to write code that is Python 2.7 + 3.x (for high enough x) compatible, so its not a super pressing issue * We do have a Python 2 buildbot to test for regressions * For semver reasons we should drop Python 2.7 support in Sage 10, not 9.1 Having said that, I'm fine

[sage-devel] Porting .sage files to sage-9.0

2020-01-09 Thread David Roe
I had a recent discussion asking if there are any good tools for porting Sage code to Python 3. Given the recent discussion about how long we support Python 2, it seems like one concrete step we can take to help users is to provide

[sage-devel] Re: Removing reverse graph from CGraph

2020-01-09 Thread David Coudert
I'm in favor of this change. The code is faster and slightly easier to understand. Extra opinions are more than welcome. David. Le mardi 7 janvier 2020 22:42:45 UTC+1, Jonathan Kliem a écrit : > > Dear all, > > currently the sparse graph backend keeps a reversed copy of the graph. > > However,

Re: [sage-devel] Adopting orphaned math packages

2020-01-09 Thread E. Madison Bray
On Thu, Jan 9, 2020 at 4:28 AM Michael Orlitzky wrote: > > On 1/6/20 10:35 AM, E. Madison Bray wrote: > > > > Sorry for the delay; I went ahead and created an empty project under > > our organization and added (I assume) you as a maintainer, so have at > > it: