On Thu, Feb 8, 2018 at 11:00 PM Eric Wieser
wrote:
> Presumably you would extend that to all (str, np.number), or even (str,
> np.generic_)?
>
Yes, I'm currently doing (np.character, np.number) and (np.character,
np.bool_). But only in direct consultation with the diagram of NumPy's type
hierarch
Presumably you would extend that to all (str, np.number), or even (str,
np.generic_)?
I suppose there’s the argument that with python-3-only support around the
corner, even (str, bytes) should go to object.
Right now, promote_types gives examples in the docs of int/string
conversions, so changing
This is one of my oldest NumPy pain-points:
>>> np.array([1, 2, 'three'])
array(['1', '2', 'three'],
dtype='https://github.com/pydata/xarray/pull/1847), but mostly just
hides bugs until later. It's certainly very un-Pythonic.
The sane promotion rule would be `np.promote_types(str, float) ->
SciPy 2018, the 17th annual Scientific Computing with Python conference,
will be held July 9-15, 2018 in Austin, Texas. The annual SciPyConference
brings together over 700 participants from industry, academia, and
government to showcase their latest projects, learn from skilled users and
developers
On Thu, Feb 8, 2018 at 11:32 AM, Peter Cock
wrote:
> On Thu, Feb 8, 2018 at 11:22 AM, Ralf Gommers
> wrote:
> > On Wed, Feb 7, 2018 at 11:29 PM, Stefan van der Walt <
> stef...@berkeley.edu>
> > wrote:
> >>
> >> For scikit-image, we've started a policy of pushing minor edits
> >> (spelling corre
On Thu, Feb 8, 2018 at 11:22 AM, Ralf Gommers wrote:
> On Wed, Feb 7, 2018 at 11:29 PM, Stefan van der Walt
> wrote:
>>
>> For scikit-image, we've started a policy of pushing minor edits
>> (spelling corrections, sentence restructuring, etc.) directly to the PR
>> branch, instead of flagging thos
On Wed, Feb 7, 2018 at 11:29 PM, Stefan van der Walt
wrote:
> On Wed, 07 Feb 2018 14:26:37 -0700, Charles R Harris wrote:
> > I was thinking about things to do to simplify the NumPy development
> > process. One thing that came to mind was our use of prefixes on commits,
> > BUG, TST, etc. Those p
On Wed, Feb 7, 2018 at 11:04 PM, Andrew Nelson wrote:
> Other factors hindering new contributors:
>
> 1) Being unfamiliar with git. e.g. knowing that you have to fork numpy
> first, then clone from your fork, then create a feature branch. That's just
> the """straightforward bit""". It's hell the
