>
> Which operating systems / distros would be affected by this (i.e., only
> ship with 2.6.x [and probably some older 3.x])?
>
What I'd seriously worry about here is RHEL 6 and derivatives (CentOS,
SciLinux). It only comes with Python 2.6 by default, and while old (came
out in 2010), it is
John H Palmieri wrote:
> Building Sage requires a system installation of Python. So far Python
> 2.6 has been good enough, and when changes were made to inadvertently
> break this (one as recent as March: see
> https://groups.google.com/forum/#!msg/sage-devel/1hbXSJFWDZw/NNP9L2V9DQAJ),
> people com
Building Sage requires a system installation of Python. So far Python 2.6
has been good enough, and when changes were made to inadvertently break
this (one as recent as March: see
https://groups.google.com/forum/#!msg/sage-devel/1hbXSJFWDZw/NNP9L2V9DQAJ),
people complained.
Now the plan is to
Afaik this is the expected result: Compiled modules (both bytecode pyc or
binary so) are versioned and will not be loaded if there is a version
mismatch.
On Friday, June 10, 2016 at 3:10:56 PM UTC-4, Frédéric Chapoton wrote:
>
> ok, sorry for being so dumb and unclear. Please be patient. Let m
ok, sorry for being so dumb and unclear. Please be patient. Let me try to
be more clear.
Currently I do that:
* enter a python3 virtual env (using source mypy3/bin/activate)
* cd sage/src
* launch ipython
* import sage
* from sage.interfaces.all import *
resulting in
ImportError: No module named
Whats your question
a) you want to build Sage in a py3 environment? Then build Sage in a py3
environment. What hat do you mean by "flag to pass to make"??
b) you want to build Sage in a py2 environment but you want Sage to build
its own Python 3. Then run "SAGE_PYTHON3=yes make"
On Friday
On page 3 at the top, is that a typo with how (9)(1/2) is formatted?
--
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 p
Relying on what Maxima does for infinities is probably not a great tactic.
There are two models, conflicting and yet both in use. And neither one
quite covers what you might want.
See
http://people.eecs.berkeley.edu/~fateman/papers/infinity.pdf
for some discussion. Is there "one point" where +-
Sure, but how can I try ? Is there something like a flag to pass to make ?
Le vendredi 10 juin 2016 20:19:38 UTC+2, Volker Braun a écrit :
>
> Sage is supposedly requiring Python 2.7 or 3.3+ to build, but it isn't
> tested with py3 so its unlikely to actually work.
>
>
>
> On Friday, June 10, 201
Sage is supposedly requiring Python 2.7 or 3.3+ to build, but it isn't
tested with py3 so its unlikely to actually work.
On Friday, June 10, 2016 at 2:10:38 PM UTC-4, Frédéric Chapoton wrote:
>
> Hello,
>
> What is the correct way to start trying to build sage in a python3
> (virtual) environn
Will there be a trac made about this?
On Tuesday, June 7, 2016 at 3:36:50 PM UTC-5, john_perry_usm wrote:
>
> This surprised me today:
>
> > limit(1/x, x=0)
> Infinity
>
> I was expecting something more like this:
>
> > limit(x/abs(x), x=0)
> und
>
> The help on Infinity wasn't illuminating:
>
>
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
Something else you can do on the Sage side is to have something like:
try:
from sage.foo import Bar
except ImportError:
pass
So it only gets included into the global namespace if you have the module
installed.
Best,
Travis
--
You received this message because you are subscribed to the
13 matches
Mail list logo
