Done. Patch is ready for review at
http://trac.sagemath.org/sage_trac/ticket/12806
Cheers,
J
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at htt
On 6/14/12 7:40 AM, Javier López Peña wrote:
On Thursday, June 14, 2012 3:39:23 PM UTC+1, Javier López Peña wrote:
Yes, that is the case. The (weighted) clustering coefficient
algorithm (with weighted *edges*)
computes some auxiliary *vertex* weights. The old method used to
retur
On Thursday, June 14, 2012 3:39:23 PM UTC+1, Javier López Peña wrote:
>
> Yes, that is the case. The (weighted) clustering coefficient algorithm
> (with weighted *edges*)
> computes some auxiliary *vertex* weights. The old method used to return
> all of it, the new one
> just returns the cluste
On Thursday, June 14, 2012 3:27:41 PM UTC+1, jason wrote:
>
> So, to be clear, the new networkx function does not give you as much
> information as the old one?
Yes, that is the case. The (weighted) clustering coefficient algorithm
(with weighted *edges*)
computes some auxiliary *vertex* wei
On 6/14/12 7:20 AM, Javier López Peña wrote:
I don't think this should be a problem, but current policy is to
first deprecate it for a while (usually I've heard one year, see
also #13109 for something that will hopefully work in the
future). Presumably you can chan
>
> I don't think this should be a problem, but current policy is to first
>> deprecate it for a while (usually I've heard one year, see also #13109 for
>> something that will hopefully work in the future). Presumably you can
>> change the backend but still return the weights for now, and make
On Thursday, June 14, 2012 7:19:01 AM UTC-4, Javier López Peña wrote:
>
> Hi all,
>
> I am working on the failing doctest to upgrade our almost 2 year old
> NetworkX 1.2 to NetworkX 1.6 (see #12806, [1]) I have sorted out the
> doctest failures in graph.py and digraph.py; in order to solve the
