summaryrefslogtreecommitdiff
path: root/doc/neps
diff options
context:
space:
mode:
authorStefan van der Walt <stefanv@berkeley.edu>2018-07-25 23:30:39 -0700
committerStefan van der Walt <stefanv@berkeley.edu>2018-07-25 23:30:39 -0700
commita4e6f5a12db146221975a2f3d1574434d2df3bf3 (patch)
tree6986b0a3bfe59c98cf529101b0a262abb07633a8 /doc/neps
parent530a4ae11a19615626fe9ca52414ec54c9f8ab47 (diff)
downloadnumpy-a4e6f5a12db146221975a2f3d1574434d2df3bf3.tar.gz
String encoding: increase uncertainty about correct implementation (as per https://mail.python.org/pipermail/numpy-discussion/2018-July/078472.html)
Diffstat (limited to 'doc/neps')
-rw-r--r--doc/neps/roadmap.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/neps/roadmap.rst b/doc/neps/roadmap.rst
index 1cd522463..6aa9b4545 100644
--- a/doc/neps/roadmap.rst
+++ b/doc/neps/roadmap.rst
@@ -31,7 +31,7 @@ Better dtypes
- More consistent support for dtype metadata
- Support for writing a dtype in Python
- New string dtype(s):
- - Encoded strings with fixed-width storage (utf8, latin1, ...)
+ - Encoded strings with fixed-width storage (utf8, latin1, ...) and/or
- Variable length strings (could share implementation with dtype=object, but are explicitly type-checked)
- One of these should probably be the default for text data. The current behavior on Python 3 is neither efficient nor user friendly.
- `np.int` should not be platform dependent