In theory you just need clang.
François
> On 17/09/2016, at 03:18, Travis Scrimshaw wrote:
>
> I could look into the Symmetrica code next week for things like you
> mentioned, but I don't have access to an OS X machine to test.
>
> Best,
> Travis
>
>
> --
> You received this message becaus
For tab completion and so on we want a list of "useful" GAP functions,
excluding internal functions that are not meant for end users.
Unfortunately, there isn't really a good way to get that from GAP. The best
approach seems to be to look for the actually documented functions.
Downside is that
After doing some Sage development, I ran doctests and 2 GAP tests
failed. The reason:
sage: from sage.libs.gap.assigned_names import *
Exiting Sage (CPU time 1m58.64s, Wall time 2m36.84s).
This is almost 2 minutes of CPU time (so it cannot be blamed on I/O) in
a Sage session just doing this. T
I could look into the Symmetrica code next week for things like you
mentioned, but I don't have access to an OS X machine to test.
Best,
Travis
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving ema
Hi,
I thought this was a question for sage-devel because it is about tickets I am
currently working on (#21254 specifically). Sorry for the wrong assumption.
I did try sage -pip install pylint before posting but the results were
identical (even launching it from within sage -sh)
Thanks
S.
Hi,
note that https://ask.sagemath.org is a nice place to ask such questions
that are not related to sage development but still interesting.
Anyway, Sage uses its own Python install, so you should install pylint
within Sage and import it from there.
A priori, the following should work:
Dear all,
I am trying to use pylint to validate some of the code in a patch I wrote for
sage and, unsurprisingly, I am getting several complaints because my
system-wide pylint can't resolve modules like sage.something.
What is the correct way of doing this? Is there any other alternative to
p
On 2016-09-16 02:05, Paul Masson wrote:
What exact steps did you take to build Sage?
Yes, we need more details. In case you upgraded from an older version of
Sage, this is probably an instance of #21441.
--
You received this message because you are subscribed to the Google Groups
"sage-deve
> On 16/09/2016, at 19:43, Jeroen Demeyer wrote:
>
> On 2016-09-15 23:21, Francois Bissey wrote:
>> lcalc: is no surprise. It uses a number of obsolete features, not sure
>> how long gcc itself will build it.
>
> This is a bit off-topic, but for lcalc we should also at some investigate
> wheth
On 2016-09-15 23:21, Francois Bissey wrote:
lcalc: is no surprise. It uses a number of obsolete features, not sure
how long gcc itself will build it.
This is a bit off-topic, but for lcalc we should also at some
investigate whether we really need the package. It could very well be
that all fe
10 matches
Mail list logo
