Zachary Pincus wrote:

Hello all,

I just recently updated to the SVN version of numpy to test my code against it, and found that a small change made to numpy.get_printoptions (it now returns a dictionary instead of a list) breaks my code.

Here's the changeset: http://projects.scipy.org/scipy/numpy/changeset/3877

I'm not really looking forward to needing to detect numpy versions just so I can do the right thing with get_printoptions, but I do agree that the new version of the function is more sensible. My question is if there's any particular policy about backwards- incompatible python api changes, or if I need to be aware of their possibility at every point release. (Either is fine -- I'm happy for numpy to be better at the cost of incompatibility, but I'd like to know if changes like these are the rule or exception.)

At this point, changes like you experienced should be the exception. But, occasionally they will happen. We really try to document them when they occur but this relies on those of us who make the changes making adequate note about them. When the version jumps to 1.1, then there may be more incompatibilities but they should be documented. Thanks for the note and the reminder. -Travis