#9925: Doctest error in sage/graphs/graph.py
-----------------------------+----------------------------------------------
 Reporter:  mpatel           |         Owner:  mvngu            
     Type:  defect           |        Status:  closed           
 Priority:  major            |     Milestone:  sage-4.6         
Component:  doctest          |    Resolution:  fixed            
 Keywords:                   |        Author:  Nathann Cohen    
 Upstream:  N/A              |      Reviewer:  Dmitrii Pasechnik
   Merged:  sage-4.6.alpha2  |   Work_issues:                   
-----------------------------+----------------------------------------------

Comment(by ncohen):

 Well, as you had taken the time to write this testing function, I tested
 it against the patches (with n = 10 000, as I was working on a sheet of
 paper at the same time and did not mind forgetting it for several minutes
 `:-D`) :

 With #9422 applied :
 {{{
 #!python
 sage: runner(10000)
 0
 }}}

 With no patch applied, but with
 {{{
 #!python
 g = graphs.RandomBipartite(10, 10, .5)
 }}}
 replaced by
 {{{
 #!python
 g = Graph(graphs.RandomBipartite(10, 10, .5))
 }}}

 in your code (which is exactly what the docstring in #10067 does) :

 {{{
 #!python
 sage: runner(10000)
 0
 }}}

 Be sure that this is not just a statistical proof : #9422 "disconnects"
 the call to the ``is_subgraph`` command, so there is really no path left
 leading to this exception from BipartiteGraph !

 Nathann

 P.S. : Thank you for this ``#!python`` trick ! Very nice `;-)`

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9925#comment:29>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to