delta/python-packages/numpy.git/numpy/_globals.py, branch v1.20.0 github.com: numpy/numpy.git MAINT: Remove implicit inheritance from object class (#15236) 2020-01-05T05:53:30+00:00 Jon Dufresne jon.dufresne@gmail.com 2020-01-05T05:53:30+00:00 c31cc36a8a814ed4844a2a553454185601914a5a Inheriting from object was necessary for Python 2 compatibility to use new-style classes. In Python 3, this is unnecessary as there are no old-style classes. Dropping the object is more idiomatic Python. 
Inheriting from object was necessary for Python 2 compatibility to use
new-style classes. In Python 3, this is unnecessary as there are no
old-style classes.

Dropping the object is more idiomatic Python.
 MAINT: Remove unnecessary 'from __future__ import ...' statements 2020-01-03T15:48:11+00:00 Jon Dufresne jon.dufresne@gmail.com 2019-08-27T11:36:38+00:00 ed1e9659f103260a32536b4a7615393e3b1173dc As numpy is Python 3 only, these import statements are now unnecessary and don't alter runtime behavior. 
As numpy is Python 3 only, these import statements are now unnecessary
and don't alter runtime behavior.
ENH: set correct __module__ for objects in numpy's public API 2018-11-14T04:24:31+00:00 Stephan Hoyer shoyer@google.com 2018-11-13T17:38:07+00:00 4d24bbda32d133d51940b0691bd9b428d4198eaa Fixes GH-12271 Tests verify that everything in ``dir(numpy)`` either has ``__module__`` set to ``'numpy'``, or appears in an explicit whitelist of undocumented functions and exported bulitins. These should eventually be documented or removed. I also identified a handful of functions for which I had accidentally not setup dispatch for with ``__array_function__`` before, because they were listed under "ndarray methods" in ``_add_newdocs.py``. I guess that should be a lesson in trusting code comments :). 
Fixes GH-12271

Tests verify that everything in ``dir(numpy)`` either has ``__module__`` set to
``'numpy'``, or appears in an explicit whitelist of undocumented functions and
exported bulitins. These should eventually be documented or removed.

I also identified a handful of functions for which I had accidentally not setup
dispatch for with ``__array_function__`` before, because they were listed under
"ndarray methods" in ``_add_newdocs.py``. I guess that should be a lesson in
trusting code comments :).
ENH: Add a repr to np._NoValue 2018-02-04T04:44:55+00:00 Eric Wieser wieser.eric@gmail.com 2018-02-03T20:04:46+00:00 1271e17ea6ca8abe12f7dd045ac0af8674f594d4 This change _NoValue from a class to an instance, which is more inline with the builtin None. Fixes gh-8991, closes gh-9592 
This change _NoValue from a class to an instance, which is more inline with the builtin None.

Fixes gh-8991, closes gh-9592
MAINT: Use new-style classes on 2.7 2017-07-24T16:00:10+00:00 Eric Wieser wieser.eric@gmail.com 2017-07-24T16:00:10+00:00 7748f26fdbc44cf6d06c270f0a166d797b574744 Deliberately avoids tests, to prevent introducing a failure on old-style classes later. 
Deliberately avoids tests, to prevent introducing a failure on old-style classes later.
BUG: Make sure numpy globals keep identity after reload. 2016-08-16T19:12:32+00:00 Charles Harris charlesr.harris@gmail.com 2016-07-20T17:09:36+00:00 0ade4c43f052247a2d12a2c49d3c846e6c429fa9 Reloading currently causes problems because global classes defined in numpy/__init__.py change their identity (a is b) after reload. The solution taken here is to move those classes to a new non-reloadable module numpy/_globals and import them into numpy from there. Classes moved are ModuleDeprecationWarning, VisibleDeprecationWarning, and _NoValue. Closes #7844. 
Reloading currently causes problems because global classes defined in
numpy/__init__.py change their identity (a is b) after reload. The
solution taken here is to move those classes to a new non-reloadable
module numpy/_globals and import them into numpy from there.

Classes moved are ModuleDeprecationWarning, VisibleDeprecationWarning,
and _NoValue.

Closes #7844.