When I try the 3d plot commands of polyhedron class and polygon3d on the
default jmol viewer, the output doesn't match the command, since I directly
copy these commands from examples in tutorials.
1.
polygon3d([[0,0,1],[0,1,0],[1,0,0]])
This gives a totally empty graph, though the numbers on t
FWIW I think this is not a bad idea, as long as it's effortless to maintain
and someone is already volunteering to do it. If I were spending time on
developing Sage again instead of wrestling with getting Rob's MBX to work
for me ;-) then I think this would help somewhat in prioritizing what I
"./sage -t src/sage/arith.py" gets this.
hundleymac:sage jahundle$ ./sage -t src/sage/arith.py
init.sage does not exist ... creating
no stored timings available
Running doctests with ID 2016-07-07-13-47-14-67aaeb78.
Git branch: develop
Using --optional=mpir,python2,sage
Doctesting 1 file
On Jul 7, 2016 07:13, "Andrew" wrote:
>
> Hi!
>
> How do you doc-test output that starts with ...? The particular output
that I want to test is:
>
> sage: print(CartanType(['A', oo]).ascii_art())
> ...---O---O---O---O---O---O---O---...
> -3 -2 -1 0 1 2 3
>
You could do
sage: print(
Le jeudi 7 juillet 2016 11:13:52 UTC+2, Dima Pasechnik a écrit :
>
>
>
> On Wednesday, July 6, 2016 at 8:22:57 PM UTC+1, Frédéric Chapoton wrote:
>>
>> Dear all,
>>
>> Essentially, print has now been converted to python3-compatible behaviour
>> in all of sage, after a lot of work by many people
Hi Arpit,
Did you try doctesting other parts of Sage to see whether your
segfaults are related to the ticket or not? It could be related to your
system setup.
If this is not the case, you should, as Travis asked you on an earlier
question, try to find a minimal example which causes the bug from t
Hi!
How do you doc-test output that starts with ...? The particular output that
I want to test is:
sage: print(CartanType(['A', oo]).ascii_art())
...---O---O---O---O---O---O---O---...
-3 -2 -1 0 1 2 3
but sage complains with:
ValueError: line 6 of the docstring for sage.combi
On Wednesday, July 6, 2016 at 5:04:33 PM UTC+1, William wrote:
>
>
>
> On Wednesday, July 6, 2016, Erik Bray >
> wrote:
>
>> On Jul 6, 2016 17:40, "William Stein" <> wrote:
>> >
>> > On Wed, Jul 6, 2016 at 8:31 AM, Erik Bray <> wrote:
>> >
>> > > Alternatively, we can do a little better than "an
On Wednesday, July 6, 2016 at 8:22:57 PM UTC+1, Frédéric Chapoton wrote:
>
> Dear all,
>
> Essentially, print has now been converted to python3-compatible behaviour
> in all of sage, after a lot of work by many people
>
shouldn't we release an update to sagenb, to get these changes there into
Hello,
My apologies for not being able to get back sooner. I was working on a
separate ticket this week. And there were some compile errors after Sage
upgraded to 7.3beta6. I've fixed those and pushed the changes. Sage now
builds and running Sage allows access to the functionalities in the
ori
On 2016-07-06 22:17, Vincent Delecroix wrote:
> Indeed
> {{{
> sage: parent(~1) # parent changes
> Rational Field
> sage: parent(1.inverse_of_unit()) # same parent
> Integer Ring
> sage: 2.inverse_of_unit() # error
> Traceback (most recent call last):
> ...
> ZeroDivisio
11 matches
Mail list logo
