On Friday, November 2, 2018 at 10:43:23 AM UTC-7, Jonathan Carifio wrote:
>
> Method 1:
>
> ct1 = 0
> tris = pc.triangulations()
> for _ in tris:
> ct1 += 1
> with open("test1.txt",'w') as f:
> f.write(str(ct1))
>
>
> Method 2:
>
> data2 = list(pc.triangulations())
> ct2 = len(data2)
> with
I tried your solution, it didn't work for me. In jupyter the kernel did not
start, in jupyterlab there was also some style issues.
El lunes, 5 de noviembre de 2018, 14:56:50 (UTC+1), Enrique Artal escribió:
>
> That's true. I just edit the kernel.json for each new release (I read it
> in some tu
Can you provide
/usr/local/soft/sage-8.4/local/var/tmp/sage/build/mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0/src/config.log
as well? Something looks strange in that log.
François
> On 6/11/2018, at 11:41, François Bissey wrote:
>
> Your compiler is very old and right now you are fa
Your compiler is very old and right now you are failing even bootstrapping
a better compiler.
Nevertheless trying to compile those instructions shouldn’t have happened.
Can you post the output of
as —version
please.
François
> On 6/11/2018, at 11:03, Daniel Ouimet wrote:
>
> Hi,
>
> on a Linu
Hi,
on a Linux CentOS 6.10, I have an error compiling:
[mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0] tmp-mul_1.s:
Assembler messages:
[mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0] tmp-mul_1.s:94:
Error: no such instruction: `mulx (%rsi),%r9,%r8'
[mpir-3.0.0-644faf502c56f97
On Saturday, November 3, 2018 at 6:40:07 AM UTC-4, Volker Braun wrote:
> Are you running each of the three computation in the same session, or in 3
> different processes? They should do the same computation, so the only thing I
> can think of is that there is something cached that shouldn't be.
>
Le 05/11/2018 à 19:30, Michael Orlitzky a écrit :
On 11/05/2018 07:26 AM, Xavier Caruso wrote:
Hello,
...
So IMHO, it makes sense (and it would be easier to review) to have two
separated tickets, one for univariate functions and one for multivariate
functions. Don't you agree?
I think the rig
On Mon, Nov 5, 2018 at 7:02 AM Samuel Lelièvre
wrote:
> Dear sage-devel,
>
> The freeze period for the next Debian release starts on
> 12 January 2019, as discussed at
>
> https://trac.sagemath.org/ticket/22626#comment:118
>
> This conditions what functionality users of Debian and its
> derivat
On 11/05/2018 07:26 AM, Xavier Caruso wrote:
> Hello,
> ...
>
> So IMHO, it makes sense (and it would be easier to review) to have two
> separated tickets, one for univariate functions and one for multivariate
> functions. Don't you agree?
I think the right design for piecewise functions is to wo
This code works in Sage 8.3, but not in Sage 8.4.
P. = PolynomialRing(QQ)
I = Ideal([x^3, x*y^2, y^4, x^2*y*z, y^3*z, x^2*z^2, x*y*z^2, x*z^3])
I.hilbert_polynomial()
I haven't yet dug into the cause, but the error it reports is,
AttributeError: 'sage.rings.rational.Rational' obj
> I am trying to marry SageMath and Jupyterhub. I think I got them engaged,
> but the wedding night has a problem:
This is not a Sage + JupyterHub problem as much as a Sage + system Jupyter one.
Packagers have already solved it for various distributions, so, if you
don't need a Sage version compi
That's true. I just edit the kernel.json for each new release (I read it in
some tutorial for jupyterhub+sagemath). I will try this.
El lunes, 5 de noviembre de 2018, 10:20:59 (UTC+1), Kwankyu Lee escribió:
>
> The
>
> On Monday, November 5, 2018 at 5:53:35 PM UTC+9, Jori Mäntysalo wrote:
>>
>>
Hello,
(Sorry for replying so late...)
Le vendredi 26 octobre 2018, Matthias Koeppe a écrit :
> Though it sounds like you only need piecewise functions of a single
> real variable, I would suggest to make the ticket for piecewise linear
> (or polynomial) functions of several variables.
While r
Dear sage-devel,
The freeze period for the next Debian release starts on
12 January 2019, as discussed at
https://trac.sagemath.org/ticket/22626#comment:118
This conditions what functionality users of Debian and its
derivatives (including Ubuntu) will find in Sage for the next
two years, if th
The
On Monday, November 5, 2018 at 5:53:35 PM UTC+9, Jori Mäntysalo wrote:
>
> On Mon, 5 Nov 2018, Enrique Artal wrote:
>
> > For me it works adding "env": { "SAGE_ROOT": "where_SAGE_ROOT_is" } in
> > kernel.json
>
> Thanks, seems to be much better solution.
A problem with this is that it is
On Mon, 5 Nov 2018, Enrique Artal wrote:
For me it works adding "env": { "SAGE_ROOT": "where_SAGE_ROOT_is" } in
kernel.json
Thanks, seems to be much better solution.
Now, what is the best practise for upgrading Sage? Jupyterhub makes it
easy to have several kernels installed, but there is no
For me it works adding "env": { "SAGE_ROOT": "where_SAGE_ROOT_is" } in
kernel.json
El lunes, 5 de noviembre de 2018, 8:21:31 (UTC+1), François Bissey escribió:
>
> Didn’t we have that conversation a couple of months ago?
> The message here comes from this section of code in sage-env
>
> # New v
On Mon, 5 Nov 2018, François Bissey wrote:
I’d be curious about that, but yes that may be off-list.
Of course if I can make a good step-by-step manual, then I will write
about that in this list.
--
Jori Mäntysalo
18 matches
Mail list logo
