summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorSebastian Berg <sebastian@sipsolutions.net>2021-04-19 15:19:24 -0500
committerSebastian Berg <sebastian@sipsolutions.net>2021-05-12 15:33:34 -0700
commit834b1184c1f609a4e9ba06c55ea64ba882e4cdc1 (patch)
treed7bcb87952969fabddffe2a7e445f13f44b2ae34 /doc
parentaaaa9753277ff9d387beecaf0f43519eacdea4eb (diff)
downloadnumpy-834b1184c1f609a4e9ba06c55ea64ba882e4cdc1.tar.gz
MAINT: Remove `NPY_USE_NEW_CASTINGIMPL`
This doesn't serve any purpose anymore. The new code is now always used. (In very few cases this may lead to small slowdowns, this should only matter in ufuncs where it doesn't seem to matter enough to worry about it.)
Diffstat (limited to 'doc')
-rw-r--r--doc/source/reference/global_state.rst14
1 files changed, 0 insertions, 14 deletions
diff --git a/doc/source/reference/global_state.rst b/doc/source/reference/global_state.rst
index b59467210..f18481235 100644
--- a/doc/source/reference/global_state.rst
+++ b/doc/source/reference/global_state.rst
@@ -84,17 +84,3 @@ contiguous in memory.
Most users will have no reason to change these; for details
see the :ref:`memory layout <memory-layout>` documentation.
-Using the new casting implementation
-------------------------------------
-
-Within NumPy 1.20 it is possible to enable the new experimental casting
-implementation for testing purposes. To do this set::
-
- NPY_USE_NEW_CASTINGIMPL=1
-
-Setting the flag is only useful to aid with NumPy developement to ensure the
-new version is bug free and should be avoided for production code.
-It is a helpful test for projects that either create custom datatypes or
-use for example complicated structured dtypes. The flag is expected to be
-removed in 1.21 with the new version being always in use.
-