[sage-devel] Re: Plotting arccsch() in Sage 7.2

On Sunday, June 12, 2016 at 3:07:07 AM UTC+2, kcrisman wrote: > > There may have been some change in Pynac that leads it to return complex > values more often now? > I have no idea abot plot(). How to determine which values are offending? -- You received this message because you are subscribed

[sage-devel] Re: Plotting arccsch() in Sage 7.2

There may have been some change in Pynac that leads it to return complex values more often now? On Saturday, June 11, 2016 at 6:43:42 PM UTC-4, Paul Masson wrote: > > Attempting a simple plot( arccsch(x),-1,1) leads to the error message > > verbose 0 (3531: plot.py, generate_plot_points)

[sage-devel] Plotting arccsch() in Sage 7.2

Attempting a simple plot( arccsch(x),-1,1) leads to the error message verbose 0 (3531: plot.py, generate_plot_points) WARNING: When plotting, failed to evaluate function at 200 points. verbose 0 (3531: plot.py, generate_plot_points) Last error message: 'can't convert complex to float' while

[sage-devel] Re: Abandon Python 2.6 support?

William Stein wrote: > On Saturday, June 11, 2016, Volker Braun > wrote: > > Note that we can trivially support Python 2..6 just by vendoring > argparse.py. Make user's lives easier or save a few kilobytes of > disk space? How is

[sage-devel] Re: Build Error for 7.3 beta 3 on Mac OS X 10.11.5

Thank you so much, that fixed the problem! On Tuesday, June 7, 2016 at 6:13:24 PM UTC-5, Paul Masson wrote: > > You need to perform an explicit installation of the Xcode command line > tools. I had the same error recently and that solved it. -- You received this message because you are

Re: [sage-devel] import and build with py3

On Saturday, June 11, 2016 at 12:27:50 PM UTC+1, William wrote: > > > > On Saturday, June 11, 2016, Frédéric Chapoton > wrote: > >> ok, thanks. >> >> But now I did "make" inside the py3 virtualenv. So I have a copy of sage >> build using py3 (do I ? I am not sure at all.

[sage-devel] Re: Abandon Python 2.6 support?

On Saturday, June 11, 2016 at 2:48:30 PM UTC+1, Volker Braun wrote: > > Note that we can trivially support Python 2.6 just by vendoring > argparse.py. Make user's lives easier or save a few kilobytes of disk > space? How is this not a total slam-dunk? > I didn't object to this on #19984, I

Re: [sage-devel] Abandon Python 2.6 support?

On Saturday, June 11, 2016, Volker Braun wrote: > Note that we can trivially support Python 2.6 just by vendoring > argparse.py. Make user's lives easier or save a few kilobytes of disk > space? How is this not a total slam-dunk?-- > Huge +1 > You received this

[sage-devel] Re: Abandon Python 2.6 support?

Note that we can trivially support Python 2.6 just by vendoring argparse.py. Make user's lives easier or save a few kilobytes of disk space? How is this not a total slam-dunk? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from

Re: [sage-devel] import and build with py3

On Saturday, June 11, 2016 at 1:27:50 PM UTC+2, William wrote: > > I'm confused by this whole thread. Why exactly do you think what you want > to do is even possible? > Sage does not support python3 yet. > I'm also confused; Though what should work is: Use Python 3.3+ to satisfy Sage's

Re: [sage-devel] import and build with py3

Yes, I am *fully aware* that this will not work. You may have noticed that I tried to advance towards python3 compatibility in the last few months. My aim is simple: I want to try and *see where it fails*. This could either stop on known issues, or help to discover unexpected problems.

Re: [sage-devel] import and build with py3

On Saturday, June 11, 2016, Frédéric Chapoton wrote: > ok, thanks. > > But now I did "make" inside the py3 virtualenv. So I have a copy of sage > build using py3 (do I ? I am not sure at all. It spend a lot of time > building python2.7). > And still the same imports of

[sage-devel] Re: import and build with py3

ok, thanks. But now I did "make" inside the py3 virtualenv. So I have a copy of sage build using py3 (do I ? I am not sure at all. It spend a lot of time building python2.7). And still the same imports of cython modules fail. And sage runs and works, but behaves in a totally "python2" way, for