[Numpy-discussion] Re: hello from your Contributor Experience Lead

[Ralf Gommers]

Hi Inessa,

Happy holidays to you and everyone on this list!

Also, I'm excited to see what you can do in this new role! It's great that
we have dedicated funded time for improving the contributor experience.

It's been a few months since Melissa announced that we got a new grant
(jointly with SciPy, Matplotlib and Pandas) [1], so for those people who
would like some more context, the grant proposal is described in Melissa's
message and published at [2].

Cheers,
Ralf

[1]
https://mail.python.org/archives/list/numpy-discussion@python.org/message/VUGREVPU3VO236HBCFSJNLD5Y55S62JT/
[2]
https://figshare.com/articles/online_resource/Advancing_an_inclusive_culture_in_the_scientific_Python_ecosystem/16548063


On Thu, Dec 16, 2021 at 6:49 AM Inessa Pawson  wrote:

> Hi, everyone!
> Most of you know me as an active contributor on the NumPy web and survey
> teams and organizer of numerous Python community events. At the beginning
> of this month, I started in a new role at NumPy – a Contributor Experience
> Lead.
>
> Stop by and say hi at the next NumPy Newcomers' Hour which is scheduled
> for *today, Dec 16th at 4 pm UTC**. Follow the link to join via Zoom:
> https://zoom.us/j/6345425936
>
> *To convert the start time to the local time of the area you are in, use
> the following link:
> https://www.timeanddate.com/worldclock/fixedtime.html?msg=NumPy+Newcomers%27+Hour&iso=20211216T16&p1=1440&ah=1
>
> --
> Every good wish,
> Inessa
>
>
> ___
> NumPy-Discussion mailing list -- numpy-discussion@python.org
> To unsubscribe send an email to numpy-discussion-le...@python.org
> https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
> Member address: ralf.gomm...@googlemail.com
>
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com

[Numpy-discussion] Re: New

[Ralf Gommers]

On Sun, Dec 26, 2021 at 2:13 PM Isha Verma  wrote:

> Hello I am new to NumPy and I would like to contribute. Can someone please
> help me with the ways I can contribute !
>

Hi Isha, welcome! We have extensive contributor documentation, and guidance
on what types of contributions you can make at https://numpy.org/contribute/.
There's also a Slack workspace linked there that you can get access to; the
#newcomers channel has regular suggestions on tasks that may be nice for
new contributors. And it's a good place to ask questions.

Cheers,
Ralf
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com

[Numpy-discussion] Re: An article on numpy data types

[Lev Maximov]

> I'm surprised no one has mentioned it already: int and uint are reversed
in the first table.
Not anymore! I know I'm susceptible to this type of blunders )

Thank you for your kind attention!

I've made a few more fixes here and there and added a couple of
illustrations. Looks more or less finished to me.
Giving it away to the editors.

Best regards,
Lev


On Mon, Dec 27, 2021 at 5:17 AM Juan Nunez-Iglesias 
wrote:

> I'm surprised no one has mentioned it already: int and uint are reversed
> in the first table.
>
> I do agree with others that this is a great overview page that should be
> included in the numpy docs. Thanks Lev!
>
> Juan.
>
> On Sun, 26 Dec 2021, at 12:59 PM, Lev Maximov wrote:
>
> I've tried to take into account all the suggestions from this thread.
>
> https://axil.github.io/numpy-data-types.html shows new version now and
>
>
> https://github.com/axil/numpy-data-types/commit/14d9da053fd67e5569436faa1f58599c0cc8b380#diff-ed7002b439e9ac845f22357d822bac1444730fbdb6016d3ec9432297b9ec9f73
> displays most of the changes.
>
> As for the inheritance diagram, I think it is perfectly fine to add it to
> the documentation as is,
> except that I'd put back the 'void' type I've originally omitted to keep
> it simple.
>
> Btw is anyone aware why 'U' is missing from the np.typecode['Character']?
>
> On Sun, Dec 26, 2021 at 11:57 PM Lev Maximov 
> wrote:
>
> Python 3.9.7 (tags/v3.9.7:1016ef3, Aug 30 2021, 20:19:38) [MSC v.1929 64
> bit (AMD64)] on win32
>
>   ^^ this is relevant this
> is not
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import numpy as np
> >>> np.int_
> 
>
> On Sun, Dec 26, 2021 at 11:42 PM Michael Siebert <
> michael.sieber...@gmail.com> wrote:
>
>
> Okay, little modification to my last mail: many Android smartphones are
> still 32 bit, but according to
>
> https://www.androidauthority.com/arm-32-vs-64-bit-explained-1232065/
>
> from 2023 on, all (or at least many) new ARM processors will be 64 bit
> only.
>
> Apple‘s iPhone 64 bit only since quite a while already (September 2017,
> iOS 11 release).
>
> On 26. Dec 2021, at 17:31, Lev Maximov  wrote:
>
> 
> Hi Michael,
>
> > Python on Windows is and is supposed to be, as far as I get it, a dying
> platform.
> I would join Matti in thinking that it is a misconception.
>
> Have you heard of the enormous daily updated unofficial repository
>  of the binary windows
> compilations of
> almost 600 python libraries by Christoph Gohlke? (numpy and libs depending
> on it are built with MKL there)
> It is there for a reason.
>
> If you look at the stats such as this one (Matti already mentioned them
> while I was writing this text),
>
> https://www.jetbrains.com/research/python-developers-survey-2018/
> https://www.jetbrains.com/lp/python-developers-survey-2020/
>
> you'll see (in addition to the fact that numpy is the #1 library in data
> science ;) ) that in
> the recent years the percentage of windows user among the developers is
> quite high:
> 69% linux - 47% windows - 32% macos (2018)
> 68% linux - 48% windows - 29% macos (2020)
> So it looks as if it is rather growing than dying.
>
> This is due to the popularity of the above mentioned data science and AI,
> which have skyrocketed in the
> last 10 years. And the vast majority of data scientists work on windows.
>
> Windows as a platform for developers as a whole is also quite flourishing
> today.
> According to the stackoverflow 2021 developer survey
> 
> 45% of the respondents use Windows (25% linux, 25% macos).
> Among the professional developers the numbers are 41% for windows, 30%
> macos, 26% linux.
>
> Also the primary audience of the tutorials like mine (as well as of
> stackoverflow?) are windows users.
> Linux users can easily figure things described there on their own, through
> the docstrings, source code
> or, as a last resort, through the docs )
>
> >The more experienced the Python developers are, the more likely they are
> to use Linux and macOS as development
> > environments, and the less likely they are to choose Windows.
> (from the same jetbrains survey of 2018)
>
> I wouldn't like to go into holy wars, though. I'm equally literate in both
> unix and windows (somewhat less in macos)
> and in my opinion the interests of all the users of the the three
> operating systems should be taken into account
> in both the code of the library and the docs.
>
> The documentation is sometimes pretty ignorant of mac/windows users, btw:
> > Alias on this platform (Linux x86_64)
> https://numpy.org/doc/stable/reference/arrays.scalars.html#numpy.int_
> And what about the other platforms?
>
> As for the particular issue of the difference in the default integer
> types, in my opinion the default choice of int32 on windows for
> array [1,2,3] fits the description
>
> >" If not given, 

[Numpy-discussion] Re: An article on numpy data types

[Eric Firing]

On 2021/12/27 9:32 AM, Lev Maximov wrote:
 > I'm surprised no one has mentioned it already: int and uint are 
reversed in the first table.

Not anymore! I know I'm susceptible to this type of blunders )

Thank you for your kind attention!

I've made a few more fixes here and there and added a couple of 
illustrations. Looks more or less finished to me.

Giving it away to the editors.

Best regards,
Lev



Lev,

I think timedelta64 is missing.  Is that intentional?

Eric
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com

[Numpy-discussion] Re: help with PyArrayInterface

[bloring]

Thank you Matti. That is what I was looking for!

However, I've since learned that it is not what is needed. I'm posting again 
because I found some aspects of the PyArrayInterface a bit inconsistent w/ 
other places in numpy and confusing. It may be the case that others in the 
future find this post helpful.

Numpy's PyArrayInterface structure in its simplest use requires 3 fields to 
declare the type of data pointed to.

```
char typekind; // a code declaring the type, does not declare the size of the 
type. 
int itemsize; // the size of the type declared in typekind
int flags; // flags that among other things declare endianness of the data 
pointed to
```

I needed all 3 of these, the flags field was needed to tell that the memory was 
in native machine order because that is not the default.

Thanks for the help, I got it working
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com