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. It spend a lot of time
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 build
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.
Frederi
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 cython modules fail.
> And
Hello,
What is the correct way to start trying to build sage in a python3
(virtual) environnement ?
When I do a "make" inside a py3 virtual env, sage just setups its own
environnement, using py2, of course.
When I try to import parts of sage from an ipython3 session, I run into
several things
