From balducci at units.it  Fri Mar  1 05:23:23 2019
From: balducci at units.it (balducci at units.it)
Date: Fri, 01 Mar 2019 11:23:23 +0100
Subject: [Numpy-discussion] python 3.8: heads up: numpy/ma/core.py causes
 warning that breaks numpy detection in boost build
Message-ID: <9789.1551435827@dschgrazlin2.units.it>

hello

just a notice to help preventing future problems... 


python-3.8.0 (alpha) emits the following warning on numpy/ma/core.py
(verified up to official 1.16.2):

    ----8<----
    /usr/python3/site_python3/lib64/numpy.egg/numpy/ma/core.py:4466: SyntaxWarning: "is" with a literal. Did you mean "=="?
      if self.shape is ():
    /usr/python3/site_python3/lib64/numpy.egg/numpy/ma/core.py:4466: SyntaxWarning: "is" with a literal. Did you mean "=="?
      if self.shape is ():
    /usr/python3/site_python3/lib64/numpy.egg/numpy/core/include
    ---->8----


In turn, this breaks boost's numpy detection, which is done with:

----8<----
notice: [python-cfg] running command '/usr/python3/bin/python -c "import sys; sys.stderr = sys.stdout; import numpy; print(numpy.get_include())"'
---->8----

and thus produces an unusable include path (containing the warning
message from python)

The following:

    ----8<----
    *** numpy/ma/core.py.PYTHON_3_8_COMPAT	Wed Feb 27 12:45:06 2019
    --- numpy/ma/core.py	Wed Feb 27 12:45:06 2019
    ***************
    *** 4463,4469 ****
              if m is nomask:
                  # compare to _count_reduce_items in _methods.py

    !             if self.shape is ():
                      if axis not in (None, 0):
                          raise np.AxisError(axis=axis, ndim=self.ndim)
                      return 1
    --- 4463,4469 ----
              if m is nomask:
                  # compare to _count_reduce_items in _methods.py

    !             if self.shape == ():
                      if axis not in (None, 0):
                          raise np.AxisError(axis=axis, ndim=self.ndim)
                      return 1
    ---->8----

fixes everything for me

thanks
ciao
-g


From deak.andris at gmail.com  Fri Mar  1 05:46:55 2019
From: deak.andris at gmail.com (Andras Deak)
Date: Fri, 1 Mar 2019 11:46:55 +0100
Subject: [Numpy-discussion] python 3.8: heads up: numpy/ma/core.py
 causes warning that breaks numpy detection in boost build
In-Reply-To: <9789.1551435827@dschgrazlin2.units.it>
References: <9789.1551435827@dschgrazlin2.units.it>
Message-ID: <CAMEWA4MfCTE920UbU0RBkg5Xaz+YWNWo_yqRzJRNe=neegYwpw@mail.gmail.com>

On Fri, Mar 1, 2019 at 11:24 AM <balducci at units.it> wrote:
> python-3.8.0 (alpha) emits the following warning on numpy/ma/core.py
> (verified up to official 1.16.2):
>
>     ----8<----
>     /usr/python3/site_python3/lib64/numpy.egg/numpy/ma/core.py:4466: SyntaxWarning: "is" with a literal. Did you mean "=="?
>       if self.shape is ():
>     /usr/python3/site_python3/lib64/numpy.egg/numpy/ma/core.py:4466: SyntaxWarning: "is" with a literal. Did you mean "=="?
>       if self.shape is ():
>     /usr/python3/site_python3/lib64/numpy.egg/numpy/core/include
>     ---->8----
Hi,

I believe the warning is really helpful, testing for an empty tuple
with `is` probably only works because of a CPython implementation
detail (namely that the empty tuple is interned by the interpreter).
In other words, this seems like a bug which is fixed by using ==
instead.
Regards,

Andr?s


>
>
> In turn, this breaks boost's numpy detection, which is done with:
>
> ----8<----
> notice: [python-cfg] running command '/usr/python3/bin/python -c "import sys; sys.stderr = sys.stdout; import numpy; print(numpy.get_include())"'
> ---->8----
>
> and thus produces an unusable include path (containing the warning
> message from python)
>
> The following:
>
>     ----8<----
>     *** numpy/ma/core.py.PYTHON_3_8_COMPAT      Wed Feb 27 12:45:06 2019
>     --- numpy/ma/core.py        Wed Feb 27 12:45:06 2019
>     ***************
>     *** 4463,4469 ****
>               if m is nomask:
>                   # compare to _count_reduce_items in _methods.py
>
>     !             if self.shape is ():
>                       if axis not in (None, 0):
>                           raise np.AxisError(axis=axis, ndim=self.ndim)
>                       return 1
>     --- 4463,4469 ----
>               if m is nomask:
>                   # compare to _count_reduce_items in _methods.py
>
>     !             if self.shape == ():
>                       if axis not in (None, 0):
>                           raise np.AxisError(axis=axis, ndim=self.ndim)
>                       return 1
>     ---->8----
>
> fixes everything for me
>
> thanks
> ciao
> -g
>
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion

From tyler.je.reddy at gmail.com  Wed Mar  6 12:36:58 2019
From: tyler.je.reddy at gmail.com (Tyler Reddy)
Date: Wed, 6 Mar 2019 09:36:58 -0800
Subject: [Numpy-discussion] Weekly BIDS / community meeting
Message-ID: <CAHPuU_aEuSXOpGv0Us5Gvpv-+SeM056jvhNyPkNC0+p1xK1bCw@mail.gmail.com>

Hi,

Just a reminder of the weekly meeting in a few hours today, March 6, at 12
pm Pacific time.

The document with a space for community suggested topics & video conference
link is available here: https://hackmd.io/4JBjLkbCS02nELfckJWB5Q?view
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190306/e2ed5951/attachment.html>

From fbastien at nvidia.com  Wed Mar  6 13:04:06 2019
From: fbastien at nvidia.com (Frederic Bastien)
Date: Wed, 6 Mar 2019 18:04:06 +0000
Subject: [Numpy-discussion] NEP-18 comment
Message-ID: <BYAPR12MB3144C39108604BE6E65406E8A8730@BYAPR12MB3144.namprd12.prod.outlook.com>

Hi,

I was told recently about the NEP-18. I like it, but I have a comment.

At first, it is enabled in a release by setting an environment variable.
Then in the following release, it is enabled by default.

Is it possible to allow for the second release to disable it by an environment variable? This would allow to disable it for people that would be inconvenienced by this change.

Who could be negatively impacted by this? Small array operation.

I recall many years ago of much effort to speed up small array, including at least one GSoC. I didn't do timing, but I'm pretty sure the change needed for NEP-19 raise the default overhead for all operation that it impact.
I also recall people in the mailing list asking how to speed up the small array case.
So giving people a way to not pay for that overhead would make sure that for people that care about the small array cases won't pay that extra overhead price. So they won't see a slowdown by updating NumPy.

Probably less than 1% of user will enable the new functionality in the current release as it is not enabled by default. Making it easy to try is great, but doesn't guaranty that it will be tested in all corner cases. So it isn't sure we would heard before the second release about regression this change does.

What do you think about that small changes?

Thanks for the great work on such important library.

Fr?d?ric Bastien

-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190306/092f28e0/attachment.html>

From shoyer at gmail.com  Wed Mar  6 15:41:11 2019
From: shoyer at gmail.com (Stephan Hoyer)
Date: Wed, 6 Mar 2019 12:41:11 -0800
Subject: [Numpy-discussion] NEP-18 comment
In-Reply-To: <BYAPR12MB3144C39108604BE6E65406E8A8730@BYAPR12MB3144.namprd12.prod.outlook.com>
References: <BYAPR12MB3144C39108604BE6E65406E8A8730@BYAPR12MB3144.namprd12.prod.outlook.com>
Message-ID: <CAEQ_Tve2FLNDVF0VAA2TRfUqgYRPVgTN2WT4a46q7d+CjOsyKg@mail.gmail.com>

On Wed, Mar 6, 2019 at 10:10 AM Frederic Bastien <fbastien at nvidia.com>
wrote:

> Hi,
>
>
>
> I was told recently about the NEP-18. I like it, but I have a comment.
>
>
>
> At first, it is enabled in a release by setting an environment variable.
>
> Then in the following release, it is enabled by default.
>
>
>
> Is it possible to allow for the second release to disable it by an
> environment variable? This would allow to disable it for people that would
> be inconvenienced by this change.
>
>
>
> Who could be negatively impacted by this? Small array operation.
>
>
>
> I recall many years ago of much effort to speed up small array, including
> at least one GSoC. I didn?t do timing, but I?m pretty sure the change
> needed for NEP-19 raise the default overhead for all operation that it
> impact.
>
> I also recall people in the mailing list asking how to speed up the small
> array case.
>
> So giving people a way to not pay for that overhead would make sure that
> for people that care about the small array cases won?t pay that extra
> overhead price. So they won?t see a slowdown by updating NumPy.
>
>
>
> Probably less than 1% of user will enable the new functionality in the
> current release as it is not enabled by default. Making it easy to try is
> great, but doesn?t guaranty that it will be tested in all corner cases. So
> it isn?t sure we would heard before the second release about regression
> this change does.
>
>
>
> What do you think about that small changes?
>
>
Hi Frederic,

Thanks for raising these concerns (and thanks for your work on Theano!).

I agree, this seems like an easy and worthwhile change. The NEP-18
implementation has been rewritten in C, so I expect that the typical
overhead will be quite minimal (about 1 us per function call), but I agree
that there may be some important edge cases that we missed.

The only downside I can think of is that libraries using NEP-18 won't be
able to simply rely upon the NumPy version for checking if it's supported
-- they will also have to check an environment variable.

Best,
Stephan


>
>
> Thanks for the great work on such important library.
>
>
>
> Fr?d?ric Bastien
> ------------------------------
> This email message is for the sole use of the intended recipient(s) and
> may contain confidential information.  Any unauthorized review, use,
> disclosure or distribution is prohibited.  If you are not the intended
> recipient, please contact the sender by reply email and destroy all copies
> of the original message.
> ------------------------------
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190306/fdad3a9e/attachment-0001.html>

From fbastien at nvidia.com  Wed Mar  6 15:48:03 2019
From: fbastien at nvidia.com (Frederic Bastien)
Date: Wed, 6 Mar 2019 20:48:03 +0000
Subject: [Numpy-discussion] NEP-18 comment
In-Reply-To: <CAEQ_Tve2FLNDVF0VAA2TRfUqgYRPVgTN2WT4a46q7d+CjOsyKg@mail.gmail.com>
References: <BYAPR12MB3144C39108604BE6E65406E8A8730@BYAPR12MB3144.namprd12.prod.outlook.com>
 <CAEQ_Tve2FLNDVF0VAA2TRfUqgYRPVgTN2WT4a46q7d+CjOsyKg@mail.gmail.com>
Message-ID: <BYAPR12MB3144207F58BEB09BF784D378A8730@BYAPR12MB3144.namprd12.prod.outlook.com>

That is a good point. In the worst case, if some library doesn?t check the env variable what would happen? Crash I suppose? If so, this isn?t too bad.

I think that the script that care about the small array case are mostly disjoint from the one that care about integration with other lib. But I could be wrong on that. I?m too close to machine learning/deep learning to evaluation well that point.

From: NumPy-Discussion <numpy-discussion-bounces+fbastien=nvidia.com at python.org> On Behalf Of Stephan Hoyer
Sent: Wednesday, March 6, 2019 3:41 PM
To: Discussion of Numerical Python <numpy-discussion at python.org>
Subject: Re: [Numpy-discussion] NEP-18 comment

On Wed, Mar 6, 2019 at 10:10 AM Frederic Bastien <fbastien at nvidia.com<mailto:fbastien at nvidia.com>> wrote:
Hi,

I was told recently about the NEP-18. I like it, but I have a comment.

At first, it is enabled in a release by setting an environment variable.
Then in the following release, it is enabled by default.

Is it possible to allow for the second release to disable it by an environment variable? This would allow to disable it for people that would be inconvenienced by this change.

Who could be negatively impacted by this? Small array operation.

I recall many years ago of much effort to speed up small array, including at least one GSoC. I didn?t do timing, but I?m pretty sure the change needed for NEP-19 raise the default overhead for all operation that it impact.
I also recall people in the mailing list asking how to speed up the small array case.
So giving people a way to not pay for that overhead would make sure that for people that care about the small array cases won?t pay that extra overhead price. So they won?t see a slowdown by updating NumPy.

Probably less than 1% of user will enable the new functionality in the current release as it is not enabled by default. Making it easy to try is great, but doesn?t guaranty that it will be tested in all corner cases. So it isn?t sure we would heard before the second release about regression this change does.

What do you think about that small changes?

Hi Frederic,

Thanks for raising these concerns (and thanks for your work on Theano!).

I agree, this seems like an easy and worthwhile change. The NEP-18 implementation has been rewritten in C, so I expect that the typical overhead will be quite minimal (about 1 us per function call), but I agree that there may be some important edge cases that we missed.

The only downside I can think of is that libraries using NEP-18 won't be able to simply rely upon the NumPy version for checking if it's supported -- they will also have to check an environment variable.

Best,
Stephan


Thanks for the great work on such important library.

Fr?d?ric Bastien
________________________________
This email message is for the sole use of the intended recipient(s) and may contain confidential information.  Any unauthorized review, use, disclosure or distribution is prohibited.  If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
________________________________
_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion at python.org<mailto:NumPy-Discussion at python.org>
https://mail.python.org/mailman/listinfo/numpy-discussion
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190306/82319eb9/attachment.html>

From stefanv at berkeley.edu  Wed Mar  6 17:22:14 2019
From: stefanv at berkeley.edu (Stefan van der Walt)
Date: Wed, 6 Mar 2019 14:22:14 -0800
Subject: [Numpy-discussion] NEP-18 comment
In-Reply-To: <CAEQ_Tve2FLNDVF0VAA2TRfUqgYRPVgTN2WT4a46q7d+CjOsyKg@mail.gmail.com>
References: <BYAPR12MB3144C39108604BE6E65406E8A8730@BYAPR12MB3144.namprd12.prod.outlook.com>
 <CAEQ_Tve2FLNDVF0VAA2TRfUqgYRPVgTN2WT4a46q7d+CjOsyKg@mail.gmail.com>
Message-ID: <20190306222214.coz2aa5gub5bbyk2@carbo>

It's great to have your input here, Frederic?thank you!

On Wed, 06 Mar 2019 12:41:11 -0800, Stephan Hoyer wrote:
> I agree, this seems like an easy and worthwhile change. The NEP-18
> implementation has been rewritten in C, so I expect that the typical
> overhead will be quite minimal (about 1 us per function call), but I agree
> that there may be some important edge cases that we missed.

The environment variable made sense when we only wanted to give select
access to try the new feature, but I think it's a slippery slope to
allow it to *disable* functionality that, for everyone else, is default.
Once you start having functionality vary across environments, you are
bound to see strange things happen.  E.g., the same code, run with the
same verison of dask, may or may not work depending on a shell setting?

Best regards,
St?fan

From sebastian at sipsolutions.net  Thu Mar  7 08:58:13 2019
From: sebastian at sipsolutions.net (Sebastian Berg)
Date: Thu, 07 Mar 2019 14:58:13 +0100
Subject: [Numpy-discussion] NEP-18 comment
In-Reply-To: <CAEQ_Tve2FLNDVF0VAA2TRfUqgYRPVgTN2WT4a46q7d+CjOsyKg@mail.gmail.com>
References: <BYAPR12MB3144C39108604BE6E65406E8A8730@BYAPR12MB3144.namprd12.prod.outlook.com>
 <CAEQ_Tve2FLNDVF0VAA2TRfUqgYRPVgTN2WT4a46q7d+CjOsyKg@mail.gmail.com>
Message-ID: <51fe32a7ba634e9433d605a158120d1d69757f2d.camel@sipsolutions.net>

On Wed, 2019-03-06 at 12:41 -0800, Stephan Hoyer wrote:
> On Wed, Mar 6, 2019 at 10:10 AM Frederic Bastien <fbastien at nvidia.com
> > wrote:
> > Hi,
> >  
> > I was told recently about the NEP-18. I like it, but I have a
> > comment.
> >  
> > At first, it is enabled in a release by setting an environment
> > variable.
> > Then in the following release, it is enabled by default.
> >  
> > Is it possible to allow for the second release to disable it by an
> > environment variable? This would allow to disable it for people
> > that would be inconvenienced by this change.
> >  
> > Who could be negatively impacted by this? Small array operation.
> >  
> > I recall many years ago of much effort to speed up small array,
> > including at least one GSoC. I didn?t do timing, but I?m pretty
> > sure the change needed for NEP-19 raise the default overhead for
> > all operation that it impact.
> > I also recall people in the mailing list asking how to speed up the
> > small array case.
> > So giving people a way to not pay for that overhead would make sure
> > that for people that care about the small array cases won?t pay
> > that extra overhead price. So they won?t see a slowdown by updating
> > NumPy.
> >  
> > Probably less than 1% of user will enable the new functionality in
> > the current release as it is not enabled by default. Making it easy
> > to try is great, but doesn?t guaranty that it will be tested in all
> > corner cases. So it isn?t sure we would heard before the second
> > release about regression this change does.
> >  
> > What do you think about that small changes?
> > 
> 
> Hi Frederic,
> 
> Thanks for raising these concerns (and thanks for your work on
> Theano!).
> 
> I agree, this seems like an easy and worthwhile change. The NEP-18
> implementation has been rewritten in C, so I expect that the typical
> overhead will be quite minimal (about 1 us per function call), but I
> agree that there may be some important edge cases that we missed.
> 

If this is really an issue/worthwhile, how much overhead would be left
if you skip the dispatching check and call the original implementation
directly? It seems to me that may be quite a bit less than 1us (but
maybe still too much)?

The reason I ask is that if we can get a large part of the way with a
runtime (instead of import time) switch, such as:

np.enable_array_function_dispatch()  # likely more hidden than that.

than that seems much more useful to me, because dask and friends can
just call it and users do not need to know about it. Otherwise, we add
an optimization which would only be used by a tiny fraction of numpy
users, or it would be used blindly and problems arise when someone
starts using e.g. dask later.
And if we disable dispatching by default, dask would have to print a
confusing "please set this environment variable" message.

- Sebastian



> The only downside I can think of is that libraries using NEP-18 won't
> be able to simply rely upon the NumPy version for checking if it's
> supported -- they will also have to check an environment variable.
> 
> Best,
> Stephan
>  
> >  
> > Thanks for the great work on such important library.
> >  
> > Fr?d?ric Bastien
> > This email message is for the sole use of the intended recipient(s)
> > and may contain confidential information.  Any unauthorized review,
> > use, disclosure or distribution is prohibited.  If you are not the
> > intended recipient, please contact the sender by reply email and
> > destroy all copies of the original message.
> > _______________________________________________
> > NumPy-Discussion mailing list
> > NumPy-Discussion at python.org
> > https://mail.python.org/mailman/listinfo/numpy-discussion
> 
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190307/5445bc76/attachment.sig>

From fbastien at nvidia.com  Thu Mar  7 09:23:10 2019
From: fbastien at nvidia.com (Frederic Bastien)
Date: Thu, 7 Mar 2019 14:23:10 +0000
Subject: [Numpy-discussion] NEP-18 comment
In-Reply-To: <51fe32a7ba634e9433d605a158120d1d69757f2d.camel@sipsolutions.net>
References: <BYAPR12MB3144C39108604BE6E65406E8A8730@BYAPR12MB3144.namprd12.prod.outlook.com>
 <CAEQ_Tve2FLNDVF0VAA2TRfUqgYRPVgTN2WT4a46q7d+CjOsyKg@mail.gmail.com>
 <51fe32a7ba634e9433d605a158120d1d69757f2d.camel@sipsolutions.net>
Message-ID: <BYAPR12MB31443C2E982113E9FFD697DFA84C0@BYAPR12MB3144.namprd12.prod.outlook.com>

I like your idea Sebastian. This way it is enabled only when needed and it is invisible to the user at the same time.

Stefan, does it solve well enough the potential problem you raised?

It still raise the problem that if you import a lib and do not use it, then the small array would slow down. I do not see way around that expect to tell the library dev to call that method not  on import, but when it get used. But this can be tricky to do for some lib I think.

I prefer a slowdown when you try to use advanced feature then a slow down by default and your proposition does that.

Fr?d?ric

-----Original Message-----
From: NumPy-Discussion <numpy-discussion-bounces+fbastien=nvidia.com at python.org> On Behalf Of Sebastian Berg
Sent: Thursday, March 7, 2019 8:58 AM
To: numpy-discussion at python.org
Subject: Re: [Numpy-discussion] NEP-18 comment

On Wed, 2019-03-06 at 12:41 -0800, Stephan Hoyer wrote:
> On Wed, Mar 6, 2019 at 10:10 AM Frederic Bastien <fbastien at nvidia.com
> > wrote:
> > Hi,
> >  
> > I was told recently about the NEP-18. I like it, but I have a 
> > comment.
> >  
> > At first, it is enabled in a release by setting an environment 
> > variable.
> > Then in the following release, it is enabled by default.
> >  
> > Is it possible to allow for the second release to disable it by an 
> > environment variable? This would allow to disable it for people that 
> > would be inconvenienced by this change.
> >  
> > Who could be negatively impacted by this? Small array operation.
> >  
> > I recall many years ago of much effort to speed up small array, 
> > including at least one GSoC. I didn?t do timing, but I?m pretty sure 
> > the change needed for NEP-19 raise the default overhead for all 
> > operation that it impact.
> > I also recall people in the mailing list asking how to speed up the 
> > small array case.
> > So giving people a way to not pay for that overhead would make sure 
> > that for people that care about the small array cases won?t pay that 
> > extra overhead price. So they won?t see a slowdown by updating 
> > NumPy.
> >  
> > Probably less than 1% of user will enable the new functionality in 
> > the current release as it is not enabled by default. Making it easy 
> > to try is great, but doesn?t guaranty that it will be tested in all 
> > corner cases. So it isn?t sure we would heard before the second 
> > release about regression this change does.
> >  
> > What do you think about that small changes?
> > 
> 
> Hi Frederic,
> 
> Thanks for raising these concerns (and thanks for your work on 
> Theano!).
> 
> I agree, this seems like an easy and worthwhile change. The NEP-18 
> implementation has been rewritten in C, so I expect that the typical 
> overhead will be quite minimal (about 1 us per function call), but I 
> agree that there may be some important edge cases that we missed.
> 

If this is really an issue/worthwhile, how much overhead would be left if you skip the dispatching check and call the original implementation directly? It seems to me that may be quite a bit less than 1us (but maybe still too much)?

The reason I ask is that if we can get a large part of the way with a runtime (instead of import time) switch, such as:

np.enable_array_function_dispatch()  # likely more hidden than that.

than that seems much more useful to me, because dask and friends can just call it and users do not need to know about it. Otherwise, we add an optimization which would only be used by a tiny fraction of numpy users, or it would be used blindly and problems arise when someone starts using e.g. dask later.
And if we disable dispatching by default, dask would have to print a confusing "please set this environment variable" message.

- Sebastian



> The only downside I can think of is that libraries using NEP-18 won't 
> be able to simply rely upon the NumPy version for checking if it's 
> supported -- they will also have to check an environment variable.
> 
> Best,
> Stephan
>  
> >  
> > Thanks for the great work on such important library.
> >  
> > Fr?d?ric Bastien
> > This email message is for the sole use of the intended recipient(s) 
> > and may contain confidential information.  Any unauthorized review, 
> > use, disclosure or distribution is prohibited.  If you are not the 
> > intended recipient, please contact the sender by reply email and 
> > destroy all copies of the original message.
> > _______________________________________________
> > NumPy-Discussion mailing list
> > NumPy-Discussion at python.org
> > https://mail.python.org/mailman/listinfo/numpy-discussion
> 
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion

From stefanv at berkeley.edu  Thu Mar  7 12:15:23 2019
From: stefanv at berkeley.edu (Stefan van der Walt)
Date: Thu, 7 Mar 2019 09:15:23 -0800
Subject: [Numpy-discussion] NEP-18 comment
In-Reply-To: <BYAPR12MB31443C2E982113E9FFD697DFA84C0@BYAPR12MB3144.namprd12.prod.outlook.com>
References: <BYAPR12MB3144C39108604BE6E65406E8A8730@BYAPR12MB3144.namprd12.prod.outlook.com>
 <CAEQ_Tve2FLNDVF0VAA2TRfUqgYRPVgTN2WT4a46q7d+CjOsyKg@mail.gmail.com>
 <51fe32a7ba634e9433d605a158120d1d69757f2d.camel@sipsolutions.net>
 <BYAPR12MB31443C2E982113E9FFD697DFA84C0@BYAPR12MB3144.namprd12.prod.outlook.com>
Message-ID: <20190307171523.sle5kznmqhrvvd2u@carbo>

Hi Sebastian, Frederic,

On Thu, 07 Mar 2019 14:23:10 +0000, Frederic Bastien wrote:
> I like your idea Sebastian. This way it is enabled only when needed and it is invisible to the user at the same time.
> 
> Stefan, does it solve well enough the potential problem you raised?

I don't think so.  This means that NumPy suddenly behaves differently
when dask is imported, which again causes the problem mentioned earlier:
that identical NumPy code could behave differently depending on library
versions, imports, and the environment.

That said, I think this is a better solution than an environment
variable.

Anyway, my opinion is just one of many: I'd like to hear what the other
developers think.

Best regards,
St?fan

From fbastien at nvidia.com  Thu Mar  7 13:24:43 2019
From: fbastien at nvidia.com (Frederic Bastien)
Date: Thu, 7 Mar 2019 18:24:43 +0000
Subject: [Numpy-discussion] NEP-18 comment
In-Reply-To: <20190307171523.sle5kznmqhrvvd2u@carbo>
References: <BYAPR12MB3144C39108604BE6E65406E8A8730@BYAPR12MB3144.namprd12.prod.outlook.com>
 <CAEQ_Tve2FLNDVF0VAA2TRfUqgYRPVgTN2WT4a46q7d+CjOsyKg@mail.gmail.com>
 <51fe32a7ba634e9433d605a158120d1d69757f2d.camel@sipsolutions.net>
 <BYAPR12MB31443C2E982113E9FFD697DFA84C0@BYAPR12MB3144.namprd12.prod.outlook.com>
 <20190307171523.sle5kznmqhrvvd2u@carbo>
Message-ID: <BYAPR12MB3144731782D556EB5BD94916A84C0@BYAPR12MB3144.namprd12.prod.outlook.com>

I see speed changes vs behavior changes as different category of changes in my mind.

I understand that now importing library can slow down NumPy for small arrays.
But I have the impression you tell this can also give behavior change.

I do not understand why this could happen. A pure numpy script, that you just import dask or other library without using them, would just cause a slowdown. Not a behavior change.

Behavior change's start to happen only when you start to use the new library.

Did I miss something?

Fr?d?ric

-----Original Message-----
From: NumPy-Discussion <numpy-discussion-bounces+fbastien=nvidia.com at python.org> On Behalf Of Stefan van der Walt
Sent: Thursday, March 7, 2019 12:15 PM
To: Discussion of Numerical Python <numpy-discussion at python.org>
Cc: Matthew Rocklin <mrocklin at gmail.com>
Subject: Re: [Numpy-discussion] NEP-18 comment

Hi Sebastian, Frederic,

On Thu, 07 Mar 2019 14:23:10 +0000, Frederic Bastien wrote:
> I like your idea Sebastian. This way it is enabled only when needed and it is invisible to the user at the same time.
> 
> Stefan, does it solve well enough the potential problem you raised?

I don't think so.  This means that NumPy suddenly behaves differently when dask is imported, which again causes the problem mentioned earlier:
that identical NumPy code could behave differently depending on library versions, imports, and the environment.

That said, I think this is a better solution than an environment variable.

Anyway, my opinion is just one of many: I'd like to hear what the other developers think.

Best regards,
St?fan
_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion at python.org
https://mail.python.org/mailman/listinfo/numpy-discussion
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------

From m.h.vankerkwijk at gmail.com  Thu Mar  7 14:02:17 2019
From: m.h.vankerkwijk at gmail.com (Marten van Kerkwijk)
Date: Thu, 7 Mar 2019 14:02:17 -0500
Subject: [Numpy-discussion] NEP-18 comment
In-Reply-To: <BYAPR12MB3144731782D556EB5BD94916A84C0@BYAPR12MB3144.namprd12.prod.outlook.com>
References: <BYAPR12MB3144C39108604BE6E65406E8A8730@BYAPR12MB3144.namprd12.prod.outlook.com>
 <CAEQ_Tve2FLNDVF0VAA2TRfUqgYRPVgTN2WT4a46q7d+CjOsyKg@mail.gmail.com>
 <51fe32a7ba634e9433d605a158120d1d69757f2d.camel@sipsolutions.net>
 <BYAPR12MB31443C2E982113E9FFD697DFA84C0@BYAPR12MB3144.namprd12.prod.outlook.com>
 <20190307171523.sle5kznmqhrvvd2u@carbo>
 <BYAPR12MB3144731782D556EB5BD94916A84C0@BYAPR12MB3144.namprd12.prod.outlook.com>
Message-ID: <CAJNV+9vb1kjTsnzEcgxRek08HPaK5sEt1T98yHWiDJQNx8dBYA@mail.gmail.com>

Hi Fr?d?ric,

The problem with any environment type variable is that when you disable the
dispatch functionality, all other classes that rely on being able to
override a numpy function stop working as well, i.e., the behaviour of
everything from dask to astropy's Quantity would depend on that setting.

As another alternative, in any call where you *know* that the input is pure
ndarray, you can already call `np.<function>.__wrapped__(...)` to call the
original code. This is *not* guaranteed to remain in place between
versions, but obviously for cases that the speed really matters, one can
use it.

Personally, though, I think it would make most sense to try to ensure the
functions are as fast as possible including the dispatcher check, since
that benefits all. My sense is that for quite a number of numpy functions,
there is lower hanging fruit...

All the best,

Marten

On Thu, Mar 7, 2019 at 1:25 PM Frederic Bastien <fbastien at nvidia.com> wrote:

> I see speed changes vs behavior changes as different category of changes
> in my mind.
>
> I understand that now importing library can slow down NumPy for small
> arrays.
> But I have the impression you tell this can also give behavior change.
>
> I do not understand why this could happen. A pure numpy script, that you
> just import dask or other library without using them, would just cause a
> slowdown. Not a behavior change.
>
> Behavior change's start to happen only when you start to use the new
> library.
>
> Did I miss something?
>
> Fr?d?ric
>
> -----Original Message-----
> From: NumPy-Discussion <numpy-discussion-bounces+fbastien=
> nvidia.com at python.org> On Behalf Of Stefan van der Walt
> Sent: Thursday, March 7, 2019 12:15 PM
> To: Discussion of Numerical Python <numpy-discussion at python.org>
> Cc: Matthew Rocklin <mrocklin at gmail.com>
> Subject: Re: [Numpy-discussion] NEP-18 comment
>
> Hi Sebastian, Frederic,
>
> On Thu, 07 Mar 2019 14:23:10 +0000, Frederic Bastien wrote:
> > I like your idea Sebastian. This way it is enabled only when needed and
> it is invisible to the user at the same time.
> >
> > Stefan, does it solve well enough the potential problem you raised?
>
> I don't think so.  This means that NumPy suddenly behaves differently when
> dask is imported, which again causes the problem mentioned earlier:
> that identical NumPy code could behave differently depending on library
> versions, imports, and the environment.
>
> That said, I think this is a better solution than an environment variable.
>
> Anyway, my opinion is just one of many: I'd like to hear what the other
> developers think.
>
> Best regards,
> St?fan
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
> -----------------------------------------------------------------------------------
> This email message is for the sole use of the intended recipient(s) and
> may contain
> confidential information.  Any unauthorized review, use, disclosure or
> distribution
> is prohibited.  If you are not the intended recipient, please contact the
> sender by
> reply email and destroy all copies of the original message.
>
> -----------------------------------------------------------------------------------
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190307/9725ed1a/attachment-0001.html>

From sebastian at sipsolutions.net  Thu Mar  7 14:18:12 2019
From: sebastian at sipsolutions.net (Sebastian Berg)
Date: Thu, 07 Mar 2019 20:18:12 +0100
Subject: [Numpy-discussion] NEP-18 comment
In-Reply-To: <BYAPR12MB3144731782D556EB5BD94916A84C0@BYAPR12MB3144.namprd12.prod.outlook.com>
References: <BYAPR12MB3144C39108604BE6E65406E8A8730@BYAPR12MB3144.namprd12.prod.outlook.com>
 <CAEQ_Tve2FLNDVF0VAA2TRfUqgYRPVgTN2WT4a46q7d+CjOsyKg@mail.gmail.com>
 <51fe32a7ba634e9433d605a158120d1d69757f2d.camel@sipsolutions.net>
 <BYAPR12MB31443C2E982113E9FFD697DFA84C0@BYAPR12MB3144.namprd12.prod.outlook.com>
 <20190307171523.sle5kznmqhrvvd2u@carbo>
 <BYAPR12MB3144731782D556EB5BD94916A84C0@BYAPR12MB3144.namprd12.prod.outlook.com>
Message-ID: <a7c4b98423713cc5fd33d2ab164d6bbfdeff34af.camel@sipsolutions.net>

On Thu, 2019-03-07 at 18:24 +0000, Frederic Bastien wrote:
> I see speed changes vs behavior changes as different category of
> changes in my mind.
> 
> I understand that now importing library can slow down NumPy for small
> arrays.
> But I have the impression you tell this can also give behavior
> change.
> 
> I do not understand why this could happen. A pure numpy script, that
> you just import dask or other library without using them, would just
> cause a slowdown. Not a behavior change.
> 
> Behavior change's start to happen only when you start to use the new
> library.


Yes, but if a user can switch, downstream projects might change their
behaviour (my thought makes that less likely, but it is still a risk).

The best solution would be to just make things fast enough that we do
not have to worry about it. And I would not rule out that we are
already there.
Things seem a bit hard to time with all the C/Python boundaries
involved, but it seems to me that the actual time spend on the C-side
is reasonably low. The biggest chunk is probably that we have 4
function calls instead of 1:

  1. Public api call
  2. dispatch call (get arguments relevant for dispatching)
  3. Call C-side function implementing the logic
  4. Call the actual function

Improving that much seems like it might get ugly pretty fast. But I am
wondering if dispatching from within C for functions that are currently
defined in C already may be moderately easy (and also the ones with the
largest pay-off).

Best,

Sebastian



> 
> Did I miss something?
> 
> Fr?d?ric
> 
> -----Original Message-----
> From: NumPy-Discussion <
> numpy-discussion-bounces+fbastien=nvidia.com at python.org> On Behalf Of
> Stefan van der Walt
> Sent: Thursday, March 7, 2019 12:15 PM
> To: Discussion of Numerical Python <numpy-discussion at python.org>
> Cc: Matthew Rocklin <mrocklin at gmail.com>
> Subject: Re: [Numpy-discussion] NEP-18 comment
> 
> Hi Sebastian, Frederic,
> 
> On Thu, 07 Mar 2019 14:23:10 +0000, Frederic Bastien wrote:
> > I like your idea Sebastian. This way it is enabled only when needed
> > and it is invisible to the user at the same time.
> > 
> > Stefan, does it solve well enough the potential problem you raised?
> 
> I don't think so.  This means that NumPy suddenly behaves differently
> when dask is imported, which again causes the problem mentioned
> earlier:
> that identical NumPy code could behave differently depending on
> library versions, imports, and the environment.
> 
> That said, I think this is a better solution than an environment
> variable.
> 
> Anyway, my opinion is just one of many: I'd like to hear what the
> other developers think.
> 
> Best regards,
> St?fan
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
> -------------------------------------------------------------------
> ----------------
> This email message is for the sole use of the intended recipient(s)
> and may contain
> confidential information.  Any unauthorized review, use, disclosure
> or distribution
> is prohibited.  If you are not the intended recipient, please contact
> the sender by
> reply email and destroy all copies of the original message.
> -------------------------------------------------------------------
> ----------------
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190307/5583b042/attachment.sig>

From shoyer at gmail.com  Thu Mar  7 14:30:53 2019
From: shoyer at gmail.com (Stephan Hoyer)
Date: Thu, 7 Mar 2019 11:30:53 -0800
Subject: [Numpy-discussion] NEP-18 comment
In-Reply-To: <a7c4b98423713cc5fd33d2ab164d6bbfdeff34af.camel@sipsolutions.net>
References: <BYAPR12MB3144C39108604BE6E65406E8A8730@BYAPR12MB3144.namprd12.prod.outlook.com>
 <CAEQ_Tve2FLNDVF0VAA2TRfUqgYRPVgTN2WT4a46q7d+CjOsyKg@mail.gmail.com>
 <51fe32a7ba634e9433d605a158120d1d69757f2d.camel@sipsolutions.net>
 <BYAPR12MB31443C2E982113E9FFD697DFA84C0@BYAPR12MB3144.namprd12.prod.outlook.com>
 <20190307171523.sle5kznmqhrvvd2u@carbo>
 <BYAPR12MB3144731782D556EB5BD94916A84C0@BYAPR12MB3144.namprd12.prod.outlook.com>
 <a7c4b98423713cc5fd33d2ab164d6bbfdeff34af.camel@sipsolutions.net>
Message-ID: <CAEQ_TvceX3wRoqjYuM3m5oCW4CCNtzSU-aJiGZuX1ixR5KMj6w@mail.gmail.com>

On Thu, Mar 7, 2019 at 11:18 AM Sebastian Berg <sebastian at sipsolutions.net>
wrote:

> Things seem a bit hard to time with all the C/Python boundaries
> involved, but it seems to me that the actual time spend on the C-side
> is reasonably low. The biggest chunk is probably that we have 4
> function calls instead of 1:
>
>   1. Public api call
>   2. dispatch call (get arguments relevant for dispatching)
>   3. Call C-side function implementing the logic
>   4. Call the actual function
>
> Improving that much seems like it might get ugly pretty fast. But I am
> wondering if dispatching from within C for functions that are currently
> defined in C already may be moderately easy (and also the ones with the
> largest pay-off).
>

Yes, I think this could be doable. The main savings is that we would avoid
parsing Python arguments twice.

That said, there are lots of NumPy functions defined in Python, and few
people seem to notice the performance difference, e.g., the speed
difference between np.sum(x) and x.sum() is already larger than the
overhead of dispatching.

If this really matters, then we should probably rewrite functions like
np.sum() in C, too.



> Best,
>
> Sebastian
>
>
>
> >
> > Did I miss something?
> >
> > Fr?d?ric
> >
> > -----Original Message-----
> > From: NumPy-Discussion <
> > numpy-discussion-bounces+fbastien=nvidia.com at python.org> On Behalf Of
> > Stefan van der Walt
> > Sent: Thursday, March 7, 2019 12:15 PM
> > To: Discussion of Numerical Python <numpy-discussion at python.org>
> > Cc: Matthew Rocklin <mrocklin at gmail.com>
> > Subject: Re: [Numpy-discussion] NEP-18 comment
> >
> > Hi Sebastian, Frederic,
> >
> > On Thu, 07 Mar 2019 14:23:10 +0000, Frederic Bastien wrote:
> > > I like your idea Sebastian. This way it is enabled only when needed
> > > and it is invisible to the user at the same time.
> > >
> > > Stefan, does it solve well enough the potential problem you raised?
> >
> > I don't think so.  This means that NumPy suddenly behaves differently
> > when dask is imported, which again causes the problem mentioned
> > earlier:
> > that identical NumPy code could behave differently depending on
> > library versions, imports, and the environment.
> >
> > That said, I think this is a better solution than an environment
> > variable.
> >
> > Anyway, my opinion is just one of many: I'd like to hear what the
> > other developers think.
> >
> > Best regards,
> > St?fan
> > _______________________________________________
> > NumPy-Discussion mailing list
> > NumPy-Discussion at python.org
> > https://mail.python.org/mailman/listinfo/numpy-discussion
> > -------------------------------------------------------------------
> > ----------------
> > This email message is for the sole use of the intended recipient(s)
> > and may contain
> > confidential information.  Any unauthorized review, use, disclosure
> > or distribution
> > is prohibited.  If you are not the intended recipient, please contact
> > the sender by
> > reply email and destroy all copies of the original message.
> > -------------------------------------------------------------------
> > ----------------
> > _______________________________________________
> > NumPy-Discussion mailing list
> > NumPy-Discussion at python.org
> > https://mail.python.org/mailman/listinfo/numpy-discussion
> >
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190307/f9a71eac/attachment.html>

From prishatbachhar at gmail.com  Fri Mar  8 12:20:47 2019
From: prishatbachhar at gmail.com (prishat bachhar)
Date: Fri, 8 Mar 2019 22:50:47 +0530
Subject: [Numpy-discussion] Gsoc aspirant for 2019
Message-ID: <CAF5AobSpPyO94v9RjUwgWBNu8=HFo2tjF9vhKECA9m7MKDDMWg@mail.gmail.com>

Respected mentor,
I am a 2nd year student from Jadavpur University, India. I have been using
numpy for quite some time now.I want to contribute to the same.Can you
guide me how to move forward with it. I am quite adept to programming in
Python as well as C and C++. Some guidance will be very helpful.

Thank you,
Prishat Bachhar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190308/11638417/attachment.html>

From ralf.gommers at gmail.com  Fri Mar  8 13:17:56 2019
From: ralf.gommers at gmail.com (Ralf Gommers)
Date: Fri, 8 Mar 2019 10:17:56 -0800
Subject: [Numpy-discussion] Gsoc aspirant for 2019
In-Reply-To: <CAF5AobSpPyO94v9RjUwgWBNu8=HFo2tjF9vhKECA9m7MKDDMWg@mail.gmail.com>
References: <CAF5AobSpPyO94v9RjUwgWBNu8=HFo2tjF9vhKECA9m7MKDDMWg@mail.gmail.com>
Message-ID: <CABL7CQgtm1Y=efi21MrW41uVUn7mj5rtGrK_c3DftQ0BJvcuvw@mail.gmail.com>

On Fri, Mar 8, 2019 at 9:21 AM prishat bachhar <prishatbachhar at gmail.com>
wrote:

> Respected mentor,
> I am a 2nd year student from Jadavpur University, India. I have been using
> numpy for quite some time now.I want to contribute to the same.Can you
> guide me how to move forward with it. I am quite adept to programming in
> Python as well as C and C++. Some guidance will be very helpful.
>
Hi Prishat, NumPy does not participate in GSoC. You can find the projects
that do at http://python-gsoc.org/

Cheers,
Ralf

Thank you,
> Prishat Bachhar
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190308/d07a7bdb/attachment.html>

From ralf.gommers at gmail.com  Tue Mar 12 01:44:18 2019
From: ralf.gommers at gmail.com (Ralf Gommers)
Date: Mon, 11 Mar 2019 22:44:18 -0700
Subject: [Numpy-discussion] Fwd: Announcement and thanks to Season of Docs
 survey respondents: Season of Docs has launched
In-Reply-To: <CAEyDeRss0W_O3yE6mr7p_iAD_d3Wxv=zNpin6sTbezKCS5SboQ@mail.gmail.com>
References: <CAEyDeRss0W_O3yE6mr7p_iAD_d3Wxv=zNpin6sTbezKCS5SboQ@mail.gmail.com>
Message-ID: <CABL7CQg_NN6Y4OT0ivXZ7hkQSKaveNNwfnHSKidXSobFQNhEEQ@mail.gmail.com>

It's official, Season of Docs is happening! Does look very interesting, I'd
love to see NumPy and SciPy participate.

Ralf



---------- Forwarded message ---------
From: Sarah Maddox <sarahmaddox at google.com>
Date: Mon, Mar 11, 2019 at 2:56 PM
Subject: Announcement and thanks to Season of Docs survey respondents:
Season of Docs has launched
To:


Thank you for your feedback on the initial proposal of Google?s Season of
Docs program! You?re receiving this email because you indicated that you?d
like us to send you updates about the program.

We?re delighted to announce that we?ve launched the 2019 pilot of Season of
Docs. Details are on our website: g.co/seasonofdocs
<https://developers.google.com/season-of-docs/>.

Season of Docs is a Google program that fosters collaboration between open
source projects and technical writers. It?s similar to Summer of Code, but
with a focus on documentation and technical writers.

Would you like to take part as a mentor in the inaugural year of Season of
Docs? Organization applications open on April 2, 2019. See the full timeline
<https://developers.google.com/season-of-docs/docs/timeline> and join the
announcement group at season-of-docs-announce
<https://groups.google.com/group/season-of-docs-announce> to stay informed.

Please do tweet and blog about Season of Docs if you?d like to share the
news. We want as many people to know about it as possible. We?ve provided
logos that you can download and some example content on the press page
<https://developers.google.com/season-of-docs/docs/press>.

If you have any questions, please email
season-of-docs-support at googlegroups.com.

Many thanks again for your valuable feedback on the initial proposal.

Sarah Maddox, Andrew Chen, and the Season of Docs team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190311/c9ce6bd9/attachment.html>

From kerlynmanyi at gmail.com  Tue Mar 12 03:36:03 2019
From: kerlynmanyi at gmail.com (Nkep Kerlyn)
Date: Tue, 12 Mar 2019 08:36:03 +0100
Subject: [Numpy-discussion] MY INTRODUCTION TO NumPy COMMUNITY
Message-ID: <CALY=LBH1Ri5g4kG3wkXyZ3Vy5Bmhv2SAxNc_kevfsy=i4L05CA@mail.gmail.com>

Hello everyone,

I am a Computer Engineer(Telecoms major) from Buea, Cameroon. I recently
completed undergraduate studies from the University of Buea.

I am interested in contributing to NumPy during and after the upcoming
session of Outreachy 2019. I am proficient in Python and  fluent in English
speaking and communication. I am also a beginner in NumPy but I am ever
ready to learn.

I have looked at the Outreachy Ideas page. I have setup my development
environment and will start solving issues immediately. I will be grateful
if i can be pointed out to a good first bug.

I look forward to interacting with you all and contributing to this awesome
community.

Regards,
Kerlyn Nkep.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190312/1f506a83/attachment.html>

From asishkrramuk at gmail.com  Tue Mar 12 08:22:00 2019
From: asishkrramuk at gmail.com (asish kr)
Date: Tue, 12 Mar 2019 17:52:00 +0530
Subject: [Numpy-discussion] Outreachy applicant
Message-ID: <CA+vg+Cr2twMSgzrh2UuMRDNyfGhWQRJ_YL1Ro1a7_dMsVQzDDQ@mail.gmail.com>

Hi,  i am an outreachy applicant and would like to contribute to this
project.  Is there anyone who could guide me here. Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190312/9b94b107/attachment.html>

From prishatbachhar at gmail.com  Tue Mar 12 12:15:20 2019
From: prishatbachhar at gmail.com (prishat bachhar)
Date: Tue, 12 Mar 2019 21:45:20 +0530
Subject: [Numpy-discussion] Gsoc 2019
Message-ID: <CAF5AobRu=yFJkdiG4TnKSkSmoPqL2YXPHyO6Wpgi-KReXSMz3g@mail.gmail.com>

Respected community members
I am a 2nd year student from Jadavpur University. I have been using numpy
and Python for 2 years and would like to contribute to it. I am able to
code in Python and C++. Can someone guide me.
On Mar 12, 2019 9:30 PM, <numpy-discussion-request at python.org> wrote:

> Send NumPy-Discussion mailing list submissions to
>         numpy-discussion at python.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://mail.python.org/mailman/listinfo/numpy-discussion
> or, via email, send a message with subject or body 'help' to
>         numpy-discussion-request at python.org
>
> You can reach the person managing the list at
>         numpy-discussion-owner at python.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of NumPy-Discussion digest..."
>
>
> Today's Topics:
>
>    1. Fwd: Announcement and thanks to Season of Docs survey
>       respondents: Season of Docs has launched (Ralf Gommers)
>    2. MY INTRODUCTION TO NumPy COMMUNITY (Nkep Kerlyn)
>    3. Outreachy applicant (asish kr)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 11 Mar 2019 22:44:18 -0700
> From: Ralf Gommers <ralf.gommers at gmail.com>
> To: Discussion of Numerical Python <numpy-discussion at python.org>,
>         SciPy Developers List <scipy-dev at python.org>
> Subject: [Numpy-discussion] Fwd: Announcement and thanks to Season of
>         Docs survey respondents: Season of Docs has launched
> Message-ID:
>         <CABL7CQg_NN6Y4OT0ivXZ7hkQSKaveNNwfnHSKi
> dXSobFQNhEEQ at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> It's official, Season of Docs is happening! Does look very interesting, I'd
> love to see NumPy and SciPy participate.
>
> Ralf
>
>
>
> ---------- Forwarded message ---------
> From: Sarah Maddox <sarahmaddox at google.com>
> Date: Mon, Mar 11, 2019 at 2:56 PM
> Subject: Announcement and thanks to Season of Docs survey respondents:
> Season of Docs has launched
> To:
>
>
> Thank you for your feedback on the initial proposal of Google?s Season of
> Docs program! You?re receiving this email because you indicated that you?d
> like us to send you updates about the program.
>
> We?re delighted to announce that we?ve launched the 2019 pilot of Season of
> Docs. Details are on our website: g.co/seasonofdocs
> <https://developers.google.com/season-of-docs/>.
>
> Season of Docs is a Google program that fosters collaboration between open
> source projects and technical writers. It?s similar to Summer of Code, but
> with a focus on documentation and technical writers.
>
> Would you like to take part as a mentor in the inaugural year of Season of
> Docs? Organization applications open on April 2, 2019. See the full
> timeline
> <https://developers.google.com/season-of-docs/docs/timeline> and join the
> announcement group at season-of-docs-announce
> <https://groups.google.com/group/season-of-docs-announce> to stay
> informed.
>
> Please do tweet and blog about Season of Docs if you?d like to share the
> news. We want as many people to know about it as possible. We?ve provided
> logos that you can download and some example content on the press page
> <https://developers.google.com/season-of-docs/docs/press>.
>
> If you have any questions, please email
> season-of-docs-support at googlegroups.com.
>
> Many thanks again for your valuable feedback on the initial proposal.
>
> Sarah Maddox, Andrew Chen, and the Season of Docs team
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mail.python.org/pipermail/numpy-discussion/
> attachments/20190311/c9ce6bd9/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 12 Mar 2019 08:36:03 +0100
> From: Nkep Kerlyn <kerlynmanyi at gmail.com>
> To: numpy-discussion at python.org
> Subject: [Numpy-discussion] MY INTRODUCTION TO NumPy COMMUNITY
> Message-ID:
>         <CALY=LBH1Ri5g4kG3wkXyZ3Vy5Bmhv2SAxNc_kevfsy=i4L05CA at mail.gmail.
> com>
> Content-Type: text/plain; charset="utf-8"
>
> Hello everyone,
>
> I am a Computer Engineer(Telecoms major) from Buea, Cameroon. I recently
> completed undergraduate studies from the University of Buea.
>
> I am interested in contributing to NumPy during and after the upcoming
> session of Outreachy 2019. I am proficient in Python and  fluent in English
> speaking and communication. I am also a beginner in NumPy but I am ever
> ready to learn.
>
> I have looked at the Outreachy Ideas page. I have setup my development
> environment and will start solving issues immediately. I will be grateful
> if i can be pointed out to a good first bug.
>
> I look forward to interacting with you all and contributing to this awesome
> community.
>
> Regards,
> Kerlyn Nkep.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mail.python.org/pipermail/numpy-discussion/
> attachments/20190312/1f506a83/attachment-0001.html>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 12 Mar 2019 17:52:00 +0530
> From: asish kr <asishkrramuk at gmail.com>
> To: numpy-discussion at python.org
> Subject: [Numpy-discussion] Outreachy applicant
> Message-ID:
>         <CA+vg+Cr2twMSgzrh2UuMRDNyfGhWQRJ_YL1Ro1a7_dMsVQzDDQ at mail.gmail.
> com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,  i am an outreachy applicant and would like to contribute to this
> project.  Is there anyone who could guide me here. Thanks
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mail.python.org/pipermail/numpy-discussion/
> attachments/20190312/9b94b107/attachment-0001.html>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
>
> ------------------------------
>
> End of NumPy-Discussion Digest, Vol 150, Issue 8
> ************************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190312/a15d7b2d/attachment.html>

From tyler.je.reddy at gmail.com  Tue Mar 12 12:47:29 2019
From: tyler.je.reddy at gmail.com (Tyler Reddy)
Date: Tue, 12 Mar 2019 09:47:29 -0700
Subject: [Numpy-discussion] BIDS / community call March 13
Message-ID: <CAHPuU_ZrdTRAr6d9uV2qmXZuwtHi4uzVuESMmcB8DfKFV92BzQ@mail.gmail.com>

Hi,

A reminder of our weekly community call tomorrow, March 13th, at 12 pm
Pacific Time. Note that we recently started Daylight Savings Time in
California, so some locations may experience a relative time difference.

There's a section for community-suggested topics in the meeting document
that may be edited: https://hackmd.io/pYftrlnJQR-opNHS9Zg7-A?view
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190312/5592a840/attachment.html>

From ralf.gommers at gmail.com  Tue Mar 12 14:20:31 2019
From: ralf.gommers at gmail.com (Ralf Gommers)
Date: Tue, 12 Mar 2019 11:20:31 -0700
Subject: [Numpy-discussion] Gsoc 2019
In-Reply-To: <CAF5AobRu=yFJkdiG4TnKSkSmoPqL2YXPHyO6Wpgi-KReXSMz3g@mail.gmail.com>
References: <CAF5AobRu=yFJkdiG4TnKSkSmoPqL2YXPHyO6Wpgi-KReXSMz3g@mail.gmail.com>
Message-ID: <CABL7CQhG52jHW8qJrSGnmjALTT9jUa+sYn=Y1kjoz1OmL9n3xw@mail.gmail.com>

On Tue, Mar 12, 2019 at 9:15 AM prishat bachhar <prishatbachhar at gmail.com>
wrote:

> Respected community members
> I am a 2nd year student from Jadavpur University. I have been using numpy
> and Python for 2 years and would like to contribute to it. I am able to
> code in Python and C++. Can someone guide me.
>
Hi Prishat, NumPy does not participate in GSoC, sorry.

Cheers,
Ralf


On Mar 12, 2019 9:30 PM, <numpy-discussion-request at python.org> wrote:
>
>> Send NumPy-Discussion mailing list submissions to
>>         numpy-discussion at python.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>         https://mail.python.org/mailman/listinfo/numpy-discussion
>> or, via email, send a message with subject or body 'help' to
>>         numpy-discussion-request at python.org
>>
>> You can reach the person managing the list at
>>         numpy-discussion-owner at python.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of NumPy-Discussion digest..."
>>
>>
>> Today's Topics:
>>
>>    1. Fwd: Announcement and thanks to Season of Docs survey
>>       respondents: Season of Docs has launched (Ralf Gommers)
>>    2. MY INTRODUCTION TO NumPy COMMUNITY (Nkep Kerlyn)
>>    3. Outreachy applicant (asish kr)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Mon, 11 Mar 2019 22:44:18 -0700
>> From: Ralf Gommers <ralf.gommers at gmail.com>
>> To: Discussion of Numerical Python <numpy-discussion at python.org>,
>>         SciPy Developers List <scipy-dev at python.org>
>> Subject: [Numpy-discussion] Fwd: Announcement and thanks to Season of
>>         Docs survey respondents: Season of Docs has launched
>> Message-ID:
>>         <
>> CABL7CQg_NN6Y4OT0ivXZ7hkQSKaveNNwfnHSKidXSobFQNhEEQ at mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> It's official, Season of Docs is happening! Does look very interesting,
>> I'd
>> love to see NumPy and SciPy participate.
>>
>> Ralf
>>
>>
>>
>> ---------- Forwarded message ---------
>> From: Sarah Maddox <sarahmaddox at google.com>
>> Date: Mon, Mar 11, 2019 at 2:56 PM
>> Subject: Announcement and thanks to Season of Docs survey respondents:
>> Season of Docs has launched
>> To:
>>
>>
>> Thank you for your feedback on the initial proposal of Google?s Season of
>> Docs program! You?re receiving this email because you indicated that you?d
>> like us to send you updates about the program.
>>
>> We?re delighted to announce that we?ve launched the 2019 pilot of Season
>> of
>> Docs. Details are on our website: g.co/seasonofdocs
>> <https://developers.google.com/season-of-docs/>.
>>
>> Season of Docs is a Google program that fosters collaboration between open
>> source projects and technical writers. It?s similar to Summer of Code, but
>> with a focus on documentation and technical writers.
>>
>> Would you like to take part as a mentor in the inaugural year of Season of
>> Docs? Organization applications open on April 2, 2019. See the full
>> timeline
>> <https://developers.google.com/season-of-docs/docs/timeline> and join the
>> announcement group at season-of-docs-announce
>> <https://groups.google.com/group/season-of-docs-announce> to stay
>> informed.
>>
>> Please do tweet and blog about Season of Docs if you?d like to share the
>> news. We want as many people to know about it as possible. We?ve provided
>> logos that you can download and some example content on the press page
>> <https://developers.google.com/season-of-docs/docs/press>.
>>
>> If you have any questions, please email
>> season-of-docs-support at googlegroups.com.
>>
>> Many thanks again for your valuable feedback on the initial proposal.
>>
>> Sarah Maddox, Andrew Chen, and the Season of Docs team
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <
>> http://mail.python.org/pipermail/numpy-discussion/attachments/20190311/c9ce6bd9/attachment-0001.html
>> >
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Tue, 12 Mar 2019 08:36:03 +0100
>> From: Nkep Kerlyn <kerlynmanyi at gmail.com>
>> To: numpy-discussion at python.org
>> Subject: [Numpy-discussion] MY INTRODUCTION TO NumPy COMMUNITY
>> Message-ID:
>>         <CALY=LBH1Ri5g4kG3wkXyZ3Vy5Bmhv2SAxNc_kevfsy=
>> i4L05CA at mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hello everyone,
>>
>> I am a Computer Engineer(Telecoms major) from Buea, Cameroon. I recently
>> completed undergraduate studies from the University of Buea.
>>
>> I am interested in contributing to NumPy during and after the upcoming
>> session of Outreachy 2019. I am proficient in Python and  fluent in
>> English
>> speaking and communication. I am also a beginner in NumPy but I am ever
>> ready to learn.
>>
>> I have looked at the Outreachy Ideas page. I have setup my development
>> environment and will start solving issues immediately. I will be grateful
>> if i can be pointed out to a good first bug.
>>
>> I look forward to interacting with you all and contributing to this
>> awesome
>> community.
>>
>> Regards,
>> Kerlyn Nkep.
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <
>> http://mail.python.org/pipermail/numpy-discussion/attachments/20190312/1f506a83/attachment-0001.html
>> >
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Tue, 12 Mar 2019 17:52:00 +0530
>> From: asish kr <asishkrramuk at gmail.com>
>> To: numpy-discussion at python.org
>> Subject: [Numpy-discussion] Outreachy applicant
>> Message-ID:
>>         <
>> CA+vg+Cr2twMSgzrh2UuMRDNyfGhWQRJ_YL1Ro1a7_dMsVQzDDQ at mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hi,  i am an outreachy applicant and would like to contribute to this
>> project.  Is there anyone who could guide me here. Thanks
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <
>> http://mail.python.org/pipermail/numpy-discussion/attachments/20190312/9b94b107/attachment-0001.html
>> >
>>
>> ------------------------------
>>
>> Subject: Digest Footer
>>
>> _______________________________________________
>> NumPy-Discussion mailing list
>> NumPy-Discussion at python.org
>> https://mail.python.org/mailman/listinfo/numpy-discussion
>>
>>
>> ------------------------------
>>
>> End of NumPy-Discussion Digest, Vol 150, Issue 8
>> ************************************************
>>
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190312/1cc2c3e2/attachment-0001.html>

From ralf.gommers at gmail.com  Tue Mar 12 14:21:44 2019
From: ralf.gommers at gmail.com (Ralf Gommers)
Date: Tue, 12 Mar 2019 11:21:44 -0700
Subject: [Numpy-discussion] [SciPy-Dev] Fwd: Announcement and thanks to
 Season of Docs survey respondents: Season of Docs has launched
In-Reply-To: <CAGu2niV5eYn=DzWP0kp29O8oOCP3SNsznqmcEzoFWeVzHRF=hg@mail.gmail.com>
References: <CAEyDeRss0W_O3yE6mr7p_iAD_d3Wxv=zNpin6sTbezKCS5SboQ@mail.gmail.com>
 <CABL7CQg_NN6Y4OT0ivXZ7hkQSKaveNNwfnHSKidXSobFQNhEEQ@mail.gmail.com>
 <CAGu2niV5eYn=DzWP0kp29O8oOCP3SNsznqmcEzoFWeVzHRF=hg@mail.gmail.com>
Message-ID: <CABL7CQj0un1iGwQQnPA_pF0vrHr_32tTP4N3o+N=BSC+aZKE2A@mail.gmail.com>

No idea yet. I suspect that either the PSF or NumFOCUS (or both) will
though.

On Tue, Mar 12, 2019 at 8:09 AM Eric Larson <larson.eric.d at gmail.com> wrote:

> Any idea if PSF is going to be an umbrella org for this, as they are for
> GSoC?
>
> Eric
>
>
> On Tue, Mar 12, 2019 at 1:46 AM Ralf Gommers <ralf.gommers at gmail.com>
> wrote:
>
>> It's official, Season of Docs is happening! Does look very interesting,
>> I'd love to see NumPy and SciPy participate.
>>
>> Ralf
>>
>>
>>
>> ---------- Forwarded message ---------
>> From: Sarah Maddox <sarahmaddox at google.com>
>> Date: Mon, Mar 11, 2019 at 2:56 PM
>> Subject: Announcement and thanks to Season of Docs survey respondents:
>> Season of Docs has launched
>> To:
>>
>>
>> Thank you for your feedback on the initial proposal of Google?s Season of
>> Docs program! You?re receiving this email because you indicated that you?d
>> like us to send you updates about the program.
>>
>> We?re delighted to announce that we?ve launched the 2019 pilot of Season
>> of Docs. Details are on our website: g.co/seasonofdocs
>> <https://developers.google.com/season-of-docs/>.
>>
>> Season of Docs is a Google program that fosters collaboration between
>> open source projects and technical writers. It?s similar to Summer of Code,
>> but with a focus on documentation and technical writers.
>>
>> Would you like to take part as a mentor in the inaugural year of Season
>> of Docs? Organization applications open on April 2, 2019. See the full
>> timeline <https://developers.google.com/season-of-docs/docs/timeline>
>> and join the announcement group at season-of-docs-announce
>> <https://groups.google.com/group/season-of-docs-announce> to stay
>> informed.
>>
>> Please do tweet and blog about Season of Docs if you?d like to share the
>> news. We want as many people to know about it as possible. We?ve provided
>> logos that you can download and some example content on the press page
>> <https://developers.google.com/season-of-docs/docs/press>.
>>
>> If you have any questions, please email
>> season-of-docs-support at googlegroups.com.
>>
>> Many thanks again for your valuable feedback on the initial proposal.
>>
>> Sarah Maddox, Andrew Chen, and the Season of Docs team
>>
>> _______________________________________________
>> SciPy-Dev mailing list
>> SciPy-Dev at python.org
>> https://mail.python.org/mailman/listinfo/scipy-dev
>>
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev at python.org
> https://mail.python.org/mailman/listinfo/scipy-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190312/08781edf/attachment.html>

From stefanv at berkeley.edu  Wed Mar 13 16:05:17 2019
From: stefanv at berkeley.edu (Stefan van der Walt)
Date: Wed, 13 Mar 2019 13:05:17 -0700
Subject: [Numpy-discussion] #4808 -- let np.pad default to constant
Message-ID: <20190313200517.gd27qtq6tvllvpbz@carbo>

In PR 4808, I propose changing the default padding mode (for `np.pad`)
to constant (0).

It was suggested that I mention the change here, in case someone has a
use case or argument for not making it.

https://github.com/numpy/numpy/pull/4808

Thanks!
St?fan

From warren.weckesser at gmail.com  Wed Mar 13 17:04:35 2019
From: warren.weckesser at gmail.com (Warren Weckesser)
Date: Wed, 13 Mar 2019 17:04:35 -0400
Subject: [Numpy-discussion] #4808 -- let np.pad default to constant
In-Reply-To: <20190313200517.gd27qtq6tvllvpbz@carbo>
References: <20190313200517.gd27qtq6tvllvpbz@carbo>
Message-ID: <CAGzF1ud7VY3wcth4BowtGqM2nc736z2s+-6qskC5wiKsUtCAMA@mail.gmail.com>

On 3/13/19, Stefan van der Walt <stefanv at berkeley.edu> wrote:
> In PR 4808, I propose changing the default padding mode (for `np.pad`)
> to constant (0).

+1

Warren

>
> It was suggested that I mention the change here, in case someone has a
> use case or argument for not making it.
>
> https://github.com/numpy/numpy/pull/4808
>
> Thanks!
> St?fan
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>

From matti.picus at gmail.com  Wed Mar 13 17:05:48 2019
From: matti.picus at gmail.com (Matti Picus)
Date: Wed, 13 Mar 2019 23:05:48 +0200
Subject: [Numpy-discussion] Outreachy applicant
In-Reply-To: <CA+vg+Cr2twMSgzrh2UuMRDNyfGhWQRJ_YL1Ro1a7_dMsVQzDDQ@mail.gmail.com>
References: <CA+vg+Cr2twMSgzrh2UuMRDNyfGhWQRJ_YL1Ro1a7_dMsVQzDDQ@mail.gmail.com>
Message-ID: <900cfc93-510d-cae4-3477-04674ca428b9@gmail.com>


On 12/3/19 2:22 pm, asish kr wrote:
> Hi,? i am an outreachy applicant and would like to contribute to this 
> project.? Is there anyone who could guide me here. Thanks
>
>

I responded privately to the applicant. More information about our 
Outreachy mentoring is here 
https://www.outreachy.org/may-2019-august-2019-outreachy-internships/communities/numpy/improve-c-api-documentation-for-numpy/cfp


Matti


From ralf.gommers at gmail.com  Wed Mar 13 18:46:35 2019
From: ralf.gommers at gmail.com (Ralf Gommers)
Date: Wed, 13 Mar 2019 15:46:35 -0700
Subject: [Numpy-discussion] MY INTRODUCTION TO NumPy COMMUNITY
In-Reply-To: <CALY=LBH1Ri5g4kG3wkXyZ3Vy5Bmhv2SAxNc_kevfsy=i4L05CA@mail.gmail.com>
References: <CALY=LBH1Ri5g4kG3wkXyZ3Vy5Bmhv2SAxNc_kevfsy=i4L05CA@mail.gmail.com>
Message-ID: <CABL7CQiia=z3MGHxHj48AXV6bFMWQW5WdH5mf+j81GP6VwbJ3w@mail.gmail.com>

Hi Kerlyn, welcome!

On Tue, Mar 12, 2019 at 12:36 AM Nkep Kerlyn <kerlynmanyi at gmail.com> wrote:

> Hello everyone,
>
> I am a Computer Engineer(Telecoms major) from Buea, Cameroon. I recently
> completed undergraduate studies from the University of Buea.
>
> I am interested in contributing to NumPy during and after the upcoming
> session of Outreachy 2019. I am proficient in Python and  fluent in English
> speaking and communication. I am also a beginner in NumPy but I am ever
> ready to learn.
>
> I have looked at the Outreachy Ideas page. I have setup my development
> environment and will start solving issues immediately. I will be grateful
> if i can be pointed out to a good first bug.
>

I think Matti or another mentor already replied off-list or in the
Outreachy forum, but I thought I'd point out a good issue here as well:
https://github.com/numpy/numpy/issues/13114. The numpy.ma and
numpy.polynomial parts of that are probably a little easier to get started
with than the C API part, so I would recommend picking one of those. Please
feel free to comment on the Github issue if you need some help.

Cheers,
Ralf


> I look forward to interacting with you all and contributing to this
> awesome community.
>
> Regards,
> Kerlyn Nkep.
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190313/f648abee/attachment.html>

From pmhobson at gmail.com  Wed Mar 13 20:02:37 2019
From: pmhobson at gmail.com (Paul Hobson)
Date: Wed, 13 Mar 2019 17:02:37 -0700
Subject: [Numpy-discussion] #4808 -- let np.pad default to constant
In-Reply-To: <CAGzF1ud7VY3wcth4BowtGqM2nc736z2s+-6qskC5wiKsUtCAMA@mail.gmail.com>
References: <20190313200517.gd27qtq6tvllvpbz@carbo>
 <CAGzF1ud7VY3wcth4BowtGqM2nc736z2s+-6qskC5wiKsUtCAMA@mail.gmail.com>
Message-ID: <CADT3MEBsDLb5rTVNCOJwwroKJsRWT96dK4Niu+wZJSH_Q=J-TQ@mail.gmail.com>

As a user, I think this is a good change.

On Wed, Mar 13, 2019 at 2:05 PM Warren Weckesser <warren.weckesser at gmail.com>
wrote:

> On 3/13/19, Stefan van der Walt <stefanv at berkeley.edu> wrote:
> > In PR 4808, I propose changing the default padding mode (for `np.pad`)
> > to constant (0).
>
> +1
>
> Warren
>
> >
> > It was suggested that I mention the change here, in case someone has a
> > use case or argument for not making it.
> >
> > https://github.com/numpy/numpy/pull/4808
> >
> > Thanks!
> > St?fan
> > _______________________________________________
> > NumPy-Discussion mailing list
> > NumPy-Discussion at python.org
> > https://mail.python.org/mailman/listinfo/numpy-discussion
> >
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190313/9393bce8/attachment-0001.html>

From stefanv at berkeley.edu  Fri Mar 15 14:39:52 2019
From: stefanv at berkeley.edu (Stefan van der Walt)
Date: Fri, 15 Mar 2019 11:39:52 -0700
Subject: [Numpy-discussion] NumPy sprint at BIDS: May 10/11
Message-ID: <20190315183952.4zfzok55wwgri3mm@carbo>

Hi everyone,

On May 10/11, we will host another NumPy sprint at the Berkeley
Institute for Data Science.  The focus of this meeting will be the
design of a new data type system, and to consolidate:

- https://github.com/numpy/numpy/pull/12630 [Matti's NEP PR WIP]
- https://hackmd.io/ok21UoAQQmOtSVk6keaJhw?view [Matti's dtype notes]
- https://hackmd.io/s/ryTFaOPHE# [Eric's dtype notes]

Please let me know if you are interested in attending.

Best regards,
St?fan

From luckysandy99 at gmail.com  Sat Mar 16 03:59:07 2019
From: luckysandy99 at gmail.com (Sandy)
Date: Sat, 16 Mar 2019 13:29:07 +0530
Subject: [Numpy-discussion] Testing your contributions
Message-ID: <CAA4aTATHUQ4V_5PrPLAmQ9J6zymU2vP3b3KGkaKw4Zb63BiWUQ@mail.gmail.com>

Hey there,

I am new to numpy. I just wanted to know, suppose I make a code
contribution to the repo https://github.com/numpy/numpy how do I test
its working?

From kmckenna at baselinesw.com  Sat Mar 16 06:04:12 2019
From: kmckenna at baselinesw.com (kmckenna at baselinesw.com)
Date: Sat, 16 Mar 2019 06:04:12 -0400
Subject: [Numpy-discussion] introducing Numpy.net,
 a pure C# implementation of Numpy
Message-ID: <000701d4dbdf$9c7832e0$d56898a0$@baselinesw.com>

This is a quick note to announce open source numpy.net available at this
repository

 

https://github.com/Quansight-Labs/numpy.net

 

This is a pure C# based implementation of Numpy, ported from the underlying
C library and the python application layer.

Written and tested on .NET standard 2.1 so it will run anywhere.

 

I have the vast majority of the most commonly used functions implemented and
unit tested. It supports fully functional slicing and views.

Verified to generate binary compatible output with python numpy.

 

I built it because I was tasked with porting a large Python Numpy
application to C# and as you may know, there are not a lot of good solutions
(until now).  My employer graciously agreed to open source it.

 

If you have some time to review it, I'd love to get some feedback from some
Numpy experts (I don't consider myself one).

 

I believe it is ready to start building tools like SciPy on top of it.

 

Longer term, I would like to see this ported to Java.  I expect pure C# to
port easily to Java.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190316/12a5b077/attachment.html>

From charlesr.harris at gmail.com  Sat Mar 16 12:02:02 2019
From: charlesr.harris at gmail.com (Charles R Harris)
Date: Sat, 16 Mar 2019 10:02:02 -0600
Subject: [Numpy-discussion] introducing Numpy.net,
 a pure C# implementation of Numpy
In-Reply-To: <000701d4dbdf$9c7832e0$d56898a0$@baselinesw.com>
References: <000701d4dbdf$9c7832e0$d56898a0$@baselinesw.com>
Message-ID: <CAB6mnxJMPXM0E5eLyRYohkCW5bm29nA5eQS7w_2wNEMAdoJrug@mail.gmail.com>

On Sat, Mar 16, 2019 at 4:41 AM <kmckenna at baselinesw.com> wrote:

> This is a quick note to announce open source numpy.net available at this
> repository
>
>
>
> https://github.com/Quansight-Labs/numpy.net
>
>
>
> This is a pure C# based implementation of Numpy, ported from the
> underlying C library and the python application layer.
>
> Written and tested on .NET standard 2.1 so it will run anywhere.
>
>
>
> I have the vast majority of the most commonly used functions implemented
> and unit tested. It supports fully functional slicing and views.
>
> Verified to generate binary compatible output with python numpy.
>
>
>
> I built it because I was tasked with porting a large Python Numpy
> application to C# and as you may know, there are not a lot of good
> solutions (until now).  My employer graciously agreed to open source it.
>
>
>
> If you have some time to review it, I'd love to get some feedback from
> some Numpy experts (I don't consider myself one).
>
>
>
> I believe it is ready to start building tools like SciPy on top of it.
>
>
>
> Longer term, I would like to see this ported to Java.  I expect pure C# to
> port easily to Java.
>

That's interesting. What parts are in C#? Any benchmarks comparing the two
implementations?

Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190316/bfaea5d1/attachment.html>

From charlesr.harris at gmail.com  Sat Mar 16 12:06:24 2019
From: charlesr.harris at gmail.com (Charles R Harris)
Date: Sat, 16 Mar 2019 10:06:24 -0600
Subject: [Numpy-discussion] introducing Numpy.net,
 a pure C# implementation of Numpy
In-Reply-To: <CAB6mnxJMPXM0E5eLyRYohkCW5bm29nA5eQS7w_2wNEMAdoJrug@mail.gmail.com>
References: <000701d4dbdf$9c7832e0$d56898a0$@baselinesw.com>
 <CAB6mnxJMPXM0E5eLyRYohkCW5bm29nA5eQS7w_2wNEMAdoJrug@mail.gmail.com>
Message-ID: <CAB6mnxLiiQYFaxDStAkR-c2-MHdpHiq81MoCwiPqpj-5-+o8Bw@mail.gmail.com>

On Sat, Mar 16, 2019 at 10:02 AM Charles R Harris <charlesr.harris at gmail.com>
wrote:

>
>
> On Sat, Mar 16, 2019 at 4:41 AM <kmckenna at baselinesw.com> wrote:
>
>> This is a quick note to announce open source numpy.net available at this
>> repository
>>
>>
>>
>> https://github.com/Quansight-Labs/numpy.net
>>
>>
>>
>> This is a pure C# based implementation of Numpy, ported from the
>> underlying C library and the python application layer.
>>
>> Written and tested on .NET standard 2.1 so it will run anywhere.
>>
>>
>>
>> I have the vast majority of the most commonly used functions implemented
>> and unit tested. It supports fully functional slicing and views.
>>
>> Verified to generate binary compatible output with python numpy.
>>
>>
>>
>> I built it because I was tasked with porting a large Python Numpy
>> application to C# and as you may know, there are not a lot of good
>> solutions (until now).  My employer graciously agreed to open source it.
>>
>>
>>
>> If you have some time to review it, I'd love to get some feedback from
>> some Numpy experts (I don't consider myself one).
>>
>>
>>
>> I believe it is ready to start building tools like SciPy on top of it.
>>
>>
>>
>> Longer term, I would like to see this ported to Java.  I expect pure C#
>> to port easily to Java.
>>
>
> That's interesting. What parts are in C#? Any benchmarks comparing the two
> implementations?
>
>
What about BLAS libraries?

Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190316/98505b85/attachment.html>

From matti.picus at gmail.com  Sat Mar 16 12:42:00 2019
From: matti.picus at gmail.com (Matti Picus)
Date: Sat, 16 Mar 2019 18:42:00 +0200
Subject: [Numpy-discussion] Testing your contributions
In-Reply-To: <CAA4aTATHUQ4V_5PrPLAmQ9J6zymU2vP3b3KGkaKw4Zb63BiWUQ@mail.gmail.com>
References: <CAA4aTATHUQ4V_5PrPLAmQ9J6zymU2vP3b3KGkaKw4Zb63BiWUQ@mail.gmail.com>
Message-ID: <a08ea6db-05b5-848a-3517-432563150162@gmail.com>

On 16/3/19 9:59 am, Sandy wrote:
> Hey there,
>
> I am new to numpy. I just wanted to know, suppose I make a code
> contribution to the repo https://github.com/numpy/numpy how do I test
> its working?
> _______________________________________________


Welcome.

You should add a test.

Running `python runtest.py` will build and run all the tests, including 
your new one.

More information is available at 
www.numpy.org/devdocs/reference/testing.html

More information about a typical development workflow is at 
www.numpy.org/devdocs/dev/gitwash/development_workflow.html


Please pinpoint unclear documentation by opening an issue 
https://github.com/numpy/numpy/issues.


In general, you will get a more sympathetic response by trying something 
first and reporting what didn't work or what was unclear.


Matti


From kmckenna at baselinesw.com  Sat Mar 16 12:21:07 2019
From: kmckenna at baselinesw.com (kmckenna at baselinesw.com)
Date: Sat, 16 Mar 2019 12:21:07 -0400
Subject: [Numpy-discussion] [SPAM]Re:  introducing Numpy.net,
 a pure C# implementation of Numpy
In-Reply-To: <CAB6mnxLiiQYFaxDStAkR-c2-MHdpHiq81MoCwiPqpj-5-+o8Bw@mail.gmail.com>
References: <000701d4dbdf$9c7832e0$d56898a0$@baselinesw.com>
 <CAB6mnxJMPXM0E5eLyRYohkCW5bm29nA5eQS7w_2wNEMAdoJrug@mail.gmail.com>
 <CAB6mnxLiiQYFaxDStAkR-c2-MHdpHiq81MoCwiPqpj-5-+o8Bw@mail.gmail.com>
Message-ID: <004701d4dc14$44981060$cdc83120$@baselinesw.com>

 

 

From: NumPy-Discussion <numpy-discussion-bounces+kmckenna=baselinesw.com at python.org> On Behalf Of Charles R Harris
Sent: Saturday, March 16, 2019 12:06 PM
To: Discussion of Numerical Python <numpy-discussion at python.org>
Subject: [SPAM]Re: [Numpy-discussion] introducing Numpy.net, a pure C# implementation of Numpy

 

 

 

On Sat, Mar 16, 2019 at 10:02 AM Charles R Harris <charlesr.harris at gmail.com <mailto:charlesr.harris at gmail.com> > wrote:

 

 

On Sat, Mar 16, 2019 at 4:41 AM <kmckenna at baselinesw.com <mailto:kmckenna at baselinesw.com> > wrote:

This is a quick note to announce open source numpy.net <http://numpy.net>  available at this repository

 

https://github.com/Quansight-Labs/numpy.net

 

This is a pure C# based implementation of Numpy, ported from the underlying C library and the python application layer.

Written and tested on .NET standard 2.1 so it will run anywhere.

 

I have the vast majority of the most commonly used functions implemented and unit tested. It supports fully functional slicing and views.

Verified to generate binary compatible output with python numpy.

 

I built it because I was tasked with porting a large Python Numpy application to C# and as you may know, there are not a lot of good solutions (until now).  My employer graciously agreed to open source it.

 

If you have some time to review it, I'd love to get some feedback from some Numpy experts (I don't consider myself one).

 

I believe it is ready to start building tools like SciPy on top of it.

 

Longer term, I would like to see this ported to Java.  I expect pure C# to port easily to Java.

 

That's interesting. What parts are in C#? Any benchmarks comparing the two implementations?

 

 

What about BLAS libraries?

 

 

1.	All of it is in C#.   The underlying C code was ported and so was the python layer.
2.	Benchmarks?   If you mean performance benchmarks, I have nothing official but I will say that the C# implementation is not as fast as the optimized C code and it never will be.  The only place you would really notice it is if you were doing a UFUNC operation on a large array.
3.	I am not a numpy programmer so I don?t know what BLAS libraries are.  I just did a quick google and my guess is that this is not relevant in my implementation.

 

I envision my tool to be used if someone wants to port a numpy application to .NET or wants to do Numpy things in a .NET application,

 

Kevin

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190316/f6760ecb/attachment-0001.html>

From charlesr.harris at gmail.com  Sat Mar 16 13:22:01 2019
From: charlesr.harris at gmail.com (Charles R Harris)
Date: Sat, 16 Mar 2019 11:22:01 -0600
Subject: [Numpy-discussion] [SPAM]Re: introducing Numpy.net,
 a pure C# implementation of Numpy
In-Reply-To: <004701d4dc14$44981060$cdc83120$@baselinesw.com>
References: <000701d4dbdf$9c7832e0$d56898a0$@baselinesw.com>
 <CAB6mnxJMPXM0E5eLyRYohkCW5bm29nA5eQS7w_2wNEMAdoJrug@mail.gmail.com>
 <CAB6mnxLiiQYFaxDStAkR-c2-MHdpHiq81MoCwiPqpj-5-+o8Bw@mail.gmail.com>
 <004701d4dc14$44981060$cdc83120$@baselinesw.com>
Message-ID: <CAB6mnxLFJ=CSzrCeOTp5DCgpsKB-mSsTTm8RXA5anCh61461hQ@mail.gmail.com>

On Sat, Mar 16, 2019 at 11:10 AM <kmckenna at baselinesw.com> wrote:

>
>
>
>
> *From:* NumPy-Discussion <numpy-discussion-bounces+kmckenna=
> baselinesw.com at python.org> *On Behalf Of *Charles R Harris
> *Sent:* Saturday, March 16, 2019 12:06 PM
> *To:* Discussion of Numerical Python <numpy-discussion at python.org>
> *Subject:* [SPAM]Re: [Numpy-discussion] introducing Numpy.net, a pure C#
> implementation of Numpy
>
>
>
>
>
>
>
> On Sat, Mar 16, 2019 at 10:02 AM Charles R Harris <
> charlesr.harris at gmail.com> wrote:
>
>
>
>
>
> On Sat, Mar 16, 2019 at 4:41 AM <kmckenna at baselinesw.com> wrote:
>
> This is a quick note to announce open source numpy.net available at this
> repository
>
>
>
> https://github.com/Quansight-Labs/numpy.net
>
>
>
> This is a pure C# based implementation of Numpy, ported from the
> underlying C library and the python application layer.
>
> Written and tested on .NET standard 2.1 so it will run anywhere.
>
>
>
> I have the vast majority of the most commonly used functions implemented
> and unit tested. It supports fully functional slicing and views.
>
> Verified to generate binary compatible output with python numpy.
>
>
>
> I built it because I was tasked with porting a large Python Numpy
> application to C# and as you may know, there are not a lot of good
> solutions (until now).  My employer graciously agreed to open source it.
>
>
>
> If you have some time to review it, I'd love to get some feedback from
> some Numpy experts (I don't consider myself one).
>
>
>
> I believe it is ready to start building tools like SciPy on top of it.
>
>
>
> Longer term, I would like to see this ported to Java.  I expect pure C# to
> port easily to Java.
>
>
>
> That's interesting. What parts are in C#? Any benchmarks comparing the two
> implementations?
>
>
>
>
>
> What about BLAS libraries?
>
>
>
>
>
>    1. All of it is in C#.   The underlying C code was ported and so was
>    the python layer.
>    2. Benchmarks?   If you mean performance benchmarks, I have nothing
>    official but I will say that the C# implementation is not as fast as the
>    optimized C code and it never will be.  The only place you would really
>    notice it is if you were doing a UFUNC operation on a large array.
>    3. I am not a numpy programmer so I don?t know what BLAS libraries
>    are.  I just did a quick google and my guess is that this is not relevant
>    in my implementation.
>
>
>
> I envision my tool to be used if someone wants to port a numpy application
> to .NET or wants to do Numpy things in a .NET application,
>
>
>

Just reply to the discussion, I may have made a boo boo in replying to your
first post.

I'm curious. Implementing NumPy in another language seems like quite a bit
of work. Did you have any tools to make it easier? I assume the C api is
gone, so that the translation is NumPy program specific. I've never used
C#, was there a reason to avoid C? What about IronPython? IIRC there was
some work to make NumPy run on IronPython before that project was ended.
I'm also curious what the application was that made it impossible to stay
with python, I suppose the customer wanted C#, but I'd like to know why
plain old Python was not an option.

Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190316/ca561be1/attachment.html>

From teoliphant at gmail.com  Sat Mar 16 17:43:15 2019
From: teoliphant at gmail.com (Travis Oliphant)
Date: Sat, 16 Mar 2019 16:43:15 -0500
Subject: [Numpy-discussion] introducing Numpy.net,
 a pure C# implementation of Numpy
In-Reply-To: <000701d4dbdf$9c7832e0$d56898a0$@baselinesw.com>
References: <000701d4dbdf$9c7832e0$d56898a0$@baselinesw.com>
Message-ID: <CAFMmPGOR3SarqbhqUgaTAjtNfR2=QCyHZeqok_3YW2B2xdxeyw@mail.gmail.com>

Thanks for sharing this work with the world,   What you did is not an easy
task.   This makes it easier for people to port NumPy-based Python code to
C#.  Of course, this group would more likely prefer people to port their C#
code to Python + NumPy.

Nonetheless, I think there are interesting things to learn from your code
for this group as well --- if you could share some of the details of what
it was like to port the code.  Things like where the difficulties where,
any abstraction concepts you developed, as well as things that were
confusing, it would be of value to this community.

Also, a lot of NumPy code these days uses a lot of other libraries.  Did
you also port the numpy.linalg or numpy.fft or numpy.stats modules?   The
numpy.linalg module currently uses low-level libraries in C called BLAS
(Basic Linear Algebra Subprograms).   There are similar interfaces in C#.

Another approach to code-sharing is the XND project  (http://xnd.io) which
allows the creation of NumPy-like interfaces in any language.  Your
implementation would be an interesting start to a C# binding of XND.

Thanks,

-Travis





On Sat, Mar 16, 2019 at 5:41 AM <kmckenna at baselinesw.com> wrote:

> This is a quick note to announce open source numpy.net available at this
> repository
>
>
>
> https://github.com/Quansight-Labs/numpy.net
>
>
>
> This is a pure C# based implementation of Numpy, ported from the
> underlying C library and the python application layer.
>
> Written and tested on .NET standard 2.1 so it will run anywhere.
>
>
>
> I have the vast majority of the most commonly used functions implemented
> and unit tested. It supports fully functional slicing and views.
>
> Verified to generate binary compatible output with python numpy.
>
>
>
> I built it because I was tasked with porting a large Python Numpy
> application to C# and as you may know, there are not a lot of good
> solutions (until now).  My employer graciously agreed to open source it.
>
>
>
> If you have some time to review it, I'd love to get some feedback from
> some Numpy experts (I don't consider myself one).
>
>
>
> I believe it is ready to start building tools like SciPy on top of it.
>
>
>
> Longer term, I would like to see this ported to Java.  I expect pure C# to
> port easily to Java.
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190316/80456ec5/attachment.html>

From nishaaggarwal2810 at gmail.com  Sun Mar 17 09:33:34 2019
From: nishaaggarwal2810 at gmail.com (Nisha Aggarwal)
Date: Sun, 17 Mar 2019 19:03:34 +0530
Subject: [Numpy-discussion] Outreachy applicant: Improve C API Documentation
 for Numpy
Message-ID: <CAN9tnR3RPdX-nPzVkw_c=QEsgn90ojdYfehTpaWLg15QbcrtLg@mail.gmail.com>

Hello,
I am an Outreachy applicant interested in the project: Improve C API
Documentation for Numpy, but I am unsure of how to proceed. Can someone
guide me here?
Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190317/73f7f4f8/attachment-0001.html>

From matti.picus at gmail.com  Sun Mar 17 10:06:44 2019
From: matti.picus at gmail.com (Matti Picus)
Date: Sun, 17 Mar 2019 16:06:44 +0200
Subject: [Numpy-discussion] Outreachy applicant: Improve C API
 Documentation for Numpy
In-Reply-To: <CAN9tnR3RPdX-nPzVkw_c=QEsgn90ojdYfehTpaWLg15QbcrtLg@mail.gmail.com>
References: <CAN9tnR3RPdX-nPzVkw_c=QEsgn90ojdYfehTpaWLg15QbcrtLg@mail.gmail.com>
Message-ID: <b445ec2a-f73b-3542-a2a4-f36c377b56ee@gmail.com>


On 17/3/19 3:33 pm, Nisha Aggarwal wrote:
> Hello,
> I am an Outreachy applicant interested in the project: Improve C API 
> Documentation for Numpy, but I am unsure of how to proceed. Can 
> someone guide me here?
> Thanks
>

Hi and welcome.

The relevant issues have the DOC tag, you can see them via

https://github.com/numpy/numpy/issues?q=is%3Aissue+is%3Aopen+doc+label%3A%2204+-+Documentation%22

Especially relevant are

https://github.com/numpy/numpy/issues/13013 which I think someone is 
already working on

https://github.com/numpy/numpy/pull/13104 which can be broken into a 
number of smaller PRs

https://github.com/numpy/numpy/issues/12632

https://github.com/numpy/numpy/issues/12385

and

https://github.com/numpy/numpy/pull/12097 which is a wip to add a 
version selector. This is not really connected with python or numpy, and 
is a pure javascript issue.


Our workflow is based on github, for an introduction see 
http://www.numpy.org/devdocs/dev/gitwash/development_workflow.html.

For instructions on building the documentation, which uses sphinx, see, 
http://www.numpy.org/devdocs/docs/index.html?highlight=documentation


Matti

From nishaaggarwal2810 at gmail.com  Sun Mar 17 10:49:15 2019
From: nishaaggarwal2810 at gmail.com (Nisha Aggarwal)
Date: Sun, 17 Mar 2019 20:19:15 +0530
Subject: [Numpy-discussion] Outreachy applicant: Improve C API
 Documentation for Numpy
In-Reply-To: <b445ec2a-f73b-3542-a2a4-f36c377b56ee@gmail.com>
References: <CAN9tnR3RPdX-nPzVkw_c=QEsgn90ojdYfehTpaWLg15QbcrtLg@mail.gmail.com>
 <b445ec2a-f73b-3542-a2a4-f36c377b56ee@gmail.com>
Message-ID: <CAN9tnR3gHJ8VMTsxS3rj2Hwpa0DXniQPeF2WrX8zTKyenjtdjg@mail.gmail.com>

Thanks, I'll check it out.




On Sun, 17 Mar 2019 at 19:36, Matti Picus <matti.picus at gmail.com> wrote:

>
> On 17/3/19 3:33 pm, Nisha Aggarwal wrote:
> > Hello,
> > I am an Outreachy applicant interested in the project: Improve C API
> > Documentation for Numpy, but I am unsure of how to proceed. Can
> > someone guide me here?
> > Thanks
> >
>
> Hi and welcome.
>
> The relevant issues have the DOC tag, you can see them via
>
>
> https://github.com/numpy/numpy/issues?q=is%3Aissue+is%3Aopen+doc+label%3A%2204+-+Documentation%22
>
> Especially relevant are
>
> https://github.com/numpy/numpy/issues/13013 which I think someone is
> already working on
>
> https://github.com/numpy/numpy/pull/13104 which can be broken into a
> number of smaller PRs
>
> https://github.com/numpy/numpy/issues/12632
>
> https://github.com/numpy/numpy/issues/12385
>
> and
>
> https://github.com/numpy/numpy/pull/12097 which is a wip to add a
> version selector. This is not really connected with python or numpy, and
> is a pure javascript issue.
>
>
> Our workflow is based on github, for an introduction see
> http://www.numpy.org/devdocs/dev/gitwash/development_workflow.html.
>
> For instructions on building the documentation, which uses sphinx, see,
> http://www.numpy.org/devdocs/docs/index.html?highlight=documentation
>
>
> Matti
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190317/938f1f87/attachment.html>

From madicken.munk at gmail.com  Mon Mar 18 11:54:13 2019
From: madicken.munk at gmail.com (Madicken Munk)
Date: Mon, 18 Mar 2019 10:54:13 -0500
Subject: [Numpy-discussion] 2019 John Hunter Excellence in Plotting Contest
Message-ID: <CACZp+DE8eQBejrDESJhfmmW+PhD7AphRB_kOU5GxPQtiksvh0Q@mail.gmail.com>

In memory of John Hunter, we are pleased to be reviving the SciPy John
Hunter Excellence in Plotting Competition for 2019. This open competition
aims to highlight the importance of data visualization to scientific
progress and showcase the capabilities of open source software.

Participants are invited to submit scientific plots to be judged by a
panel. The winning entries will be announced and displayed at the
conference.

John Hunter?s family and NumFocus are graciously sponsoring cash prizes for
the winners in the following amounts:


   -

   1st prize: $1000
   -

   2nd prize: $750
   -

   3rd prize: $500



   -

   Entries must be submitted by June, 8th to the form at
   https://goo.gl/forms/cFTB3FUBrMPfQ7Vz1
   -

   Winners will be announced at Scipy 2019 in Austin, TX.
   -

   Participants do not need to attend the Scipy conference.
   -

   Entries may take the definition of ?visualization? rather broadly.
   Entries may be, for example, a traditional printed plot, an interactive
   visualization for the web, or an animation.
   -

   Source code for the plot must be provided, in the form of Python code
   and/or a Jupyter notebook, along with a rendering of the plot in a widely
   used format.  This may be, for example, PDF for print, standalone HTML and
   Javascript for an interactive plot, or MPEG-4 for a video. If the original
   data can not be shared for reasons of size or licensing, "fake" data may be
   substituted, along with an image of the plot using real data.
   -

   Each entry must include a 300-500 word abstract describing the plot and
   its importance for a general scientific audience.
   -

   Entries will be judged on their clarity, innovation and aesthetics, but
   most importantly for their effectiveness in communicating a real-world
   problem. Entrants are encouraged to submit plots that were used during the
   course of research or work, rather than merely being hypothetical.
   -

   SciPy reserves the right to display any and all entries, whether
   prize-winning or not, at the conference, use in any materials or on its
   website, with attribution to the original author(s).


SciPy John Hunter Excellence in Plotting Competition Co-Chairs

Hannah Aizenman

Thomas Caswell

Madicken Munk

Nelle Varoquaux
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190318/b5ecc581/attachment.html>

From pmhobson at gmail.com  Mon Mar 18 16:18:42 2019
From: pmhobson at gmail.com (Paul Hobson)
Date: Mon, 18 Mar 2019 13:18:42 -0700
Subject: [Numpy-discussion] [SPAM]Re: introducing Numpy.net,
 a pure C# implementation of Numpy
In-Reply-To: <CAB6mnxLFJ=CSzrCeOTp5DCgpsKB-mSsTTm8RXA5anCh61461hQ@mail.gmail.com>
References: <000701d4dbdf$9c7832e0$d56898a0$@baselinesw.com>
 <CAB6mnxJMPXM0E5eLyRYohkCW5bm29nA5eQS7w_2wNEMAdoJrug@mail.gmail.com>
 <CAB6mnxLiiQYFaxDStAkR-c2-MHdpHiq81MoCwiPqpj-5-+o8Bw@mail.gmail.com>
 <004701d4dc14$44981060$cdc83120$@baselinesw.com>
 <CAB6mnxLFJ=CSzrCeOTp5DCgpsKB-mSsTTm8RXA5anCh61461hQ@mail.gmail.com>
Message-ID: <CADT3MEAKC6Xf=Gm4=Aij8CDchyB0yxCpBs91JjBqWgDKMC89JA@mail.gmail.com>

Just reply to the discussion, I may have made a boo boo in replying to your
> first post.
>
> I'm curious. Implementing NumPy in another language seems like quite a bit
> of work. Did you have any tools to make it easier? I assume the C api is
> gone, so that the translation is NumPy program specific. I've never used
> C#, was there a reason to avoid C? What about IronPython? IIRC there was
> some work to make NumPy run on IronPython before that project was ended.
> I'm also curious what the application was that made it impossible to stay
> with python, I suppose the customer wanted C#, but I'd like to know why
> plain old Python was not an option.
>
>
Chuck,

To start: I'd like to be clear that I'm not trying to speak for the OP, but
I thought I'd share my experiences.

I'm a civil engineer who adopted Python early in his career and became the
"data guy" in the office pretty early on. Our company's IT department
manages lots of Windows Servers running SQL Server. In my case, running
python apps on our infrastructure just isn't feasible or supported by the
IT department. Typically, we move to outside hosting when we're going that
route. However, sometimes there are a litany of reasons to stay with our in
house infrastructure. In that case, C# makes it very simple to set up and
deploy a web API against a SQL Server database. It's very much a
walled-garden approach to the web, but it can be quite efficient,
especially when you're billing clients by the hour. Additionally, C#'s ORM
treats each table in the database pretty much as dataframe. I've ported
many of my pandas-based workflows over to C# without much issue.

For example in C# I did:

var results = StormEvent
.Where(se => new List<String> { "CI", "JI" }.Contains(se.MonitoringLocations
.sitename))
.Where(se => se.pCoseParameter.pName.ToLower().Contains("flow"))
.Where(se => se.wateryear_int.Equals(2014))
.GroupBy(
se => new {se.MonitoringLocations.sitename, se.paramName},
(key, df) => new
{
ml = key.sitename,
param = key.paramName
total = df.Select(d => d.paramValue).Sum()
}
);

Whereas in pandas I would do:

results = (
StormEvents
.merge(MonitoringLocations, on='monlocID', lsuffix='_ml', rsuffix='')
.merge(Parameters, on='paramID', lsuffix='_param', rsuffix='')
.loc[lambda x: x['sitename'].isin(['CI', 'CI'])]
.loc[lambda x: x['param'].str.lower().str.contains("flow")]
.loc[lambda x: x['wateryear_int'] == 2014]
.groupby(by=['sitename', 'paramID'])
.sum()['paramValue']
)

I'm not trying to sell you on C#, I'll always go python if I can. But
depending on your organization's infrastructure and project constraints, it
can be surprisingly pleasant to work with.

The point of all of this is that in those situations, have a numpy-like
library would be very nice indeed. I've very excited to hear that the OP's
work has been open sourced.

Kudos!
-Paul
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190318/694883ba/attachment.html>

From bussonniermatthias at gmail.com  Tue Mar 19 14:28:36 2019
From: bussonniermatthias at gmail.com (Matthias Bussonnier)
Date: Tue, 19 Mar 2019 11:28:36 -0700
Subject: [Numpy-discussion] BoF submission to SciPy 2019 open
Message-ID: <CANJQusXxqnFpymGb7bB6QwkR9T3R2jgiqzTzd-m592KNB_msLw@mail.gmail.com>

Hello NumPy developers,

The SciPy conference would like to encourage you to submit proposals for
Birds of a Feather (BoF) sessions at this year's SciPy! BoFs usually
include short presentations by a panel and a moderator with the bulk of the
time spent opening up the discussion to everyone in attendance, but the
format is flexible. BoF topics can be of general interest, such as
state-of-the-project BoFs, or based on the themes of the conference and the
mini-symposia topics, or can be a great opportunity to collect informations
from members of the SciPy community.

We would like to encourage you to think about topics of interest and submit
your proposals.
Submissions are open and will close on Friday, May 31st, 2019. You can
submit you proposal here: https://www.scipy2019.scipy.org/bof-sessions.

Last Year if my memory serves correctly we had Matti and Stefan for a "So
What's up with NumPy".

Past SciPy conferences have had a large variety of BoF sessions, including
topics on Reproducibility, Jupyter Notebooks, Distributed Computing,
Geospatial Packages in Python, Teaching Scientific Computing with Python,
Python and Finance, NumFOCUS, Python in Astronomy, Collaborating and
Contributing in Open Science, Education, and a Matplotlib Enhancement
Proposal Discussion. Generally, if there is a topic where you think a
number of people at SciPy will be interested, you should propose it! Please
share this with anyone else in the community who you think would be a good
candidate for organizing a BoF.

The BoF committee will try to select the BoFs based on a number of
criteria, and/or attempt to merge BoFs submissions with a large overlap.

Thanks in advance for your submission(s), and looking forward to see you at
SciPy 2019, Austin Texas, July 8-14, 2019. Feel free to contact us if you
have any questions, concerns or suggestions.
-- 
Lindsey Heagy and Matthias Bussonnier for the SciPy organizers.
scipybofs at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190319/0b63dcad/attachment.html>

From tyler.je.reddy at gmail.com  Tue Mar 19 21:24:06 2019
From: tyler.je.reddy at gmail.com (Tyler Reddy)
Date: Tue, 19 Mar 2019 18:24:06 -0700
Subject: [Numpy-discussion] BIDS / NumPy Community Meeting tomorrow (March
 20th)
Message-ID: <CAHPuU_YXrcE0FYMxq=LWyL2fEWLRXpZG8VtV2EB7J1GNBinBnw@mail.gmail.com>

Hi,

Just a reminder of the community meeting tomorrow at 12 pm Pacific time.
There's a section for community suggested topics in the work-in-progress
document that can be edited here:
https://hackmd.io/c_SRuI0GTNKBZHzsRX9wSw?view
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190319/c20d1d08/attachment.html>

From rishablamba407 at gmail.com  Wed Mar 20 06:20:50 2019
From: rishablamba407 at gmail.com (rishab lamba)
Date: Wed, 20 Mar 2019 15:50:50 +0530
Subject: [Numpy-discussion] Outreachy Program Aspirant
Message-ID: <CAC79Pm7_eiYur418CyUfnK2z=jU0EaaYgRddcs24yo8ZbFnLeg@mail.gmail.com>

Hi, I am Rishab Lamba undergoing my B.Tech from BVCOE, India. As an
applicant from Outreachy, I was going through this project
https://www.outreachy.org/may-2019-august-2019-outreachy-internships/communities/numpy/#improve-c-api-documentation-for-numpy
and would like to work on it. I was not aware of such a program and hence
cutting it really close to the deadline but I still hope if I can make
contributions as much as possible to the numpy repository. For this, any
guidance for submitting the PRs will be appreciated
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190320/460096a9/attachment.html>

From matti.picus at gmail.com  Wed Mar 20 07:59:38 2019
From: matti.picus at gmail.com (Matti Picus)
Date: Wed, 20 Mar 2019 13:59:38 +0200
Subject: [Numpy-discussion] Outreachy Program Aspirant
In-Reply-To: <CAC79Pm7_eiYur418CyUfnK2z=jU0EaaYgRddcs24yo8ZbFnLeg@mail.gmail.com>
References: <CAC79Pm7_eiYur418CyUfnK2z=jU0EaaYgRddcs24yo8ZbFnLeg@mail.gmail.com>
Message-ID: <eeb8f2f1-2ac5-1f17-389b-0e0a230fd4da@gmail.com>

On 20/3/19 12:20 pm, rishab lamba wrote:
>
> Hi, I am Rishab Lamba undergoing my B.Tech from BVCOE, India. As an 
> applicant from Outreachy, I was going through this project 
> https://www.outreachy.org/may-2019-august-2019-outreachy-internships/communities/numpy/#improve-c-api-documentation-for-numpy 
> and would like to work on it. I was not aware of such a program and 
> hence cutting it really close to the deadline but I still hope if I 
> can make contributions as much as possible to the numpy repository. 
> For this, any guidance for submitting the PRs will be appreciated
>
Hi and welcome.

The relevant issues have the DOC tag, you can see them via

https://github.com/numpy/numpy/issues?q=is%3Aissue+is%3Aopen+doc+label%3A%2204+-+Documentation%22 


Especially relevant are

https://github.com/numpy/numpy/issues/13013 which I think someone is 
already working on

https://github.com/numpy/numpy/pull/13104 which can be broken into a 
number of smaller PRs

https://github.com/numpy/numpy/issues/12632

https://github.com/numpy/numpy/issues/12385

and

https://github.com/numpy/numpy/pull/12097 which is a wip to add a 
version selector. This is not really connected with python or numpy, and 
is a pure javascript issue.


Our workflow is based on github, for an introduction see 
http://www.numpy.org/devdocs/dev/gitwash/development_workflow.html.

For instructions on building the documentation, which uses sphinx, see, 
http://www.numpy.org/devdocs/docs/index.html?highlight=documentation

Feel free to reach out to me directly with further questions.
Matti

From stefanv at berkeley.edu  Wed Mar 20 16:09:17 2019
From: stefanv at berkeley.edu (Stefan van der Walt)
Date: Wed, 20 Mar 2019 16:09:17 -0400
Subject: [Numpy-discussion] =?utf-8?q?prpp_report=E2=80=94please_help_rev?=
 =?utf-8?q?iew!?=
Message-ID: <97e5fe59-d99d-4ab2-982c-47afb54591a7@www.fastmail.com>

Hi everyone,

During the community call today, we drew up a list of open PR counts per developer. We are working towards bringing down their number (around 240 today), and would appreciate it if you could help us review and/or make decisions.

NumPy also has 1760 open issues <https://github.com/numpy/numpy/issues>; many of these are probably invalid?but just clicking through them all takes a lot of time. So if you want to grab 5 random ones and check their status, that would be very helpful.

Best regards,
St?fan
PR count

`1. eric-wieser: 32
2. jaimefrio: 10
3. juliantaylor: 6
4. madphysicist: 6
5. mattip: 5
6. bashtage: 4
7. tylerjereddy: 4
8. zerothi: 4
9. pitrou: 3
10. hameerabbasi: 3       
`
Eric?s PRs:

 * #12519: ENH/DEP: Use a ufunc under the hood for ndarray.clip <https://api.github.com/repos/numpy/numpy/pulls/12519>
 * #12473:  ENH: Make the contents of dtype.fields namedtuple-like <https://api.github.com/repos/numpy/numpy/pulls/12473>
 * #12205: MAINT: avoid relying on `np.generic.__name__` in `np.dtype.name` <https://api.github.com/repos/numpy/numpy/pulls/12205>
 * #12178: BUG: Prevent segfaults if python runs out of memory concatenating strings in ufunc error messages <https://api.github.com/repos/numpy/numpy/pulls/12178>
 * #11955: MAINT: Move _do_append and _do_prepend out of the functions to generate padding values <https://api.github.com/repos/numpy/numpy/pulls/11955>
 * #11829: MAINT: Use textwrap.dedent in f2py tests <https://api.github.com/repos/numpy/numpy/pulls/11829>
 * #11397: DEP: Deprecate the normed argument to histogramdd to match histogram <https://api.github.com/repos/numpy/numpy/pulls/11397>
 * #10765: BUG: Disable hex(np.floating) and oct(np.floating) on python 2 <https://api.github.com/repos/numpy/numpy/pulls/10765>
 * #10741: ENH: Implement `np.floating.as_integer_ratio` <https://api.github.com/repos/numpy/numpy/pulls/10741>
 * #10723: BUG: longdouble(int) does not work <https://api.github.com/repos/numpy/numpy/pulls/10723>
 * #10417: ENH: Allow dtype objects to be indexed with multiple fields at once <https://api.github.com/repos/numpy/numpy/pulls/10417>
 * #10308: API: Make MaskedArray.mask return a view, rather than the underlying mask <https://api.github.com/repos/numpy/numpy/pulls/10308>
 * #10151: BUG: Numpy scalar types sometimes have the same name <https://api.github.com/repos/numpy/numpy/pulls/10151>
 * #10132: BUG: np.matrix does not return an array when given a full index ending in ? <https://api.github.com/repos/numpy/numpy/pulls/10132>
 * #10025: ENH: Add the ndmin argument from np.array to np.as[any]array <https://api.github.com/repos/numpy/numpy/pulls/10025>
 * #9963: ENH: Add the C99 remainder function, as `np.remainder_ieee` <https://api.github.com/repos/numpy/numpy/pulls/9963>
 * #9951: ENH: Make dtype iterable <https://api.github.com/repos/numpy/numpy/pulls/9951>
 * #9705: BUG: Fix some (not all) compiler warnings <https://api.github.com/repos/numpy/numpy/pulls/9705>
 * #9690: BUG: Fix broken out argument in np.ma ufunc_likes <https://api.github.com/repos/numpy/numpy/pulls/9690>
 * #9459: MAINT: Remove unhelpful docstrings, improve helpful ones <https://api.github.com/repos/numpy/numpy/pulls/9459>
 * #9428: ENH: add a neigborwise function <https://api.github.com/repos/numpy/numpy/pulls/9428>
 * #9353: BUG: Fix np.ma.take on un-indexable scalars <https://api.github.com/repos/numpy/numpy/pulls/9353>
 * #8970: ENH/API: Change flexible types to indicate resizability with elsize == -1 <https://api.github.com/repos/numpy/numpy/pulls/8970>
 * #8910: ENH: avoid allocations in getmaskarray <https://api.github.com/repos/numpy/numpy/pulls/8910>
 * #8868: MAINT: Split ufunc into two subtypes, and remove methods where innapropriate <https://api.github.com/repos/numpy/numpy/pulls/8868>
 * #8853: BUG: Prevent power(uint64, int64) casting to float <https://api.github.com/repos/numpy/numpy/pulls/8853>
 * #8662: ENH: preserve subclasses in ufunc.outer <https://api.github.com/repos/numpy/numpy/pulls/8662>
 * #8641: BUG: Preserve types of empty arrays in ix_ when known <https://api.github.com/repos/numpy/numpy/pulls/8641>
 * #8640: ENH: generalize `ix_` to work for arbitrary dimensionality of input <https://api.github.com/repos/numpy/numpy/pulls/8640>
 * #8615: ENH: Add support for coercing structured arrays into dicts <https://api.github.com/repos/numpy/numpy/pulls/8615>
 * #8514: ENH: Make it possible to call .view on object arrays <https://api.github.com/repos/numpy/numpy/pulls/8514>
 * #8511: MAINT: make np.ma.apply_along_axis consistent with np.apply_along_axis <https://api.github.com/repos/numpy/numpy/pulls/8511>
Jaime?s PRs:

 * #9424: ENH: Adds an out argument to bincount. <https://api.github.com/repos/numpy/numpy/pulls/9424>
 * #7473: BUG: shift operator cycles, fixes #2449 <https://api.github.com/repos/numpy/numpy/pulls/7473>
 * #7464: ENH: Make bincount output same type as weights, fixes #6854 <https://api.github.com/repos/numpy/numpy/pulls/7464>
 * #7450: BUG, MAINT: concatenate of empty sequences, fixes #1586 <https://api.github.com/repos/numpy/numpy/pulls/7450>
 * #7441: MANT: refactor PyArrayMultiIterObject constructors <https://api.github.com/repos/numpy/numpy/pulls/7441>
 * #6219: MAINT: refactor unravel_index for code repetition <https://api.github.com/repos/numpy/numpy/pulls/6219>
 * #5890: BUG: Don?t use longlong for PyLong if it isn?t larger than long <https://api.github.com/repos/numpy/numpy/pulls/5890>
 * #5740: MAINT: Refactor .flags attribute of ndarray <https://api.github.com/repos/numpy/numpy/pulls/5740>
 * #4366: BUG: Allow any integer type in bincount (fixes #823) <https://api.github.com/repos/numpy/numpy/pulls/4366>
 * #4246: BUG: `take` casting logic with an `out=` argument <https://api.github.com/repos/numpy/numpy/pulls/4246>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190320/b0f3a5e9/attachment.html>

From ralf.gommers at gmail.com  Wed Mar 20 16:29:27 2019
From: ralf.gommers at gmail.com (Ralf Gommers)
Date: Wed, 20 Mar 2019 13:29:27 -0700
Subject: [Numpy-discussion] 
	=?utf-8?q?prpp_report=E2=80=94please_help_rev?= =?utf-8?q?iew!?=
In-Reply-To: <97e5fe59-d99d-4ab2-982c-47afb54591a7@www.fastmail.com>
References: <97e5fe59-d99d-4ab2-982c-47afb54591a7@www.fastmail.com>
Message-ID: <CABL7CQj0zb8sDga3QLYHL2yMACUhrzXkWjZboep-6dbUqWUang@mail.gmail.com>

On Wed, Mar 20, 2019 at 1:09 PM Stefan van der Walt <stefanv at berkeley.edu>
wrote:

> Hi everyone,
>
> During the community call today, we drew up a list of open PR counts per
> developer.  We are working towards bringing down their number (around 240
> today), and would appreciate it if you could help us review and/or make
> decisions.
>

All the links to PRs below are broken - if you have a script that's easy to
change, could you resend with fixed links?

Cheers,
Ralf



> NumPy also has 1760 open issues <https://github.com/numpy/numpy/issues>;
> many of these are probably invalid?but just clicking through them all takes
> a lot of time.  So if you want to grab 5 random ones and check their
> status, that would be very helpful.
>
> Best regards,
> St?fan
> PR count
>
> 1. eric-wieser: 32
> 2. jaimefrio: 10
> 3. juliantaylor: 6
> 4. madphysicist: 6
> 5. mattip: 5
> 6. bashtage: 4
> 7. tylerjereddy: 4
> 8. zerothi: 4
> 9. pitrou: 3
> 10. hameerabbasi: 3
>
> Eric?s PRs:
>
>    - #12519: ENH/DEP: Use a ufunc under the hood for ndarray.clip
>    <https://api.github.com/repos/numpy/numpy/pulls/12519>
>    - #12473: ENH: Make the contents of dtype.fields namedtuple-like
>    <https://api.github.com/repos/numpy/numpy/pulls/12473>
>    - #12205: MAINT: avoid relying on np.generic.__name__ in np.dtype.name
>    <https://api.github.com/repos/numpy/numpy/pulls/12205>
>    - #12178: BUG: Prevent segfaults if python runs out of memory
>    concatenating strings in ufunc error messages
>    <https://api.github.com/repos/numpy/numpy/pulls/12178>
>    - #11955: MAINT: Move _do_append and _do_prepend out of the functions
>    to generate padding values
>    <https://api.github.com/repos/numpy/numpy/pulls/11955>
>    - #11829: MAINT: Use textwrap.dedent in f2py tests
>    <https://api.github.com/repos/numpy/numpy/pulls/11829>
>    - #11397: DEP: Deprecate the normed argument to histogramdd to match
>    histogram <https://api.github.com/repos/numpy/numpy/pulls/11397>
>    - #10765: BUG: Disable hex(np.floating) and oct(np.floating) on python
>    2 <https://api.github.com/repos/numpy/numpy/pulls/10765>
>    - #10741: ENH: Implement np.floating.as_integer_ratio
>    <https://api.github.com/repos/numpy/numpy/pulls/10741>
>    - #10723: BUG: longdouble(int) does not work
>    <https://api.github.com/repos/numpy/numpy/pulls/10723>
>    - #10417: ENH: Allow dtype objects to be indexed with multiple fields
>    at once <https://api.github.com/repos/numpy/numpy/pulls/10417>
>    - #10308: API: Make MaskedArray.mask return a view, rather than the
>    underlying mask <https://api.github.com/repos/numpy/numpy/pulls/10308>
>    - #10151: BUG: Numpy scalar types sometimes have the same name
>    <https://api.github.com/repos/numpy/numpy/pulls/10151>
>    - #10132: BUG: np.matrix does not return an array when given a full
>    index ending in ?
>    <https://api.github.com/repos/numpy/numpy/pulls/10132>
>    - #10025: ENH: Add the ndmin argument from np.array to np.as[any]array
>    <https://api.github.com/repos/numpy/numpy/pulls/10025>
>    - #9963: ENH: Add the C99 remainder function, as np.remainder_ieee
>    <https://api.github.com/repos/numpy/numpy/pulls/9963>
>    - #9951: ENH: Make dtype iterable
>    <https://api.github.com/repos/numpy/numpy/pulls/9951>
>    - #9705: BUG: Fix some (not all) compiler warnings
>    <https://api.github.com/repos/numpy/numpy/pulls/9705>
>    - #9690: BUG: Fix broken out argument in np.ma ufunc_likes
>    <https://api.github.com/repos/numpy/numpy/pulls/9690>
>    - #9459: MAINT: Remove unhelpful docstrings, improve helpful ones
>    <https://api.github.com/repos/numpy/numpy/pulls/9459>
>    - #9428: ENH: add a neigborwise function
>    <https://api.github.com/repos/numpy/numpy/pulls/9428>
>    - #9353: BUG: Fix np.ma.take on un-indexable scalars
>    <https://api.github.com/repos/numpy/numpy/pulls/9353>
>    - #8970: ENH/API: Change flexible types to indicate resizability with
>    elsize == -1 <https://api.github.com/repos/numpy/numpy/pulls/8970>
>    - #8910: ENH: avoid allocations in getmaskarray
>    <https://api.github.com/repos/numpy/numpy/pulls/8910>
>    - #8868: MAINT: Split ufunc into two subtypes, and remove methods
>    where innapropriate
>    <https://api.github.com/repos/numpy/numpy/pulls/8868>
>    - #8853: BUG: Prevent power(uint64, int64) casting to float
>    <https://api.github.com/repos/numpy/numpy/pulls/8853>
>    - #8662: ENH: preserve subclasses in ufunc.outer
>    <https://api.github.com/repos/numpy/numpy/pulls/8662>
>    - #8641: BUG: Preserve types of empty arrays in ix_ when known
>    <https://api.github.com/repos/numpy/numpy/pulls/8641>
>    - #8640: ENH: generalize ix_ to work for arbitrary dimensionality of
>    input <https://api.github.com/repos/numpy/numpy/pulls/8640>
>    - #8615: ENH: Add support for coercing structured arrays into dicts
>    <https://api.github.com/repos/numpy/numpy/pulls/8615>
>    - #8514: ENH: Make it possible to call .view on object arrays
>    <https://api.github.com/repos/numpy/numpy/pulls/8514>
>    - #8511: MAINT: make np.ma.apply_along_axis consistent with
>    np.apply_along_axis
>    <https://api.github.com/repos/numpy/numpy/pulls/8511>
>
> Jaime?s PRs:
>
>    - #9424: ENH: Adds an out argument to bincount.
>    <https://api.github.com/repos/numpy/numpy/pulls/9424>
>    - #7473: BUG: shift operator cycles, fixes #2449
>    <https://api.github.com/repos/numpy/numpy/pulls/7473>
>    - #7464: ENH: Make bincount output same type as weights, fixes #6854
>    <https://api.github.com/repos/numpy/numpy/pulls/7464>
>    - #7450: BUG, MAINT: concatenate of empty sequences, fixes #1586
>    <https://api.github.com/repos/numpy/numpy/pulls/7450>
>    - #7441: MANT: refactor PyArrayMultiIterObject constructors
>    <https://api.github.com/repos/numpy/numpy/pulls/7441>
>    - #6219: MAINT: refactor unravel_index for code repetition
>    <https://api.github.com/repos/numpy/numpy/pulls/6219>
>    - #5890: BUG: Don?t use longlong for PyLong if it isn?t larger than
>    long <https://api.github.com/repos/numpy/numpy/pulls/5890>
>    - #5740: MAINT: Refactor .flags attribute of ndarray
>    <https://api.github.com/repos/numpy/numpy/pulls/5740>
>    - #4366: BUG: Allow any integer type in bincount (fixes #823)
>    <https://api.github.com/repos/numpy/numpy/pulls/4366>
>    - #4246: BUG: take casting logic with an out= argument
>    <https://api.github.com/repos/numpy/numpy/pulls/4246>
>
>
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190320/259d76e9/attachment-0001.html>

From stefanv at berkeley.edu  Wed Mar 20 17:15:23 2019
From: stefanv at berkeley.edu (Stefan van der Walt)
Date: Wed, 20 Mar 2019 17:15:23 -0400
Subject: [Numpy-discussion] 
 =?utf-8?q?prpp_report=E2=80=94please_help_rev?= =?utf-8?q?iew!?=
In-Reply-To: <CABL7CQj0zb8sDga3QLYHL2yMACUhrzXkWjZboep-6dbUqWUang@mail.gmail.com>
References: <97e5fe59-d99d-4ab2-982c-47afb54591a7@www.fastmail.com>
 <CABL7CQj0zb8sDga3QLYHL2yMACUhrzXkWjZboep-6dbUqWUang@mail.gmail.com>
Message-ID: <f198e025-0aee-4d43-bb82-e2893964f63f@www.fastmail.com>

On Wed, Mar 20, 2019, at 13:30, Ralf Gommers wrote:
> All the links to PRs below are broken - if you have a script that's easy to change, could you resend with fixed links?

Sorry, looks like I posted the API endpoints. Here's a working version, including everyone with >= 5 PRs:

*Top 10 PR contributors:*

 1. eric-wieser: 32
 2. jaimefrio: 10
 3. juliantaylor: 6
 4. madphysicist: 6
 5. mattip: 5
 6. bashtage: 4
 7. tylerjereddy: 4
 8. zerothi: 4
 9. pitrou: 3
 10. hameerabbasi: 3
*PRs for eric-wieser:*

 * #12519: ENH/DEP: Use a ufunc under the hood for ndarray.clip <https://github.com/numpy/numpy/pull/12519>
 * #12473:  ENH: Make the contents of dtype.fields namedtuple-like <https://github.com/numpy/numpy/pull/12473>
 * #12467: WIP: Make type(np.generic) != type <https://github.com/numpy/numpy/pull/12467>
 * #12205: MAINT: avoid relying on `np.generic.__name__` in `np.dtype.name` <https://github.com/numpy/numpy/pull/12205>
 * #12178: BUG: Prevent segfaults if python runs out of memory concatenating strings in ufunc error messages <https://github.com/numpy/numpy/pull/12178>
 * #11955: MAINT: Move _do_append and _do_prepend out of the functions to generate padding values <https://github.com/numpy/numpy/pull/11955>
 * #11924: WIP/NEP: Making details of `np.core` private <https://github.com/numpy/numpy/pull/11924>
 * #11829: MAINT: Use textwrap.dedent in f2py tests <https://github.com/numpy/numpy/pull/11829>
 * #11397: DEP: Deprecate the normed argument to histogramdd to match histogram <https://github.com/numpy/numpy/pull/11397>
 * #10765: BUG: Disable hex(np.floating) and oct(np.floating) on python 2 <https://github.com/numpy/numpy/pull/10765>
 * #10741: ENH: Implement `np.floating.as_integer_ratio` <https://github.com/numpy/numpy/pull/10741>
 * #10723: BUG: longdouble(int) does not work <https://github.com/numpy/numpy/pull/10723>
 * #10417: ENH: Allow dtype objects to be indexed with multiple fields at once <https://github.com/numpy/numpy/pull/10417>
 * #10308: API: Make MaskedArray.mask return a view, rather than the underlying mask <https://github.com/numpy/numpy/pull/10308>
 * #10151: BUG: Numpy scalar types sometimes have the same name <https://github.com/numpy/numpy/pull/10151>
 * #10132: BUG: np.matrix does not return an array when given a full index ending in ? <https://github.com/numpy/numpy/pull/10132>
 * #10025: ENH: Add the ndmin argument from np.array to np.as[any]array <https://github.com/numpy/numpy/pull/10025>
 * #9963: ENH: Add the C99 remainder function, as `np.remainder_ieee` <https://github.com/numpy/numpy/pull/9963>
 * #9951: ENH: Make dtype iterable <https://github.com/numpy/numpy/pull/9951>
 * #9877: WIP: Make str ? bool conversion consistent <https://github.com/numpy/numpy/pull/9877>
 * #9705: BUG: Fix some (not all) compiler warnings <https://github.com/numpy/numpy/pull/9705>
 * #9690: BUG: Fix broken out argument in np.ma ufunc_likes <https://github.com/numpy/numpy/pull/9690>
 * #9459: MAINT: Remove unhelpful docstrings, improve helpful ones <https://github.com/numpy/numpy/pull/9459>
 * #9428: ENH: add a neigborwise function <https://github.com/numpy/numpy/pull/9428>
 * #9353: BUG: Fix np.ma.take on un-indexable scalars <https://github.com/numpy/numpy/pull/9353>
 * #8970: ENH/API: Change flexible types to indicate resizability with elsize == -1 <https://github.com/numpy/numpy/pull/8970>
 * #8910: ENH: avoid allocations in getmaskarray <https://github.com/numpy/numpy/pull/8910>
 * #8868: MAINT: Split ufunc into two subtypes, and remove methods where innapropriate <https://github.com/numpy/numpy/pull/8868>
 * #8853: BUG: Prevent power(uint64, int64) casting to float <https://github.com/numpy/numpy/pull/8853>
 * #8662: ENH: preserve subclasses in ufunc.outer <https://github.com/numpy/numpy/pull/8662>
 * #8641: BUG: Preserve types of empty arrays in ix_ when known <https://github.com/numpy/numpy/pull/8641>
 * #8640: ENH: generalize `ix_` to work for arbitrary dimensionality of input <https://github.com/numpy/numpy/pull/8640>
 * #8615: ENH: Add support for coercing structured arrays into dicts <https://github.com/numpy/numpy/pull/8615>
 * #8514: ENH: Make it possible to call .view on object arrays <https://github.com/numpy/numpy/pull/8514>
 * #8511: MAINT: make np.ma.apply_along_axis consistent with np.apply_along_axis <https://github.com/numpy/numpy/pull/8511>
*PRs for jaimefrio:*

 * #9424: ENH: Adds an out argument to bincount. <https://github.com/numpy/numpy/pull/9424>
 * #7473: BUG: shift operator cycles, fixes #2449 <https://github.com/numpy/numpy/pull/7473>
 * #7464: ENH: Make bincount output same type as weights, fixes #6854 <https://github.com/numpy/numpy/pull/7464>
 * #7450: BUG, MAINT: concatenate of empty sequences, fixes #1586 <https://github.com/numpy/numpy/pull/7450>
 * #7441: MANT: refactor PyArrayMultiIterObject constructors <https://github.com/numpy/numpy/pull/7441>
 * #6219: MAINT: refactor unravel_index for code repetition <https://github.com/numpy/numpy/pull/6219>
 * #5890: BUG: Don?t use longlong for PyLong if it isn?t larger than long <https://github.com/numpy/numpy/pull/5890>
 * #5740: MAINT: Refactor .flags attribute of ndarray <https://github.com/numpy/numpy/pull/5740>
 * #5508: WIP: make views of different type checks less strict <https://github.com/numpy/numpy/pull/5508>
 * #5487: WIP: handling of nan in unique, fixes #2111 <https://github.com/numpy/numpy/pull/5487>
 * #4366: BUG: Allow any integer type in bincount (fixes #823) <https://github.com/numpy/numpy/pull/4366>
 * #4246: BUG: `take` casting logic with an `out=` argument <https://github.com/numpy/numpy/pull/4246>
*PRs for juliantaylor:*

 * #11113: AVX for floats? <https://github.com/numpy/numpy/pull/11113>
 * #9163: BUG: use data malloc for transfer function data <https://github.com/numpy/numpy/pull/9163>
 * #8924: ENH: add scalar special cases for boolean logical loops <https://github.com/numpy/numpy/pull/8924>
 * #8856: MAINT: remove duplicated integer code <https://github.com/numpy/numpy/pull/8856>
 * #8783: ENH: cache large memory allocations on systems with MADV_FREE <https://github.com/numpy/numpy/pull/8783>
 * #7865: WIP: use openmp vector function ABI for sin, cos, exp and log <https://github.com/numpy/numpy/pull/7865>
 * #4904: more small-array performance improvements <https://github.com/numpy/numpy/pull/4904>
*PRs for madphysicist:*

 * #12829: ENH: Added option to suppress stout/err capture in tests <https://github.com/numpy/numpy/pull/12829>
 * #12828: DOC: Updates to nditer usage instructions <https://github.com/numpy/numpy/pull/12828>
 * #10820: ENH: Added support for arrays with `dtype=object` to `np.isinf`, `np.isnan`, `np.isfinite` <https://github.com/numpy/numpy/pull/10820>
 * #9514: ENH: Adding np.neighborwise function <https://github.com/numpy/numpy/pull/9514>
 * #7804: ENH: Added atleast_nd <https://github.com/numpy/numpy/pull/7804>
 * #7322: ENH: Added optional `scale` parameter to `sinc` to enable non-normali? <https://github.com/numpy/numpy/pull/7322>
*PRs for mattip:*

 * #13163: WIP, ENH: randomgen <https://github.com/numpy/numpy/pull/13163>
 * #13005: MAINT: remove warning for pre-1.9 numpy <https://github.com/numpy/numpy/pull/13005>
 * #12962: ENH: Add ?order? keyword to packbits, unpackbits <https://github.com/numpy/numpy/pull/12962>
 * #12714: WIP, ENH: extend np.vectorize for flexible NEP20 signatures <https://github.com/numpy/numpy/pull/12714>
 * #12660: WIP, NEP: add dtype design NEP - DtypeMeta, Dtype, and hierarchy <https://github.com/numpy/numpy/pull/12660>
 * #12630: WIP, NEP: add dtype design NEP <https://github.com/numpy/numpy/pull/12630>
 * #12619: WIP, NEP: draft dtype ufunc NEP <https://github.com/numpy/numpy/pull/12619>
 * #12609: DEP: issue warning when creating 0-stride broadcasted arrays <https://github.com/numpy/numpy/pull/12609>
 * #12594: WIP, DEV: add pypy3 to azure CI <https://github.com/numpy/numpy/pull/12594>
 * #12585: WIP: refactor dtype to be a type subclass <https://github.com/numpy/numpy/pull/12585>
 * #12428: ENH: always use zip64, upgrade pickle protocol to 3 <https://github.com/numpy/numpy/pull/12428>
 * #12284: WIP: ENH: supply our version of numpy.pxd, requires cython>=0.29 <https://github.com/numpy/numpy/pull/12284>
 * #11684: BUG: Raise when unravel_index, ravel_multi_index are given empty input <https://github.com/numpy/numpy/pull/11684>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190320/db3ffe10/attachment-0001.html>

From matti.picus at gmail.com  Thu Mar 21 09:08:49 2019
From: matti.picus at gmail.com (Matti Picus)
Date: Thu, 21 Mar 2019 15:08:49 +0200
Subject: [Numpy-discussion] 
 =?utf-8?q?prpp_report=E2=80=94please_help_rev?= =?utf-8?q?iew!?=
In-Reply-To: <97e5fe59-d99d-4ab2-982c-47afb54591a7@www.fastmail.com>
References: <97e5fe59-d99d-4ab2-982c-47afb54591a7@www.fastmail.com>
Message-ID: <2a5d48a6-67b3-3ad7-693f-20967a0fe84c@gmail.com>


On 20/3/19 10:09 pm, Stefan van der Walt wrote:
> Hi everyone,
>
> During the community call today, we drew up a list of open PR counts 
> per developer.? We are working towards bringing down their number 
> (around 240 today), and would appreciate it if you could help us 
> review and/or make decisions.
>
> NumPy also has 1760 open issues 
> <https://github.com/numpy/numpy/issues>; many of these are probably 
> invalid?but just clicking through them all takes a lot of time.? So if 
> you want to grab 5 random ones and check their status, that would be 
> very helpful.
>
> Best regards,
> St?fan
>

One thing that might help is if we could work through the 12 PRs that 
have a "Needs Decision" label 
https://github.com/numpy/numpy/pulls?q=is%3Aopen+is%3Apr+label%3A%2254+-+Needs+decision%22. 
These are waiting for someone to say Yay or Nay.


Matti


From brindaken95 at gmail.com  Fri Mar 22 21:08:13 2019
From: brindaken95 at gmail.com (Brinda)
Date: Sat, 23 Mar 2019 02:08:13 +0100
Subject: [Numpy-discussion] Introducing myself
Message-ID: <CAGtdFxa8XnnabqoJemsQUofznrPHX-931yF0pd3mZ7bzbmg_AA@mail.gmail.com>

Hello, I am called Malika.
My outreachy initial application has been recently approved. I am new to
this community and I'm really eager to work on this project.
Please I wish someone explains to me how to get started.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190323/41003420/attachment.html>

From sebastian at sipsolutions.net  Sat Mar 23 10:43:43 2019
From: sebastian at sipsolutions.net (Sebastian Berg)
Date: Sat, 23 Mar 2019 15:43:43 +0100
Subject: [Numpy-discussion] Introducing myself
In-Reply-To: <CAGtdFxa8XnnabqoJemsQUofznrPHX-931yF0pd3mZ7bzbmg_AA@mail.gmail.com>
References: <CAGtdFxa8XnnabqoJemsQUofznrPHX-931yF0pd3mZ7bzbmg_AA@mail.gmail.com>
Message-ID: <66774aaa30a188729a1d8e2763f0b843199766f6.camel@sipsolutions.net>

Hello Malika and welcome,

On Sat, 2019-03-23 at 02:08 +0100, Brinda wrote:
> Hello, I am called Malika. 
> My outreachy initial application has been recently approved. I am new
> to this community and I'm really eager to work on this project. 
> Please I wish someone explains to me how to get started. 


To get you started it would be great if you can try to work on an issue
in numpy and create a pull request (PR) to fix it. That way we can get
to know you a bit and you get to know numpy and our workflow.
The most relevant ones are those that have the documentation tag/label,
you can see them via:

https://github.com/numpy/numpy/issues?q=is%3Aissue+is%3Aopen+doc+label%3A%2204+-+Documentation%22

Some relevant issues (note some of these may already have someone
interested in them):

https://github.com/numpy/numpy/issues/13013 which probably someone is
already working on

https://github.com/numpy/numpy/issues/13114 which can be broken into a 
number of smaller PRs

https://github.com/numpy/numpy/issues/12632

https://github.com/numpy/numpy/issues/12385

and

https://github.com/numpy/numpy/pull/12097 which is a wip to add a 
version selector. This is not really connected with python or numpy,
and is a pure javascript issue.

Our workflow is based on github, for an introduction see 
http://www.numpy.org/devdocs/dev/gitwash/development_workflow.html. 

For instructions on building the documentation, which uses sphinx, see,
http://www.numpy.org/devdocs/docs/index.html?highlight=documentation 

I hope you can find something to get you started.

Try to work through the process and reach out when you get stuck with
specific questions: "I tried X, expected Y, but got Z".

Feel free to reach out to Matti or me directly if you have any
questions. The issues themselves are also a good place to ask if you
wish to work on one.

Best Regards,

Sebastian




> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190323/47cdb391/attachment.sig>

From vrinda18120 at iiitd.ac.in  Mon Mar 25 10:08:40 2019
From: vrinda18120 at iiitd.ac.in (Vrinda Narayan)
Date: Mon, 25 Mar 2019 19:38:40 +0530
Subject: [Numpy-discussion] Introducing Myself
Message-ID: <CAGHOg1Vnua+j+000rTLrN9vnL-1xF+RyFTEyzZonjjo1ZKmwTg@mail.gmail.com>

Heyy,
My name is Vrinda Narayan and I'm an Outreachy Applicant. I'm a CSE
undergraduate and I know python, C, JavaScript and git. I am interested in
contributing to the Numpy project Improve C API documentation for Numpy.
I have used Numpy for various projects in my college and I really look
forward to working with Numpy and contributing more to this community.
Warm regards
Vrinda Narayan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190325/8bc1a07d/attachment.html>

From matti.picus at gmail.com  Mon Mar 25 10:15:49 2019
From: matti.picus at gmail.com (Matti Picus)
Date: Mon, 25 Mar 2019 16:15:49 +0200
Subject: [Numpy-discussion] Introducing Myself
In-Reply-To: <CAGHOg1Vnua+j+000rTLrN9vnL-1xF+RyFTEyzZonjjo1ZKmwTg@mail.gmail.com>
References: <CAGHOg1Vnua+j+000rTLrN9vnL-1xF+RyFTEyzZonjjo1ZKmwTg@mail.gmail.com>
Message-ID: <50f10c43-f688-3023-0e08-a67f78cf0b46@gmail.com>

On 25/3/19 4:08 pm, Vrinda Narayan wrote:
> Heyy,
> My name is Vrinda Narayan and I'm an Outreachy Applicant. I'm a CSE 
> undergraduate and I know python, C, JavaScript and git. I am 
> interested in contributing to the Numpy project Improve C API 
> documentation for Numpy.
> I have used Numpy for various projects in my college and I really look 
> forward to working with Numpy and contributing more to this community.
> Warm?regards
> Vrinda Narayan
>

Hi Vrinda Narayan


To get you started it would be great if you can try to work on an issue
in numpy and create a pull request (PR) to fix it. That way we can get
to know you a bit and you get to know numpy and our workflow.

New contributors might find it easiest to work on the documentation tag/label,
you can see them via:
https://github.com/numpy/numpy/issues?q=is%3Aissue+is%3Aopen+doc+label%3A%2204+-+Documentation%22

Some relevant issues (note some of these may already have someone
interested in them):

https://github.com/numpy/numpy/issues/13013  which probably someone
is already working on

https://github.com/numpy/numpy/issues/13114  which can be broken into a
number of smaller PRs

https://github.com/numpy/numpy/issues/12632

https://github.com/numpy/numpy/issues/12385

and

https://github.com/numpy/numpy/pull/12097  which is a wip to add a
version selector. This is not really connected with python or numpy,
and is a pure javascript issue.

Our workflow is based on github, for an introduction see
http://www.numpy.org/devdocs/dev/gitwash/development_workflow.html.

For instructions on building the documentation, which uses sphinx, see,
http://www.numpy.org/devdocs/docs/index.html?highlight=documentation  

I hope you can find something to get you started.

Try to work through the process and reach out when you get stuck with
specific questions: "I tried X, expected Y, but got Z".

Feel free to reach out to Sebastian Berg (cc`ed on this mail) or me directly if you have any
questions. The issues themselves are also a good place to ask if you
wish to work on one.

Best Regards,
Matti


From cimrman3 at ntc.zcu.cz  Tue Mar 26 09:41:14 2019
From: cimrman3 at ntc.zcu.cz (Robert Cimrman)
Date: Tue, 26 Mar 2019 14:41:14 +0100
Subject: [Numpy-discussion] ANN: SfePy 2019.1
Message-ID: <8c391e1e-5cc6-dbb6-864a-65e49d5874cf@ntc.zcu.cz>

I am pleased to announce release 2019.1 of SfePy.

Description
-----------

SfePy (simple finite elements in Python) is a software for solving systems of
coupled partial differential equations by the finite element method or by the
isogeometric analysis (limited support). It is distributed under the new BSD
license.

Home page: http://sfepy.org
Mailing list: https://mail.python.org/mm3/mailman3/lists/sfepy.python.org/
Git (source) repository, issue tracker: https://github.com/sfepy/sfepy

Highlights of this release
--------------------------

- automatic fallback for linear solvers
- quadratic eigenvalue problem solver

For full release notes see [1].

Cheers,
Robert Cimrman

[1] http://docs.sfepy.org/doc/release_notes.html#id1

---

Contributors to this release in alphabetical order:

Robert Cimrman
Lubos Kejzlar
Vladimir Lukes

From giuseppe at cs.columbia.edu  Tue Mar 26 15:02:06 2019
From: giuseppe at cs.columbia.edu (Giuseppe Di Guglielmo)
Date: Tue, 26 Mar 2019 15:02:06 -0400
Subject: [Numpy-discussion] SWIG typemap (numpy.i)
Message-ID: <CAD1r979Kcst+1QoLgZh3sBSvRk34j3quFz9wxgzkL34hoHXFww@mail.gmail.com>

What is the right SWIG typemap for the following function?

void filter(int height, int width, unsigned int *input_array_2d, unsigned
int *input_array_2d);

The input and output arrays are bi-dimensional. The input array is
read-only and the output array is write-only. I tried something like:

%apply (int DIM1, int DIM2, int* INPLACE_ARRAY2) {(int height, int width,
int* input_array_2d), (int height, int width, int* input_array_2d)};

But it does not seem to be correct.

Thank you!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190326/090cb4da/attachment.html>

From tyler.je.reddy at gmail.com  Tue Mar 26 17:47:12 2019
From: tyler.je.reddy at gmail.com (Tyler Reddy)
Date: Tue, 26 Mar 2019 14:47:12 -0700
Subject: [Numpy-discussion] NumPy - BIDS / community meeting March 27
Message-ID: <CAHPuU_bcfxJvJO=noUKXRna8=tg-ZN=EPOO_6dMFvsxn7XY=Ng@mail.gmail.com>

Hi,

A reminder of the weekly call tomorrow (March 27) at 12 pm Pacific Time,
with work in progress meeting notes here:
https://hackmd.io/kPZJ6E4aTa-27fsEsgY2Sw?view

There's a section for community-suggested topics.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190326/25d3a0aa/attachment.html>

From supriyakotturu at gmail.com  Wed Mar 27 05:35:37 2019
From: supriyakotturu at gmail.com (Kotturu Supriya)
Date: Wed, 27 Mar 2019 15:05:37 +0530
Subject: [Numpy-discussion] Outreachy applicant
Message-ID: <CADYYBX5wn2wO4=CWO6Nn1J+GqwEXZwCCPFSGa1ESCr5g0vCP2g@mail.gmail.com>

Hello,

I am Supriya, an Outreachy applicant. I am interested in contributing to
this project. Please let me know how to proceed and any suggestions on my
first contribution would be greatly appreciated.


Regards,
Sai Supriya.


-------------------------------------------------------------
Sai Supriya Kotturu
"Life isn?t about finding yourself. Life is about creating yourself." -
George Bernard Shaw
NMREC, Hyderabad- 500018  |  7702879899  |
supriyakotturu at protonmail.com |  supriyakotturu at gmail.com |
https://www.linkedin.com/in/supriya-kotturu |
https://supriya-kotturu.gitlab.io/Portfolio |
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190327/69614a23/attachment.html>

From arpitadash1998 at gmail.com  Wed Mar 27 11:14:02 2019
From: arpitadash1998 at gmail.com (Arpita Dash)
Date: Wed, 27 Mar 2019 20:44:02 +0530
Subject: [Numpy-discussion] My introduction to NumPy community
Message-ID: <CAMOvDGWGQ2UUcOYSd_=Xp_zeB1EoCDjShcbtedc1rvpMoT6gSA@mail.gmail.com>

Hello,
My name is Arpita Dash and I'm an Outreachy Applicant. I'm a CSE
undergraduate. I am interested in contributing to the Numpy project
"Improve C API documentation for Numpy."
I am looking forward to working with Numpy and contributing to the community.

Regards,

Arpita Dash
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190327/e9d292f4/attachment.html>

From matti.picus at gmail.com  Wed Mar 27 11:27:49 2019
From: matti.picus at gmail.com (Matti Picus)
Date: Wed, 27 Mar 2019 17:27:49 +0200
Subject: [Numpy-discussion] My introduction to NumPy community
In-Reply-To: <CAMOvDGWGQ2UUcOYSd_=Xp_zeB1EoCDjShcbtedc1rvpMoT6gSA@mail.gmail.com>
References: <CAMOvDGWGQ2UUcOYSd_=Xp_zeB1EoCDjShcbtedc1rvpMoT6gSA@mail.gmail.com>
Message-ID: <118a1c82-af39-4e45-6f7e-19657aaab1ad@gmail.com>


On 27/3/19 5:14 pm, Arpita Dash wrote:
> Hello,
> My name is Arpita Dash and I'm an Outreachy Applicant. I'm a CSE
> undergraduate. I am interested in contributing to the Numpy project "Improve C API documentation for Numpy."
> I am looking forward to working with Numpy and contributing to the community.
>
> Regards,
> Arpita Dash
>

On 27/3/19 11:35 am, Kotturu Supriya wrote:
> Hello,
>
> I am?Supriya, an Outreachy applicant. I am?interested?in contributing 
> to this project. Please let me know how to?proceed and any suggestions 
> on my first contribution would?be greatly appreciated.
>
>
> Regards,
> Sai Supriya.


Welcome to you both.


To get you started it would be great if you can try to work on an issue 
in numpy and create a pull request (PR) to fix it. That way we can get 
to know you a bit and you get to know numpy and our workflow.

New contributors might find it easiest to work on the documentation tag/label,
you can see them via:

https://github.com/numpy/numpy/issues?q=is%3Aissue+is%3Aopen+doc+label%3A%2204+-+Documentation%22

Some relevant issues (note some of these may already have someone
interested in them):

https://github.com/numpy/numpy/issues/13013  which probably someone
is already working on

https://github.com/numpy/numpy/issues/13114  which can be broken into a
number of smaller PRs

https://github.com/numpy/numpy/issues/12632

https://github.com/numpy/numpy/issues/12385

and

https://github.com/numpy/numpy/pull/12097  which is a wip to add a
version selector. This is a pure javascript issue.

Our workflow is based on github, for an introduction see
http://www.numpy.org/devdocs/dev/gitwash/development_workflow.html.

For instructions on building the documentation, which uses sphinx, see,
http://www.numpy.org/devdocs/docs/index.html?highlight=documentation  

I hope you can find something to get you started.

Try to work through the process and reach out when you get stuck with
specific questions: "I tried X, expected Y, but got Z".

Feel free to reach out to me directly if you have any
questions. The issues themselves are also a good place to ask for specific guidance.

Best Regards,
Matti


From chris.barker at noaa.gov  Wed Mar 27 13:29:22 2019
From: chris.barker at noaa.gov (Chris Barker)
Date: Wed, 27 Mar 2019 10:29:22 -0700
Subject: [Numpy-discussion] [SPAM]Re: introducing Numpy.net,
 a pure C# implementation of Numpy
In-Reply-To: <CADT3MEAKC6Xf=Gm4=Aij8CDchyB0yxCpBs91JjBqWgDKMC89JA@mail.gmail.com>
References: <000701d4dbdf$9c7832e0$d56898a0$@baselinesw.com>
 <CAB6mnxJMPXM0E5eLyRYohkCW5bm29nA5eQS7w_2wNEMAdoJrug@mail.gmail.com>
 <CAB6mnxLiiQYFaxDStAkR-c2-MHdpHiq81MoCwiPqpj-5-+o8Bw@mail.gmail.com>
 <004701d4dc14$44981060$cdc83120$@baselinesw.com>
 <CAB6mnxLFJ=CSzrCeOTp5DCgpsKB-mSsTTm8RXA5anCh61461hQ@mail.gmail.com>
 <CADT3MEAKC6Xf=Gm4=Aij8CDchyB0yxCpBs91JjBqWgDKMC89JA@mail.gmail.com>
Message-ID: <CALGmxEJ=9F3s3M8yp416kW5+JOOTtbW3V-4wDFC8nQ6rHeMACA@mail.gmail.com>

On Mon, Mar 18, 2019 at 1:19 PM Paul Hobson <pmhobson at gmail.com> wrote:

>
>> I'm a civil engineer who adopted Python early in his career and became
> the "data guy" in the office pretty early on. Our company's IT department
> manages lots of Windows Servers running SQL Server. In my case, running
> python apps on our infrastructure just isn't feasible or supported by the
> IT department.
>

Just curious -- does it have to be C#? or could it be any CLR application
-- i.e. IronPython?

I imagine you could build a web service pretty easily in IronPython --
though AFAIK, the attempts at getting numpy support (and thus Pandas, etc)
never panned out.

The point of all of this is that in those situations, have a numpy-like
> library would be very nice indeed. I've very excited to hear that the OP's
> work has been open sourced.
>

I wonder if the OP's work could be used to make a numpy for Iron Python
native to the CLR ....

-CHB

-- 

Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chris.Barker at noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190327/21599f1a/attachment.html>

From pmhobson at gmail.com  Wed Mar 27 16:21:11 2019
From: pmhobson at gmail.com (Paul Hobson)
Date: Wed, 27 Mar 2019 13:21:11 -0700
Subject: [Numpy-discussion] [SPAM]Re: introducing Numpy.net,
 a pure C# implementation of Numpy
In-Reply-To: <CALGmxEJ=9F3s3M8yp416kW5+JOOTtbW3V-4wDFC8nQ6rHeMACA@mail.gmail.com>
References: <000701d4dbdf$9c7832e0$d56898a0$@baselinesw.com>
 <CAB6mnxJMPXM0E5eLyRYohkCW5bm29nA5eQS7w_2wNEMAdoJrug@mail.gmail.com>
 <CAB6mnxLiiQYFaxDStAkR-c2-MHdpHiq81MoCwiPqpj-5-+o8Bw@mail.gmail.com>
 <004701d4dc14$44981060$cdc83120$@baselinesw.com>
 <CAB6mnxLFJ=CSzrCeOTp5DCgpsKB-mSsTTm8RXA5anCh61461hQ@mail.gmail.com>
 <CADT3MEAKC6Xf=Gm4=Aij8CDchyB0yxCpBs91JjBqWgDKMC89JA@mail.gmail.com>
 <CALGmxEJ=9F3s3M8yp416kW5+JOOTtbW3V-4wDFC8nQ6rHeMACA@mail.gmail.com>
Message-ID: <CADT3MECnZM=71shqqJxrCtJWG8AsxVqk88t-UuYSt8NJATH1Gw@mail.gmail.com>

On Mon, Mar 18, 2019 at 1:19 PM Paul Hobson <pmhobson at gmail.com> wrote:
>
>> I'm a civil engineer who adopted Python early in his career and became
>> the "data guy" in the office pretty early on. Our company's IT department
>> manages lots of Windows Servers running SQL Server. In my case, running
>> python apps on our infrastructure just isn't feasible or supported by the
>> IT department.
>>
>
On Wed, Mar 27, 2019 at 10:30 AM Chris Barker <chris.barker at noaa.gov>
wrote:

> Just curious -- does it have to be C#? or could it be any CLR application
> -- i.e. IronPython?
>

I don't do this enough to know this answer to this question. But we had a
critical mass of past C# projects to serve as a guide that it's been a
relatively low effort to get the C# APIs up and running (e.g., click this
button to deploy).


> I imagine you could build a web service pretty easily in IronPython --
> though AFAIK, the attempts at getting numpy support (and thus Pandas, etc)
> never panned out.
>

That was the state of things (no numpy or pandas) last time I checked. And
C#'s pandas-like approach to DB tables is good enough that I haven't felt
the need check again recently.

The point of all of this is that in those situations, have a numpy-like
>> library would be very nice indeed. I've very excited to hear that the OP's
>> work has been open sourced.
>>
>
> I wonder if the OP's work could be used to make a numpy for Iron Python
> native to the CLR ....
>

That would be very interesting indeed.
-Paul



> -CHB
>
> --
>
> Christopher Barker, Ph.D.
> Oceanographer
>
> Emergency Response Division
> NOAA/NOS/OR&R            (206) 526-6959   voice
> 7600 Sand Point Way NE   (206) 526-6329   fax
> Seattle, WA  98115       (206) 526-6317   main reception
>
> Chris.Barker at noaa.gov
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190327/6500b222/attachment.html>

From sargam18262 at iiitd.ac.in  Thu Mar 28 17:37:12 2019
From: sargam18262 at iiitd.ac.in (Sargam Monga)
Date: Fri, 29 Mar 2019 03:07:12 +0530
Subject: [Numpy-discussion] Outreachy Applicant
Message-ID: <CAMzqykNq3=9kwWc=Yb6uT5UTq6XaDZdXfoL_Tz13AeD4VDx7Yw@mail.gmail.com>

Hello everyone, I am Sargam, an undergrad from India.I am an outreachy
applicant and would like to contribute to this project.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190329/be0b1404/attachment.html>

From dashaishwarya.28 at gmail.com  Thu Mar 28 13:32:53 2019
From: dashaishwarya.28 at gmail.com (Aishwarya Dash)
Date: Thu, 28 Mar 2019 23:02:53 +0530
Subject: [Numpy-discussion] (no subject)
Message-ID: <CAPzp76yfXJa5g4=hqexGKha4y=2DhaX-KZivbQPL8GJjbJTkbg@mail.gmail.com>

Hi, I'm Aishwarya Dash, an applicant for Outreachy, I am quite interested
to work on the docs for Numpy, and I would really appreciate guidelines on
how to contribute to the docs and what ideas I should work on to make my
application better.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190328/ec20443d/attachment.html>

From dashaishwarya.28 at gmail.com  Thu Mar 28 13:37:07 2019
From: dashaishwarya.28 at gmail.com (Aishwarya Dash)
Date: Thu, 28 Mar 2019 23:07:07 +0530
Subject: [Numpy-discussion] Outreachy Applicant
Message-ID: <CAPzp76wxaJTVmD1b0tR6WWrJuLoRqm-Jh_mm_647qR7Mn1jwUw@mail.gmail.com>

Hi, I'm Aishwarya Dash, an applicant for Outreachy. I am quite interested
to work on the documentation for Numpy, and I would really appreciate
guidelines on how to contribute to the docs and what ideas I should work on
in order to make my application better.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190328/cb096af6/attachment.html>

From pmhobson at gmail.com  Thu Mar 28 14:25:50 2019
From: pmhobson at gmail.com (Paul Hobson)
Date: Thu, 28 Mar 2019 11:25:50 -0700
Subject: [Numpy-discussion] Outreachy Applicant
In-Reply-To: <CAPzp76wxaJTVmD1b0tR6WWrJuLoRqm-Jh_mm_647qR7Mn1jwUw@mail.gmail.com>
References: <CAPzp76wxaJTVmD1b0tR6WWrJuLoRqm-Jh_mm_647qR7Mn1jwUw@mail.gmail.com>
Message-ID: <CADT3MEBDDU2yMX1Gg7+ooSPPi2bib_PKXpHM_0uBHrX_nJa_4Q@mail.gmail.com>

I'm not a numpy dev, but I think you should start here:
https://docs.scipy.org/doc/numpy/dev/

And then look at the Github issues, and search the tags for something along
the lines of "documentation" & "good first issue" / "beginner friendly"
-paul



On Thu, Mar 28, 2019 at 10:37 AM Aishwarya Dash <dashaishwarya.28 at gmail.com>
wrote:

> Hi, I'm Aishwarya Dash, an applicant for Outreachy. I am quite interested
> to work on the documentation for Numpy, and I would really appreciate
> guidelines on how to contribute to the docs and what ideas I should work on
> in order to make my application better.
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190328/78688b04/attachment.html>

From pmhobson at gmail.com  Thu Mar 28 14:25:58 2019
From: pmhobson at gmail.com (Paul Hobson)
Date: Thu, 28 Mar 2019 11:25:58 -0700
Subject: [Numpy-discussion] Outreachy Applicant
In-Reply-To: <CAMzqykNq3=9kwWc=Yb6uT5UTq6XaDZdXfoL_Tz13AeD4VDx7Yw@mail.gmail.com>
References: <CAMzqykNq3=9kwWc=Yb6uT5UTq6XaDZdXfoL_Tz13AeD4VDx7Yw@mail.gmail.com>
Message-ID: <CADT3MEDK3-fvs9wLgZFhweW80gXQjYuXmTsCtxrZLdUU=kjvpA@mail.gmail.com>

 I'm not a numpy dev, but I think you should start here:
https://docs.scipy.org/doc/numpy/dev/

And then look at the Github issues, and search the tags for something along
the lines of "documentation" & "good first issue" / "beginner friendly"
-paul


On Thu, Mar 28, 2019 at 10:07 AM Sargam Monga <sargam18262 at iiitd.ac.in>
wrote:

> Hello everyone, I am Sargam, an undergrad from India.I am an outreachy
> applicant and would like to contribute to this project.
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190328/47b4fc76/attachment.html>

From matti.picus at gmail.com  Thu Mar 28 14:42:14 2019
From: matti.picus at gmail.com (Matti Picus)
Date: Thu, 28 Mar 2019 20:42:14 +0200
Subject: [Numpy-discussion] Outreachy Applicant
In-Reply-To: <CAPzp76wxaJTVmD1b0tR6WWrJuLoRqm-Jh_mm_647qR7Mn1jwUw@mail.gmail.com>
References: <CAPzp76wxaJTVmD1b0tR6WWrJuLoRqm-Jh_mm_647qR7Mn1jwUw@mail.gmail.com>
Message-ID: <8c5c390d-6bd7-8af4-9376-47c1219997cb@gmail.com>

On 28/3/19 11:37 pm, Sargam Monga wrote:
> Hello everyone, I am Sargam, an undergrad from India.I am an outreachy 
> applicant and would like to contribute to this project.
>
On 28/3/19 7:37 pm, Aishwarya Dash wrote:
> Hi, I'm Aishwarya Dash, an applicant for Outreachy. I am quite 
> interested to work on the documentation for Numpy, and I would really 
> appreciate guidelines on how to contribute to the docs and what ideas 
> I should work on in order to make my application better.
>
>
Hello and welcome.


To get you started it would be great if you can try to work on an issue
in numpy and create a pull request (PR) to fix it. That way we can get
to know you a bit and you get to know numpy and our workflow.
New contributors might find it easiest to work on the documentation tag/label,
you can see them via:

https://github.com/numpy/numpy/issues?q=is%3Aissue+is%3Aopen+doc+label%3A%2204+-+Documentation%22

Some relevant issues (note some of these may already have someone
interested in them):

https://github.com/numpy/numpy/issues/13013  which probably someone
is already working on

https://github.com/numpy/numpy/issues/13114  which can be broken into a
number of smaller PRs

https://github.com/numpy/numpy/issues/12632

https://github.com/numpy/numpy/issues/12385

and

https://github.com/numpy/numpy/pull/12097  which is a wip to add a
version selector. This is a pure javascript issue.

Our workflow is based on github, for an introduction see
http://www.numpy.org/devdocs/dev/gitwash/development_workflow.html.

For instructions on building the documentation, which uses sphinx, see,
http://www.numpy.org/devdocs/docs/index.html?highlight=documentation  

I hope you can find something to get you started.

Try to work through the process and reach out when you get stuck with
specific questions: "I tried X, expected Y, but got Z".

Feel free to reach out to Sebastian or me directly if you have any
questions. The issues themselves are also a good place to ask for specific guidance.

Best Regards,
Matti



From mayapasiliao at gmail.com  Thu Mar 28 14:52:52 2019
From: mayapasiliao at gmail.com (Maya Dara Sofia Pasiliao)
Date: Thu, 28 Mar 2019 14:52:52 -0400
Subject: [Numpy-discussion] Outreachy applicant introduction
Message-ID: <CADhwNgHrJYV-R2mWi9ZOwun-dBhfchhSA4ubWhYOZD7+3POX7A@mail.gmail.com>

Hello,

My name is Maya Pasiliao, a computer science undergraduate in NYC. I am an
outreachy applicant as well and have seen some of the instructions for
getting started in the other emails. I just wanted to introduce myself and
say I am eager to get started.

Best,
Maya Pasiliao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190328/b83e6476/attachment.html>

From ralf.gommers at gmail.com  Thu Mar 28 16:54:11 2019
From: ralf.gommers at gmail.com (Ralf Gommers)
Date: Thu, 28 Mar 2019 21:54:11 +0100
Subject: [Numpy-discussion] Outreachy applicant introduction
In-Reply-To: <CADhwNgHrJYV-R2mWi9ZOwun-dBhfchhSA4ubWhYOZD7+3POX7A@mail.gmail.com>
References: <CADhwNgHrJYV-R2mWi9ZOwun-dBhfchhSA4ubWhYOZD7+3POX7A@mail.gmail.com>
Message-ID: <CABL7CQgdbhSzsO=hLqfUWYsuLgJmrSPM+tX_Wv4OvZQ6sq5m9A@mail.gmail.com>

On Thu, Mar 28, 2019 at 7:53 PM Maya Dara Sofia Pasiliao <
mayapasiliao at gmail.com> wrote:

> Hello,
>
> My name is Maya Pasiliao, a computer science undergraduate in NYC. I am an
> outreachy applicant as well and have seen some of the instructions for
> getting started in the other emails. I just wanted to introduce myself and
> say I am eager to get started.
>

Welcome Maya!

Cheers,
Ralf


> Best,
> Maya Pasiliao
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190328/bc56c561/attachment.html>

From kevin.k.sheppard at gmail.com  Fri Mar 29 13:01:19 2019
From: kevin.k.sheppard at gmail.com (Kevin Sheppard)
Date: Fri, 29 Mar 2019 17:01:19 +0000
Subject: [Numpy-discussion] Complex Normal Generator in NEP-19 extension
Message-ID: <CAE8Ss2GbD31cMfo=V592QH=RQdmx=NGKR9WVn+WP+HiNfvB=4A@mail.gmail.com>

One part of moving randomgen closer to fulfilling NEP-19 is rationalizing
the API, especially new features not in RandomState. Matti Picus has made a
lot of progress in getting it integrated, especially the part of replacing
RandomState shimed version of the new generator.

There is only one new method in the generator, a scalar generator for
complex normals. It is scalar in the sense that it is the complex version
of np.random.normal, and so supports broadcasting.

This was written based on some GH comments.  This would be a new API and so
it needs to come here first to see if there is any support.

If there is support, then it will appear in the new RandomGenerator, but
not the RandomState replacement. If not, then we can just delete it.

Kevin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190329/e4ce3608/attachment.html>

From einstein.edison at gmail.com  Fri Mar 29 13:03:19 2019
From: einstein.edison at gmail.com (Hameer Abbasi)
Date: Fri, 29 Mar 2019 18:03:19 +0100
Subject: [Numpy-discussion] Complex Normal Generator in NEP-19 extension
In-Reply-To: <CAE8Ss2GbD31cMfo=V592QH=RQdmx=NGKR9WVn+WP+HiNfvB=4A@mail.gmail.com>
References: <CAE8Ss2GbD31cMfo=V592QH=RQdmx=NGKR9WVn+WP+HiNfvB=4A@mail.gmail.com>
Message-ID: <3bdebd60-5821-4869-b586-40e4258cd844@Canary>

> On Friday, Mar 29, 2019 at 6:01 PM, Kevin Sheppard <kevin.k.sheppard at gmail.com (mailto:kevin.k.sheppard at gmail.com)> wrote:
> One part of moving randomgen closer to fulfilling NEP-19 is rationalizing the API, especially new features not in RandomState. Matti Picus has made a lot of progress in getting it integrated, especially the part of replacing RandomState shimed version of the new generator.
>
> There is only one new method in the generator, a scalar generator for complex normals. It is scalar in the sense that it is the complex version of np.random.normal, and so supports broadcasting.
>
> This was written based on some GH comments. This would be a new API and so it needs to come here first to see if there is any support.
>
> If there is support, then it will appear in the new RandomGenerator, but not the RandomState replacement. If not, then we can just delete it.
>
> Kevin
>
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion

+1

Best Regards,
Hameer Abbasi

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190329/66fea1ca/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 695 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190329/66fea1ca/attachment.sig>

From doriszhou1224 at gmail.com  Sat Mar 30 01:27:35 2019
From: doriszhou1224 at gmail.com (Doris Zhou)
Date: Sat, 30 Mar 2019 01:27:35 -0400
Subject: [Numpy-discussion] Outreachy applicant introduction
In-Reply-To: <CADhwNgHrJYV-R2mWi9ZOwun-dBhfchhSA4ubWhYOZD7+3POX7A@mail.gmail.com>
References: <CADhwNgHrJYV-R2mWi9ZOwun-dBhfchhSA4ubWhYOZD7+3POX7A@mail.gmail.com>
Message-ID: <CAG2_NGSBj+RjPuzbDDeAf2UwKFRdm5nadFDNTMeEAFMfX4jUuw@mail.gmail.com>

Hello!

My name is Doris and I am a Computer Science and Statistics student from
Montreal. I am interested in this project and am excited to start
contributing.

Cheers

On Thu, Mar 28, 2019, 2:54 PM Maya Dara Sofia Pasiliao, <
mayapasiliao at gmail.com> wrote:

> Hello,
>
> My name is Maya Pasiliao, a computer science undergraduate in NYC. I am an
> outreachy applicant as well and have seen some of the instructions for
> getting started in the other emails. I just wanted to introduce myself and
> say I am eager to get started.
>
> Best,
> Maya Pasiliao
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190330/c5ef25de/attachment.html>

From vaishnavi.sanchi at gmail.com  Sat Mar 30 06:28:31 2019
From: vaishnavi.sanchi at gmail.com (Sanchi Vaishnavi)
Date: Sat, 30 Mar 2019 15:58:31 +0530
Subject: [Numpy-discussion] Beginner Help: Generating HTML using Sphinx
Message-ID: <CALsXdyAUHEBB=OgmisXp0ZH8633J6UdMSC5TdhvTgWF9RwP-mw@mail.gmail.com>

I was learning to get to $ make html to work. These are the final steps
that I used on my test branch in my numpy repo:

$  sphinx-build -b html doc/source builddir
> >> build succeeded, 165 warnings.

$  make html

>> make: *** No rule to make target `html?.  Stop.


I checked one of the resultant HTML pages, and the changes had been made as
expected.
But to make sense of the last message, on reading on forums
(StackOverflow), I found that I got that error because I was in the
directory which* did not* contain the makefile. So:

$  cd doc
> $  make html
> >> sphinx-build: error: unrecognized arguments: --keep-going
> >> make: *** [html] Error 2


 I can't make sense of the last two errors. I had followed the instructions
from NumPy
<http://www.numpy.org/devdocs/docs/howto_build_docs.html#sphinx-extensions> and
Sphinx-doc
<http://www.sphinx-doc.org/en/master/usage/quickstart.html#running-the-build>
.
I realize that this question is not about NumPy, so I appreciate any
resource you can point me to.

Thank you!

Sanchi
https://github.com/chelwin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190330/10a8a598/attachment-0001.html>

From sebastian at sipsolutions.net  Sat Mar 30 08:17:46 2019
From: sebastian at sipsolutions.net (Sebastian Berg)
Date: Sat, 30 Mar 2019 13:17:46 +0100
Subject: [Numpy-discussion] Beginner Help: Generating HTML using Sphinx
In-Reply-To: <CALsXdyAUHEBB=OgmisXp0ZH8633J6UdMSC5TdhvTgWF9RwP-mw@mail.gmail.com>
References: <CALsXdyAUHEBB=OgmisXp0ZH8633J6UdMSC5TdhvTgWF9RwP-mw@mail.gmail.com>
Message-ID: <ceb21cb1aa50ac636b065fac567917a354339623.camel@sipsolutions.net>

Hi Sanchi,

On Sat, 2019-03-30 at 15:58 +0530, Sanchi Vaishnavi wrote:
> I was learning to get to $ make html to work. These are the final
> steps that I used on my test branch in my numpy repo: 
> 
> > $  sphinx-build -b html doc/source builddir 
> > >> build succeeded, 165 warnings. 
> > $  make html 
> > >> make: *** No rule to make target `html?.  Stop.
> 
>  
> I checked one of the resultant HTML pages, and the changes had been
> made as expected. 
> But to make sense of the last message, on reading on forums
> (StackOverflow), I found that I got that error because I was in the
> directory which did not contain the makefile. So: 
> 
> > $  cd doc
> > $  make html
> > >> sphinx-build: error: unrecognized arguments: --keep-going
> > >> make: *** [html] Error 2
> 

It sounds like your sphinx version is older and is missing the
"--keep-going" argument. It would probably be best to upgrade your
sphinx version.

Best,

Sebastian


>  
>  I can't make sense of the last two errors. I had followed the
> instructions from NumPy and Sphinx-doc.
> I realize that this question is not about NumPy, so I appreciate any
> resource you can point me to.
>  
> Thank you! 
> 
> Sanchi
> https://github.com/chelwin
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190330/a2dcb0a2/attachment.sig>

From unofficialparul at gmail.com  Sat Mar 30 09:51:32 2019
From: unofficialparul at gmail.com (Parul Unofficial)
Date: Sat, 30 Mar 2019 19:21:32 +0530
Subject: [Numpy-discussion] Outreachy applicant introduction
Message-ID: <CAAmvdBp5kXtE37PaMYJWsLzHe_PPNqLDnZXvTE=pT_4B0i1MpQ@mail.gmail.com>

Hello!

I'm Parul Aggarwal, a pre-final year  student from India pursuing my
bachelor's in Computer Science. I'm comfortable programming in C++ and
Python and have also worked previously on some projects based on flask,
Django. I'm an outreachy applicant and really excited to contribute to this
large community and I hope, I'm not too late to start with my
contributions.  Any guidance regarding the same would be really helpful.

Thank You!

Best
Parul Aggarwal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190330/ab20e46d/attachment.html>

From hagarhaytham597 at gmail.com  Sat Mar 30 10:19:29 2019
From: hagarhaytham597 at gmail.com (hagar haytham)
Date: Sat, 30 Mar 2019 16:19:29 +0200
Subject: [Numpy-discussion] [Outreachy Program][Improve C API documentation
 for NumPy]
Message-ID: <CAC6_R71iG1zoJiz4J6T-0vJmU3MAPbP-PQSsn+d6qE_MioQAkQ@mail.gmail.com>

Hey
I am Hagar Haytham, a Computer Engineering student. I have some experience
in python. I would like to be a part from this community and contribute to
it. I am just making sure that you're still accepting applicants and hope i
am not too late as I am still familiarizing myself with the environment.

 Thanks
Hagar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190330/1af71f4b/attachment.html>

From sebastian at sipsolutions.net  Sat Mar 30 11:13:45 2019
From: sebastian at sipsolutions.net (Sebastian Berg)
Date: Sat, 30 Mar 2019 16:13:45 +0100
Subject: [Numpy-discussion] Outreachy applicant introduction
In-Reply-To: <CAAmvdBp5kXtE37PaMYJWsLzHe_PPNqLDnZXvTE=pT_4B0i1MpQ@mail.gmail.com>
References: <CAAmvdBp5kXtE37PaMYJWsLzHe_PPNqLDnZXvTE=pT_4B0i1MpQ@mail.gmail.com>
Message-ID: <a0076f9c02a7828932efb00a8ff6f9ff58826f01.camel@sipsolutions.net>

On Sat, 2019-03-30 at 19:21 +0530, Parul Unofficial wrote:
> Hello!
> 
> I'm Parul Aggarwal, a pre-final year  student from India pursuing my
> bachelor's in Computer Science. I'm comfortable programming in C++
> and Python and have also worked previously on some projects based on
> flask, Django. I'm an outreachy applicant and really excited to
> contribute to this large community and I hope, I'm not too late to
> start with my contributions.  Any guidance regarding the same would
> be really helpful.

On Sat, 2019-03-30 at 16:19 +0200, hagar haytham wrote:
> Hey
> I am Hagar Haytham, a Computer Engineering student. I have some
> experience in python. I would like to be a part from this community
> and contribute to it. I am just making sure that you're still
> accepting applicants and hope i am not too late as I am still
> familiarizing myself with the environment.


Hello and welcome,

Yes, you can still apply, although the deadline is getting close of
course and you are required to start working on some issue by creating
a pull request. You will also need to apply on the Outreachy website.

Some issues that may be relevant are:

https://github.com/numpy/numpy/issues/12385

and

https://github.com/numpy/numpy/pull/12097 which is a wip to add a 
version selector. This is a pure javascript issue.

But maybe it is better/quicker to look at issues with the documentation
tag yourself and see if you find one that seems interesting to you and
a good start (please try a bit to avoid issues someone else is already
working on, although if there is no PR already open you can try. There
seems to be quite a bit of last minute activity):

https://github.com/numpy/numpy/issues?q=is:issue+is:open+label:"04+-+Documentation


Our workflow is based on github, for an introduction see 
http://www.numpy.org/devdocs/dev/gitwash/development_workflow.html. 

For instructions on building the documentation, which uses sphinx, see,
http://www.numpy.org/devdocs/docs/index.html?highlight=documentation 

I hope you can find something to get you started, once you do, do not
forget to apply on the Outreachy website and not what you worked on.

If you have further questions feel free to send another email to Matti
or me or if it is related, ask on the specific issue on github.

Best Regards,

Sebastian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190330/069cc6c9/attachment.sig>

From vaishnavi.sanchi at gmail.com  Sat Mar 30 13:45:31 2019
From: vaishnavi.sanchi at gmail.com (Sanchi Vaishnavi)
Date: Sat, 30 Mar 2019 23:15:31 +0530
Subject: [Numpy-discussion] Beginner Help: Generating HTML using Sphinx
In-Reply-To: <ceb21cb1aa50ac636b065fac567917a354339623.camel@sipsolutions.net>
References: <CALsXdyAUHEBB=OgmisXp0ZH8633J6UdMSC5TdhvTgWF9RwP-mw@mail.gmail.com>
 <ceb21cb1aa50ac636b065fac567917a354339623.camel@sipsolutions.net>
Message-ID: <CALsXdyCKeMa=P2kDhCf9-zTAPPdi4zhP55_K5H1aaaN9pOg3zQ@mail.gmail.com>

Hi Sebastian,

Thank you, it works perfectly now.
I wrongly assumed that I'd installed the latest version.

As it happens, conda currently ships the version 1.7.4 of sphinx, as
against the latest version 2.0.0.
I did this: pip install -U sphinx

Best,

Sanchi


On Sat, Mar 30, 2019 at 5:48 PM Sebastian Berg <sebastian at sipsolutions.net>
wrote:

> Hi Sanchi,
>
> On Sat, 2019-03-30 at 15:58 +0530, Sanchi Vaishnavi wrote:
> > I was learning to get to $ make html to work. These are the final
> > steps that I used on my test branch in my numpy repo:
> >
> > > $  sphinx-build -b html doc/source builddir
> > > >> build succeeded, 165 warnings.
> > > $  make html
> > > >> make: *** No rule to make target `html?.  Stop.
> >
> >
> > I checked one of the resultant HTML pages, and the changes had been
> > made as expected.
> > But to make sense of the last message, on reading on forums
> > (StackOverflow), I found that I got that error because I was in the
> > directory which did not contain the makefile. So:
> >
> > > $  cd doc
> > > $  make html
> > > >> sphinx-build: error: unrecognized arguments: --keep-going
> > > >> make: *** [html] Error 2
> >
>
> It sounds like your sphinx version is older and is missing the
> "--keep-going" argument. It would probably be best to upgrade your
> sphinx version.
>
> Best,
>
> Sebastian
>
>
> >
> >  I can't make sense of the last two errors. I had followed the
> > instructions from NumPy and Sphinx-doc.
> > I realize that this question is not about NumPy, so I appreciate any
> > resource you can point me to.
> >
> > Thank you!
> >
> > Sanchi
> > https://github.com/chelwin
> > _______________________________________________
> > NumPy-Discussion mailing list
> > NumPy-Discussion at python.org
> > https://mail.python.org/mailman/listinfo/numpy-discussion
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190330/5fa600e9/attachment.html>

From p.e.creasey.00 at googlemail.com  Sat Mar 30 16:56:12 2019
From: p.e.creasey.00 at googlemail.com (Peter Creasey)
Date: Sat, 30 Mar 2019 20:56:12 +0000
Subject: [Numpy-discussion] Complex Normal Generator in NEP-19 extension
Message-ID: <CACUQHuKM4vq=EK3bw_uPkJPTg75xRGS9ujkZoj98awRgyO7WhA@mail.gmail.com>

If there is support, then it will appear in the new RandomGenerator, but
> not the RandomState replacement. If not, then we can just delete it.
>
>
+1 for complex normal generation.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190330/a6935e88/attachment.html>

From einstein.edison at gmail.com  Sat Mar 30 18:24:00 2019
From: einstein.edison at gmail.com (Hameer Abbasi)
Date: Sat, 30 Mar 2019 23:24:00 +0100
Subject: [Numpy-discussion] Complex Normal Generator in NEP-19 extension
In-Reply-To: <3bdebd60-5821-4869-b586-40e4258cd844@Canary>
References: <CAE8Ss2GbD31cMfo=V592QH=RQdmx=NGKR9WVn+WP+HiNfvB=4A@mail.gmail.com>
 <3bdebd60-5821-4869-b586-40e4258cd844@Canary>
Message-ID: <a841aa9a-cba6-43a7-9b1e-863378f3adbf@Canary>

> On Friday, Mar 29, 2019 at 6:03 PM, Hameer Abbasi <einstein.edison at gmail.com (mailto:einstein.edison at gmail.com)> wrote:
> > On Friday, Mar 29, 2019 at 6:01 PM, Kevin Sheppard <kevin.k.sheppard at gmail.com (mailto:kevin.k.sheppard at gmail.com)> wrote:
> > One part of moving randomgen closer to fulfilling NEP-19 is rationalizing the API, especially new features not in RandomState. Matti Picus has made a lot of progress in getting it integrated, especially the part of replacing RandomState shimed version of the new generator.
> >
> > There is only one new method in the generator, a scalar generator for complex normals. It is scalar in the sense that it is the complex version of np.random.normal, and so supports broadcasting.
> >
> > This was written based on some GH comments. This would be a new API and so it needs to come here first to see if there is any support.
> >
> > If there is support, then it will appear in the new RandomGenerator, but not the RandomState replacement. If not, then we can just delete it.
> >
> > Kevin
> >
> > _______________________________________________
> > NumPy-Discussion mailing list
> > NumPy-Discussion at python.org
> > https://mail.python.org/mailman/listinfo/numpy-discussion
>
> +1
>
> Best Regards,
> Hameer Abbasi
>
>
>
>

To expand on this, the Complex normal distribution is pretty common in communications, control, signals and systems, and so on. :) It?d be a great add.

Best Regards,
Hameer Abbasi

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190330/0c5526c4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 695 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190330/0c5526c4/attachment.sig>

From m.h.vankerkwijk at gmail.com  Sun Mar 31 12:25:12 2019
From: m.h.vankerkwijk at gmail.com (Marten van Kerkwijk)
Date: Sun, 31 Mar 2019 12:25:12 -0400
Subject: [Numpy-discussion] Complex Normal Generator in NEP-19 extension
In-Reply-To: <a841aa9a-cba6-43a7-9b1e-863378f3adbf@Canary>
References: <CAE8Ss2GbD31cMfo=V592QH=RQdmx=NGKR9WVn+WP+HiNfvB=4A@mail.gmail.com>
 <3bdebd60-5821-4869-b586-40e4258cd844@Canary>
 <a841aa9a-cba6-43a7-9b1e-863378f3adbf@Canary>
Message-ID: <CAJNV+9t6X=AUeLsuUtid9PtnVbix6j0oPToen2Qff_0zE5+Nsw@mail.gmail.com>

Certainly have done `np.random.normal(2*n).view('c16')` very often. Makes
sense to just allow it to be generated directly. -- Marten

On Sat, Mar 30, 2019 at 6:24 PM Hameer Abbasi <einstein.edison at gmail.com>
wrote:

> On Friday, Mar 29, 2019 at 6:03 PM, Hameer Abbasi <
> einstein.edison at gmail.com> wrote:
>
> On Friday, Mar 29, 2019 at 6:01 PM, Kevin Sheppard <
> kevin.k.sheppard at gmail.com> wrote:
> One part of moving randomgen closer to fulfilling NEP-19 is rationalizing
> the API, especially new features not in RandomState. Matti Picus has made a
> lot of progress in getting it integrated, especially the part of replacing
> RandomState shimed version of the new generator.
>
> There is only one new method in the generator, a scalar generator for
> complex normals. It is scalar in the sense that it is the complex version
> of np.random.normal, and so supports broadcasting.
>
> This was written based on some GH comments.  This would be a new API and
> so it needs to come here first to see if there is any support.
>
> If there is support, then it will appear in the new RandomGenerator, but
> not the RandomState replacement. If not, then we can just delete it.
>
> Kevin
>
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
>
> +1
>
> Best Regards,
> Hameer Abbasi
>
>
> To expand on this, the Complex normal distribution is pretty common in
> communications, control, signals and systems, and so on. :) It?d be a great
> add.
>
> Best Regards,
> Hameer Abbasi
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190331/fdec1040/attachment.html>

From valentinatessy at gmail.com  Sun Mar 31 15:56:40 2019
From: valentinatessy at gmail.com (Mbeng Tanyi)
Date: Sun, 31 Mar 2019 20:56:40 +0100
Subject: [Numpy-discussion] Beginner Help: Generating HTML using Sphinx
In-Reply-To: <CALsXdyCKeMa=P2kDhCf9-zTAPPdi4zhP55_K5H1aaaN9pOg3zQ@mail.gmail.com>
References: <CALsXdyAUHEBB=OgmisXp0ZH8633J6UdMSC5TdhvTgWF9RwP-mw@mail.gmail.com>
 <ceb21cb1aa50ac636b065fac567917a354339623.camel@sipsolutions.net>
 <CALsXdyCKeMa=P2kDhCf9-zTAPPdi4zhP55_K5H1aaaN9pOg3zQ@mail.gmail.com>
Message-ID: <CADQdFiqsndFpZyMmzOHv5GR8PD8JaaonUdc4Tpqf49BfP+CJKw@mail.gmail.com>

Hello

I also got an error the first time I tried $ make file as follows:

> mkdir -p build/html build/doctrees
> LANG=C sphinx-build -b html -WT --keep-going -d build/doctrees   source
> build/html
> /bin/sh: 1: sphinx-build: not found
> Makefile:123: recipe for target 'html' failed
> make: *** [html] Error 127


After upgrading to sphinx2 as was suggested here, I still get errors after $
make html :

> mkdir -p build/html build/doctrees
> LANG=C sphinx-build -b html -WT --keep-going -d build/doctrees   source
> build/html
> Traceback (most recent call last):
>   File "/home/valentina-t/.local/bin/sphinx-build", line 7, in <module>
>     from sphinx.cmd.build import main
>   File
> "/home/valentina-t/.local/lib/python2.7/site-packages/sphinx/cmd/build.py",
> line 39
>     file=stderr)
>         ^
> SyntaxError: invalid syntax
> Makefile:123: recipe for target 'html' failed
> make: *** [html] Error
>


On Sat, Mar 30, 2019 at 6:47 PM Sanchi Vaishnavi <vaishnavi.sanchi at gmail.com>
wrote:

> Hi Sebastian,
>
> Thank you, it works perfectly now.
> I wrongly assumed that I'd installed the latest version.
>
> As it happens, conda currently ships the version 1.7.4 of sphinx, as
> against the latest version 2.0.0.
> I did this: pip install -U sphinx
>
> Best,
>
> Sanchi
>
>
> On Sat, Mar 30, 2019 at 5:48 PM Sebastian Berg <sebastian at sipsolutions.net>
> wrote:
>
>> Hi Sanchi,
>>
>> On Sat, 2019-03-30 at 15:58 +0530, Sanchi Vaishnavi wrote:
>> > I was learning to get to $ make html to work. These are the final
>> > steps that I used on my test branch in my numpy repo:
>> >
>> > > $  sphinx-build -b html doc/source builddir
>> > > >> build succeeded, 165 warnings.
>> > > $  make html
>> > > >> make: *** No rule to make target `html?.  Stop.
>> >
>> >
>> > I checked one of the resultant HTML pages, and the changes had been
>> > made as expected.
>> > But to make sense of the last message, on reading on forums
>> > (StackOverflow), I found that I got that error because I was in the
>> > directory which did not contain the makefile. So:
>> >
>> > > $  cd doc
>> > > $  make html
>> > > >> sphinx-build: error: unrecognized arguments: --keep-going
>> > > >> make: *** [html] Error 2
>> >
>>
>> It sounds like your sphinx version is older and is missing the
>> "--keep-going" argument. It would probably be best to upgrade your
>> sphinx version.
>>
>> Best,
>>
>> Sebastian
>>
>>
>> >
>> >  I can't make sense of the last two errors. I had followed the
>> > instructions from NumPy and Sphinx-doc.
>> > I realize that this question is not about NumPy, so I appreciate any
>> > resource you can point me to.
>> >
>> > Thank you!
>> >
>> > Sanchi
>> > https://github.com/chelwin
>> > _______________________________________________
>> > NumPy-Discussion mailing list
>> > NumPy-Discussion at python.org
>> > https://mail.python.org/mailman/listinfo/numpy-discussion
>> _______________________________________________
>> NumPy-Discussion mailing list
>> NumPy-Discussion at python.org
>> https://mail.python.org/mailman/listinfo/numpy-discussion
>>
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190331/3f80d47d/attachment.html>

From matti.picus at gmail.com  Sun Mar 31 16:20:19 2019
From: matti.picus at gmail.com (Matti Picus)
Date: Sun, 31 Mar 2019 23:20:19 +0300
Subject: [Numpy-discussion] Beginner Help: Generating HTML using Sphinx
In-Reply-To: <CADQdFiqsndFpZyMmzOHv5GR8PD8JaaonUdc4Tpqf49BfP+CJKw@mail.gmail.com>
References: <CALsXdyAUHEBB=OgmisXp0ZH8633J6UdMSC5TdhvTgWF9RwP-mw@mail.gmail.com>
 <ceb21cb1aa50ac636b065fac567917a354339623.camel@sipsolutions.net>
 <CALsXdyCKeMa=P2kDhCf9-zTAPPdi4zhP55_K5H1aaaN9pOg3zQ@mail.gmail.com>
 <CADQdFiqsndFpZyMmzOHv5GR8PD8JaaonUdc4Tpqf49BfP+CJKw@mail.gmail.com>
Message-ID: <adf85517-4e84-8b4a-ec78-698ed4b02af2@gmail.com>


On 31/3/19 10:56 pm, Mbeng Tanyi wrote:
> Hello
>
> I also got an error the first time I tried $ make file as follows:
>
>     mkdir -p build/html build/doctrees
>     LANG=C sphinx-build -b html -WT --keep-going -d build/doctrees
>     source build/html
>     /bin/sh: 1: sphinx-build: not found
>     Makefile:123: recipe for target 'html' failed
>     make: *** [html] Error 127
>
>
> After upgrading to sphinx2 as was suggested here, I still get errors 
> after $ make html :
>
>     mkdir -p build/html build/doctrees
>     LANG=C sphinx-build -b html -WT --keep-going -d build/doctrees??
>     source build/html
>     Traceback (most recent call last):
>     ? File "/home/valentina-t/.local/bin/sphinx-build", line 7, in
>     <module>
>     ??? from sphinx.cmd.build import main
>     ? File
>     "/home/valentina-t/.local/lib/python2.7/site-packages/sphinx/cmd/build.py",
>     line 39
>     ??? file=stderr)
>     ??????? ^
>     SyntaxError: invalid syntax
>     Makefile:123: recipe for target 'html' failed
>     make: *** [html] Error
>
>
>
>

You need to use sphinx version 1.8.5, and python3.6.

Matti