Whats in the logs?
Did you just apply the most recent OSX update?
On Monday, July 25, 2016 at 4:44:21 AM UTC+2, Paul Masson wrote:
>
> In an effort to get past a recurring issue for reviewing Trac #21034, I
> did "make distclean" followed by "make". Now I am no longer able to build
> Sage as
On Sun, Jul 24, 2016 at 9:07 PM, rjf wrote:
> Maybe flamebait .. see below.
No -- it seems that you might be a little ignorant about the culture
and development of Python. You might try a google search for
python2 python3
--
William (http://wstein.org)
--
You received this message be
Maybe flamebait .. see below.
The decision was made to use Python ( 1?) for whatever reasons
were articulated at the time.
Apparently there is an issue with backward compatibility
requiring rewriting of code. I don't know this first hand.
A more-or-less formal language definition
for the languag
In an effort to get past a recurring issue for reviewing Trac #21034, I did
"make distclean" followed by "make". Now I am no longer able to build Sage
as I have been doing for the last couple months, either the master or
develop branch. This is the error message I keep getting:
* package: atlas
Hi,
Please, may I know how to connect to the sage kernel?
I have tried my way around sage.repl.interpreter without success. (Scanty
information in documentation)
Or do I have to call it from my shell and redirect sys.stdout?
Trying out some GUI I have built
Thanks
--
You received this messag
On Sun, Jul 24, 2016 at 6:38 AM, Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
> On 24/07/16 05:13, Dima Pasechnik wrote:
>>
>> I believe that the work on libGAP interface might better wait for GAP
>> folks to come up with their own libGAP. They refused to merge "our"
>> libGAP, and they say
On Sun, Jul 24, 2016 at 5:22 PM, rjf wrote:
> And then, in a few years Python 4?
> Perhaps there is a lesson here?
Are don't understand what you're saying. Is this flame bait? I can't tell.
William
--
William (http://wstein.org)
--
You received this message because you are subscribed to th
And then, in a few years Python 4?
Perhaps there is a lesson here?
RJF
On Sunday, July 24, 2016 at 6:33:36 AM UTC-7, William wrote:
>
> Hi,
>
> We recently did a survey with a question about why people choose (or
> would choose) something else instead of Sage. There are definitely
> some peop
Is there any deep reason to 2MB attachment limit on Trac? Can it be
increased to, say, 100MB? Would be convenient to be able to upload new
packages there rather than figuring out some place to post them.
Thank you,
Andrey
--
You received this message because you are subscribed to the Google Gr
On 24/07/16 05:13, Dima Pasechnik wrote:
I believe that the work on libGAP interface might better wait for GAP
folks to come up with their own libGAP. They refused to merge "our"
libGAP, and they say they have their own version in the works, which
they need to create a Jupyter kernel for GAP.
I
Hi,
We recently did a survey with a question about why people choose (or
would choose) something else instead of Sage. There are definitely
some people who are deeply concerned by our lack of Python3 support in
Sage.
So, based purely on some user feedback, I would just like to add a
little extra
I believe that the work on libGAP interface might better wait for GAP folks to
come up with their own libGAP. They refused to merge "our" libGAP, and they say
they have their own version in the works, which they need to create a Jupyter
kernel for GAP.
Dima
--
You received this message becau
On Sun, 24 Jul 2016, Volker Braun wrote:
At the same time there is some value to testing seed-dependent ordering;
Sure, it is an implementation detail, but it does help catch errors if you
change something in the code. And sometimes you must make a choice, e.g.
when iterating over an infinite se
At the same time there is some value to testing seed-dependent ordering;
Sure, it is an implementation detail, but it does help catch errors if you
change something in the code. And sometimes you must make a choice, e.g.
when iterating over an infinite set. So before you go around and delete all
One example only:
./sage -t --randorder 0
src/sage/modular/modform_hecketriangle/hecke_triangle_group_element.py
is OK, but same with --randorder 1 gives one error, and with --randorder
21739 gives three errors. This not at all the only example.
I think that patchbot maintainers should use d
15 matches
Mail list logo