#16137: lazy_list from various input data
-------------------------------------+-------------------------------------
       Reporter:  MatthieuDien       |        Owner:
           Type:  enhancement        |       Status:  needs_review
       Priority:  major              |    Milestone:  sage-7.0
      Component:  misc               |   Resolution:
       Keywords:  LazyPowerSeries,   |    Merged in:
  lazy_list, days57                  |    Reviewers:
        Authors:  Matthieu Dien,     |  Work issues:
  Vincent Delecroix                  |       Commit:
Report Upstream:  N/A                |  72a212c34c0f2a172b9d7ac95d11f24d254a86c3
         Branch:  u/dkrenn/16137     |     Stopgaps:
   Dependencies:                     |
-------------------------------------+-------------------------------------
Changes (by dkrenn):

 * commit:  85d99c03e0f03bfa23950cc807f28a467259fbc6 =>
     72a212c34c0f2a172b9d7ac95d11f24d254a86c3


Comment:

 Replying to [comment:90 vdelecroix]:
 > > 0/1 vs. !False/True: isn't there a `bint` or something like that?), in
 particular, since update_cache_up_to is public. If I would change them...
 >
 > Nope nope. It can be `-1` if a Python error occurrs (but you will not
 see it). We can not use `bint` here.

 Ok, thank you for the clearification.
 ----
 New commits:
 
||[http://git.sagemath.org/sage.git/commit/?id=72a212c34c0f2a172b9d7ac95d11f24d254a86c3
 72a212c]||{{{Trac 16137 review: fix ReST and remove unnecessary iter}}}||

--
Ticket URL: <http://trac.sagemath.org/ticket/16137#comment:95>
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to