#16073: Python 3 preparation: The semantic of map() function is changed
-------------------------+-------------------------------------------------
       Reporter:         |        Owner:
  wluebbe                |       Status:  needs_review
           Type:         |    Milestone:  sage-6.4
  enhancement            |   Resolution:
       Priority:  major  |    Merged in:
      Component:         |    Reviewers:
  distribution           |  Work issues:
       Keywords:         |       Commit:
  python3                |  99e57e20ca0f39d11c00a263f82a9de7d4f836ae
        Authors:         |     Stopgaps:
  Wilfried Luebbe        |
Report Upstream:  N/A    |
         Branch:         |
  public/16073           |
   Dependencies:         |
-------------------------+-------------------------------------------------

Comment (by aapitzsch):

 Darij thanks. I hopefully made all the changes you suggested.

 Replying to [comment:18 darij]:
 > Here is the thing that worries me the most: There are tools for
 automatic translation of python2 into 3. I am not sure if we should, or
 are going to, release them on the Sage library; but if we are, I would
 rather not do any manual work unless we can make sure that it will not
 interfere with the automated changes. I have a hunches that a well-written
 bot could do better than some of the changes in this patch (for instance,
 it should be a rule that `all(map(...))` can stay as it is rather than
 being replaced by `all(list(map(...)))`), thus leading to better speed,
 whereas with the changes already done it would not simplify them back to
 what they should be. This does not speak against edits such as replacing
 `list` variables by `list_` and likewise, which are the right thing to do
 either way. But I would be wary of making changes that possibly complicate
 the situation without knowing that it will become untangled when the time
 comes to actually switch to python 3.

 These tools don't work well in all cases and usually one can disable
 special fixes. So manual work won't interfere with automated changes.

 The target of these changes is to simplify the switch to python 3 without
 complicating the situation. :)

--
Ticket URL: <http://trac.sagemath.org/ticket/16073#comment:20>
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 http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to