Codecov Report

Merging #1333 (ffd3839) into master (2208cc8) will increase coverage by 0.09%.
The diff coverage is 30.58%.

@@            Coverage Diff             @@
##           master    #1333       /-   ##
==========================================
  Coverage   16.09%   16.18%    0.09%     
==========================================
  Files        3739     3739              
  Lines      363643   363741       98     
==========================================
  Hits        58518    58883      365     
  Misses     305125   304858     -267     

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2208cc8...ffd3839. Read the comment docs.

What's wrong with using the new Pythonic .value property as opposed to the getter method?

It's used inconsistently. Some code in direct uses the value property, some code uses the getter method. I personally prefer the getter method, since it doesn't imply that the "value" property can be assigned. I wouldn't be against an inverse change either, however (changing all getter method accesses to the value property).

I see no advantage of using .getValue() over .value. The latter is faster, less visually cluttered, and naming convention agnostic. I reckon we will eventually deprecate the former in favour of the latter, so I would suggest the inverse change.

Not sure what you mean by "doesn't imply that it can be assigned". It doesn't imply such a thing (read-only properties are common), but it can be assigned, if you wanted to.