On 15/12/16 08:16, Jori Mäntysalo wrote:
On Wed, 14 Dec 2016, Peleg Michaeli wrote:
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`).
Yes, there are. And I think they should be mostly deprecated
On Wed, 14 Dec 2016, Peleg Michaeli wrote:
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`).
Yes, there are. And I think they should be mostly deprecated and later
deleted. /Except something li
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 dunno. Aliases are a source of ambiguity and confusion -- my advice
> is to pick one or the other and stick with it.
>
+1
--
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, se
On 2016-12-07, Peleg Michaeli wrote:
> 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):
> r"""
> ...
> """
>
Hey Peleg,
Here is what I think is going on, the @doc_index is modifying the method
degeneracy, i.e., it creates a new method with the same name of
"degeneracy" and has a link back to the actual method. Then the new
degeneracy also gets assigned to the name linkage. Now when the
documentatio
On Fri, Oct 09, 2009 at 11:36:00AM -0700, Nathann Cohen wrote:
>
> hmmm In everything I read, there are just mentions of out-
> neighbors and in-neighbors. I can give you a hundred references using
> these names,
Yup.
> and I would be much more alarmed to give you one reference using
> pre
hmmm In everything I read, there are just mentions of out-
neighbors and in-neighbors. I can give you a hundred references using
these names, and I would be much more alarmed to give you one
reference using predecessors and successors...
Especially when for edges, you can type out and in to k
On Oct 9, 2009, at 7:11 AM, Nicolas M. Thiery wrote:
> On Thu, Oct 08, 2009 at 07:03:29PM -0700, Tom Boothby wrote:
>> +1 to deprecation
>>
>> On Thu, Oct 8, 2009 at 5:43 PM, Jason Grout > s...@creativetrax.com> wrote:
>>>
>>> Nathann Cohen wrote:
Hello everybody !!!
Following
On Thu, Oct 08, 2009 at 07:03:29PM -0700, Tom Boothby wrote:
> +1 to deprecation
>
> On Thu, Oct 8, 2009 at 5:43 PM, Jason Grout
> wrote:
> >
> > Nathann Cohen wrote:
> >> Hello everybody !!!
> >>
> >> Following
> >> http://groups.google.com/group/sage-devel/browse_thread/thread/bfeb9b1828a0435
+1 to deprecation
On Thu, Oct 8, 2009 at 5:43 PM, Jason Grout wrote:
>
> Nathann Cohen wrote:
>> Hello everybody !!!
>>
>> Following
>> http://groups.google.com/group/sage-devel/browse_thread/thread/bfeb9b1828a04350/10681dbb1f189b2f,
>> I created a patch to change predecessors/successors to neig
Nathann Cohen wrote:
> Hello everybody !!!
>
> Following
> http://groups.google.com/group/sage-devel/browse_thread/thread/bfeb9b1828a04350/10681dbb1f189b2f,
>
> I created a patch to change predecessors/successors to neighbors_in and
> neighbors_out.
>
> It is available there : http://trac.sa
12 matches
Mail list logo
