[NumPy-Tickets] [NumPy] #2061: difference between behavior of assignment division and future division not documented

[NumPy Trac]

#2061: difference between behavior of assignment division and future division not
documented
----------------------------+-----------------------------------------------
  Reporter:  AlanFrankel    |       Owner:  pv                           
      Type:  defect         |      Status:  reopened                     
  Priority:  normal         |   Milestone:  Unscheduled                  
 Component:  Documentation  |     Version:  1.6.1                        
Resolution:                 |    Keywords:  assignment division operators
----------------------------+-----------------------------------------------
Changes (by AlanFrankel):

 * cc: alanf333@… (added)
  * status:  closed => reopened
  * resolution:  invalid =>


Comment:

 In response to mwiebe: Would the behavior (generation of an error) differ
 depending on whether the division operator had been imported from future?

 In response to rgommers: The red box is not where I expected it, is not
 very prominent on the page, and does not seem particularly relevant to the
 issue at hand at first glance. Nowhere on that page do the strings "+=",
 "*=, "/=" appear, for instance. In fact, when I search for "/=" from the
 NumPy search box, no documentation at all comes up. The connection between
 the double-underscore-decorated methods (e.g., ndarray.__truediv__) and
 the assignment operators is not obvious, and the fact that there are at
 least two issues at play (type coercion and truediv/div alternation) only
 makes the situation more confusing, especially in the absence of
 explanation. I won't have the time to come back to this immediately, but I
 am reopening it because I think the documentation in this area should be
 revisited.

-- 
Ticket URL: <http://projects.scipy.org/numpy/ticket/2061#comment:3>
NumPy <http://projects.scipy.org/numpy>
My example project