Re: [Numpy-discussion] Roadmap proposal, v3

2018-07-25 Thread Ralf Gommers
On Thu, Jul 26, 2018 at 12:41 AM, Chris Barker - NOAA Federal < chris.bar...@noaa.gov> wrote: > > Obviously the string dtype proposal in the roadmap is only a sketch at > this point :). > > > > I do think that options listed currently (encoded strings with > fixed-width storage and variable length

Re: [Numpy-discussion] Roadmap proposal, v3

2018-07-25 Thread Chris Barker - NOAA Federal
> Obviously the string dtype proposal in the roadmap is only a sketch at this > point :). > > I do think that options listed currently (encoded strings with fixed-width > storage and variable length strings) cover the breadth of proposals from last > time. We may not want to implement all of the

Re: [Numpy-discussion] Roadmap proposal, v3

2018-07-25 Thread Stephan Hoyer
On Wed, Jul 25, 2018 at 4:02 PM Stefan van der Walt wrote: > Hi Chris, > > On Wed, 25 Jul 2018 08:13:26 -0700, Chris Barker - NOAA Federal wrote: > > For example, I am very wary of putting a non-fixed width encoding (e.g. > > Utf-8) in a fixed width field. > > > > But this PR is not the place to

Re: [Numpy-discussion] Roadmap proposal, v3

2018-07-25 Thread Stefan van der Walt
Hi Chris, On Wed, 25 Jul 2018 08:13:26 -0700, Chris Barker - NOAA Federal wrote: > For example, I am very wary of putting a non-fixed width encoding (e.g. > Utf-8) in a fixed width field. > > But this PR is not the place to discuss that. Since you've followed that discussion closely, can you pus

Re: [Numpy-discussion] update to numpy-1.5.0 gives new warnings from scipy

2018-07-25 Thread Sebastian Berg
On Wed, 2018-07-25 at 07:44 -0400, Neal Becker wrote: > After update to numpy-1.5.0, I'm getting warnings from scipy. > These probably come from my code using convolve. Does scipy need > updating? > Probably yes, I am a bit surprised we did not notice it before if it is in scipy (or maybe scipy

Re: [Numpy-discussion] Roadmap proposal, v3

2018-07-25 Thread Chris Barker - NOAA Federal
Great work, thanks! I see this: “- Fixed width encoded strings (utf8, latin1, ...)” And a bit of discussion in the PR. But I think there are key questions to be addressed in handling strings in numpy. I know we’ve had a lot of discussion about it on this list over the years — but is there a p

Re: [Numpy-discussion] update to numpy-1.5.0 gives new warnings from scipy

2018-07-25 Thread Ralf Gommers
On Wed, Jul 25, 2018 at 11:44 AM, Neal Becker wrote: > After update to numpy-1.5.0, I'm getting warnings from scipy. > These probably come from my code using convolve. Does scipy need updating? > Should already be fixed in scipy master. Cheers, Ralf > /home/nbecker/.local/lib/python3.6/site

[Numpy-discussion] update to numpy-1.5.0 gives new warnings from scipy

2018-07-25 Thread Neal Becker
After update to numpy-1.5.0, I'm getting warnings from scipy. These probably come from my code using convolve. Does scipy need updating? /home/nbecker/.local/lib/python3.6/site-packages/scipy/fftpack/basic.py:160: FutureWarning: Using a non-tuple sequence for multidimensional indexing is deprecat