On Sun, 2021-03-07 at 09:34 +, Kevin Sheppard wrote:
> I think that and string functions that are exposed from an ndarray
> would
> have to be guaranteed to work in-place. Requiring casting to objects
> to use
> the methods feels more like syntactic sugar than an essential case. I
> think
> mos
I think that and string functions that are exposed from an ndarray would
have to be guaranteed to work in-place. Requiring casting to objects to use
the methods feels more like syntactic sugar than an essential case. I think
most of the ones mentioned are low performance and can't take advantage of
On Sat, Mar 6, 2021 at 12:57 PM dan_patterson
wrote:
> The are in np.char
>
> mystr = np.array(["test first", "test second", "test third"])
>
> np.char.title(mystr)
> array(['Test First', 'Test Second', 'Test Third'], dtype='
I mentioned those in my email, but they are far less convenient to us
The are in np.char
mystr = np.array(["test first", "test second", "test third"])
np.char.title(mystr)
array(['Test First', 'Test Second', 'Test Third'], dtype='http://numpy-discussion.10968.n7.nabble.com/
___
NumPy-Discussion mailing list
NumPy-Discuss
Currently. working with strings in numpy is not very convenient. You have
to use a separate set of functions in a separate namespace, and those
functions are relatively limited and poorly-documented.
A solution several other projects, including pandas [0] and xarray [1],
have found are string acce
