ing the other thread, did you try "make distclean" and then
> "make build"? Sometimes larger incremental builds have caused me problems
> in the past, where the solution was the distclean.
>
> Best,
> Travis
>
> On Friday, May 12, 2017 at 9:03:06 AM UTC-5,
Trying to build 8.0.beta5, I get the following error:
[cython-0.25.2.p1] Thread model: posix
[cython-0.25.2.p1] gcc version 4.9.4 (Ubuntu 4.9.4-2ubuntu1~14.04.1)
[cython-0.25.2.p1]
[cython-0.25.2.p1] Unable to find pgen, not compiling formal gra
gt; than what you had installed. I would try running "make build".
>
> Best,
> Travis
>
>
> On Friday, May 12, 2017 at 8:39:36 AM UTC-5, Peleg Michaeli wrote:
>>
>> Only now I see that I have the same problem in branch develop (but not in
>> master). Mayb
Only now I see that I have the same problem in branch develop (but not in
master). Maybe I should build sage again. I'll try that.
On Friday, 12 May 2017 15:34:29 UTC+3, Peleg Michaeli wrote:
>
> Trying to review a ticket (
> https://trac.sagemath.org/ticket/22564#comment:5), I ch
Trying to review a ticket
(https://trac.sagemath.org/ticket/22564#comment:5), I checked out into a
branch, but then trying to run sage I got:
Error: You must set either the SAGE_LOCAL or SAGE_SCRIPTS_DIR environment
variable to run this
Error setting environment variables by sourcing
'/ho
Hi,
log(1+x).limit(x=-1)
returns Infinity, but should return -Infinity. It seems that the sympy
algorithm solves this issue. Is this a known bug?
Note also that `dir='+'` solves this, but the docs say that leaving
`dir=None` should compute the two-sided limit (so perhaps a ValueError
should b
> you might simplify infinity-infinityto 0,
Well, this is the wrong thing here... but sage is smarter than that, I
believe.
On Saturday, 11 March 2017 19:09:07 UTC+2, rjf wrote:
>
>
>
> On Wednesday, March 1, 2017 at 2:11:41 AM UTC-8, Peleg Michaeli wrote:
>>
>> Hi,
Reported in
https://trac.sagemath.org/ticket/22566
and in
https://trac.sagemath.org/ticket/22567
On Thursday, 2 March 2017 11:56:05 UTC+2, Ralf Stephan wrote:
>
> Opening a ticket for bugs is always a good idea.
>
> On Wednesday, March 1, 2017 at 11:11:41 AM UTC+1, Peleg Michaeli wro
So all of this means that there's no need to report it on sage trac, but
rather simply wait for maxima's fix?
On Sunday, 15 January 2017 20:55:47 UTC+2, Nils Bruin wrote:
>
> This indeed seems to be a problem in maxima itself. With
>
> domain : complex;
> limit( (1/(c*n^6))^(log(n)/log(2/3)), n,
Hi,
I have two questions, one might be thought of as a bug report / feature
request, please tell me what you think. Trying
integrate(x, x, 0, infinity)
raises ValueError: Integral is divergent.
My first question: why it does not simply return infinity? (it does, by the
way, if one chooses algor
Well, if you open such a ticket let us know; I'll gladly add stuff there.
On Thursday, 23 February 2017 17:43:29 UTC+2, Michael Orlitzky wrote:
>
> On 02/23/2017 08:15 AM, Peleg Michaeli wrote:
> > Is it not far better to have log2 as a function (log2(x) = log(x, 2))
> &
Is it not far better to have log2 as a function (log2(x) = log(x, 2)) than
having it as a constant?
It's a bit weird that one tries log2(3) and gets "ValueError: the number of
arguments must be less than or equal to 0".
If log2 is about to stay a constant, it might be better to throw a more
us
h Sage,
> turned
> > out to be buggy, and then abandoned by its original
> > author...
> >
> > On Wednesday, February 22, 2017 at 11:32:55 AM UTC, Peleg Michaeli
> wrote:
> >>
> >> Hi,
> >>
> >> We may wish to consider embeddi
Hi,
We may wish to consider embedding this:
http://algo2.iti.kit.edu/kalp/
into sage, or copying its algorithm.
Peleg.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send
I see, great, thanks!
On Fri, 3 Feb 2017 at 17:32 Dima Pasechnik wrote:
>
>
> On Friday, February 3, 2017 at 3:29:48 PM UTC, Peleg Michaeli wrote:
>
> In my sage folder, now after rebuilding latest version (7.6.beta2), I
> figured out that the source appears twice: once in `./
In my sage folder, now after rebuilding latest version (7.6.beta2), I
figured out that the source appears twice: once in `./src/sage` and once in
`./local/lib/python2.7/site-packages/sage`. It doesn't look like a symlink.
When I run the binary, and do something like "Graph??", I see
`/local/lib
The following attempt:
sage: var('c,n')
sage: (1/(c*n^6))^log(n,2/3).limit(n=infinity)
Is ok (raises ValueError), but the following attempt:
sage: var('c,n')
sage: f = (1/(c*n^6))^log(n,2/3)
sage: f.limit(n=infinity)
hangs a little while, the prints a lot of times
;;;
;;; Detected access to pr
OK then, I'll simply add aliases in the docstrings (however, note that
there are places in sage with such aliases, such as `am =
adjacency_matrix`).
On Thursday, 8 December 2016 00:17:07 UTC+2, Sébastien Labbé wrote:
>
>
> I dunno. Aliases are a source of ambiguity and confusion -- my advice
>>
I have an ongoing problem with understanding how I should treat aliases in
Sage.
I have implemented a new method for Graph, named *degeneracy*. Another term
which is sometimes used to describe degeneracy is *linkage*. So I have
something like:
@doc_index("Degeneracy")
def degeneracy(self):
t;
>
> Le mardi 6 décembre 2016 17:31:20 UTC+1, Frédéric Chapoton a écrit :
>>
>> DO NOT TOUCH the import of range from six.moves ! This is part of our
>> general move toward python3 !
>>
>> And do never use xrange, this is now forbidden.
>>
>> Frederi
I actually think that this is an unwanted behaviour of `six`.
Anyway, we may let `Graph` handle xrange lists of neighbours if we want to
keep it that way.
On Tuesday, 6 December 2016 17:18:29 UTC+2, Peleg Michaeli wrote:
>
> I have tried to move LollipopGraph into families, but there
popGraph (as done with BarbellGraph), but
I am not sure you consider this as the right direction to go.
What do you think?
On Wednesday, 30 November 2016 00:40:21 UTC+2, Dima Pasechnik wrote:
>
>
>
> On Tuesday, November 29, 2016 at 4:42:51 PM UTC, Peleg Michaeli wrote:
>>
&g
Hi Travis,
Thanks, I did not know that...
On Thursday, 1 December 2016 16:35:55 UTC+2, Travis Scrimshaw wrote:
>
> Hey Peleg,
>You should also only define the reference (i.e., the .. [XYZ] part) in
> the master references file in doc/en/reference/references/index.rst.
>
> Best,
> Travis
>
>
56 UTC+2, Peleg Michaeli wrote:
>
> Yes.
>
> On Thursday, 1 December 2016 14:47:28 UTC+2, Dima Pasechnik wrote:
>>
>> did you try "make doc-clean" and then rebuilding the docs?
>>
>> On Thursday, December 1, 2016 at 11:58:12 AM UTC, Peleg Michaeli wrote:
>&g
Yes.
On Thursday, 1 December 2016 14:47:28 UTC+2, Dima Pasechnik wrote:
>
> did you try "make doc-clean" and then rebuilding the docs?
>
> On Thursday, December 1, 2016 at 11:58:12 AM UTC, Peleg Michaeli wrote:
>>
>> I have a method, and in the docsrting o
I have a method, and in the docsrting of this method I have references. I
then want to alias the method. Something like this:
class Class(object):
def method(self):
r"""
REFERENCES::
.. [ABC123] A, B and C in 123, 123.
"""
alia
Dear list members,
I was wondering what really makes the difference between the graph
generators in `basic.py` and those in `families.py`.
For one concrete example, I was wondering why `LollipopGraph` appears in
`basic.py` and `BarbellGraph` appears in `families.py`. These two graphs
are very
27 matches
Mail list logo
