I followed the instructions on https://stackoverflow.com/a/18238322 and it
seems to be working so far. I lost all my local branches, but I don't mind.
On Monday, July 24, 2017 at 8:01:03 PM UTC-5, Zachary Gershkoff wrote:
>
> I tried to create a new ticket and link it to an existing local branch
This error with "garbage at end of loose object" is coming back to plague
me. I recently tried to upgrade sage by pulling the develop branch, but I
couldn't.
zgersh2@helmholtz:~/sage$ git checkout develop
Switched to branch 'develop'
zgersh2@helmholtz:~/sage$ git pull
remote: Counting objects:
That's it! You're recommendation worked like a charm. I certainly didn't
appreciate the differences between Sage type and python number types.
Thank you John - very much appreciated. Paul
sage: *from* *py4j.java_gateway* *import* JavaGateway
sage: gateway = JavaGateway()
sage: random =
In Sage, "10" is a Sage integer, not a Python int. I am guessing that
gateway.jvm.java.util.Random.nextInt
expects a Python int for its input, and when it gets a Sage Integer, that
causes a problem. What happens if you replace "random.nextInt(10)" with
"random.nextInt(int(10))"?
On
Hi, I'm new to using Sage and trying to interface to java classes using
py4j. I've been successful using py4j using an anaconda installed version
of python (on a mac) but I'm running into Attribute errors using Sage. The
one below is 'sage.rings.integer.Integer' object has no attribute
Could you give details on:
- your precise operating system version
- how did you install Sage
On 02/08/2017 11:41, 张彪 wrote:
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it,
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
These lines in the log look strange:
checking for ld used by gcc... /usr/lib/gcc/x86_64-linux-gnu/4.8
checking if the linker (/usr/lib/gcc/x86_64-linux-gnu/4.8) is GNU ld... no
That is, from the mpfr's point of view, the linker does not work, thus the
result.
On Wednesday, August 2, 2017 at
