[Numpy-discussion] Re: Numpy binary wheels and CI for win/arm64 platform

2022-06-22 Thread Niyas Sait 
>
> Hi Niyas, I'd be interested in remote access to a development machine.
> This will help with NumPy and SciPy; and it would allow testing binaries
> resulting from a cross-compilation step.
> I don't have a preference for a Volterra box or an Azure VM - as long as
> it can be used for development purposes the details of getting access are
> not that important I'd say.


Thanks, Ralf for the interest. I will sort it out and will let you know.

I don't think integration in the main NumPy CI is an option right now,
> however I also don't think it is necessary. A standalone daily or weekly
> scheduled job that would notify interested devs should already be very
> helpful.


FYI, Linaro has set up a downstream CI (Nightly) to track NumPy. See log
for one of the previous runs here -
https://gitlab.com/Linaro/windowsonarm/nightly/-/jobs/2622310764.
Hopefully, that will help.

Niyas



On Tue, 21 Jun 2022 at 13:05, Ralf Gommers  wrote:

>
>
> On Mon, Jun 6, 2022 at 5:08 PM Niyas Sait  wrote:
>
>> > When you say "we could request access to new Volterra machines": how do
>> > you see that playing out? Who would provide them, and who would maintain
>> > them? Would they be available to the more general scientific python
>> > community? Who would pay the bill?
>>
>> Microsoft, Qualcomm, and Arm are very interested in native support for
>> Numpy and other scientific packages for Windows on Arm platform.
>> And we have contacts with them to start the relevant discussion if there
>> is interest to use those dev boxes (local or remote access)
>> or Azure VMs for CI/CD purposes.
>>
>
> Hi Niyas, I'd be interested in remote access to a development machine.
> This will help with NumPy and SciPy; and it would allow testing binaries
> resulting from a cross-compilation step.
>
> I don't have a preference for a Volterra box or an Azure VM - as long as
> it can be used for development purposes the details of getting access are
> not that important I'd say.
>
>
>>
>> Hope that answers your questions.
>>
>> Niyas
>>
>>
>>
>> On Mon, 6 Jun 2022 at 14:51, Matti Picus  wrote:
>>
>>> When you say "we could request access to new Volterra machines": how do
>>> you see that playing out? Who would provide them, and who would maintain
>>> them? Would they be available to the more general scientific python
>>> community? Who would pay the bill? If the people supporting this niche
>>> platform stop doing so, can we drop the wheels? CPython has PEP 11 [0],
>>> maybe this effort should start by writing a similar NEP for the
>>> scientific python community.
>>>
>>> Matti
>>>
>>>
>>> [0] https://peps.python.org/pep-0011
>>>
>>>
>>> On 6/6/22 13:35, Niyas Sait wrote:
>>> > Hello,
>>> >
>>> > It has been a while since we discussed adding CI/CD support for
>>> > Windows on Arm. Let me share a few updates and see if we can find a
>>> > way forward.
>>> >
>>> > First of all, Thanks for suggesting cibuildwheel. We have couple of
>>> > patches in progress to add native [1] and cross-compilation support
>>> > [2] to cibuildwheel. They could solve the binary wheel creation and
>>> > releases. However, we may still lack support for CI.
>>> >
>>> > I would like to check if there is any interest in using Windows/Arm64
>>> > VMs in Azure [3] or Volterra machines ( new Windows/Arm64 Dev Boxes )
>>> > [4] to add CI support for WoA platform.
>>> >
>>> > In order to use Azure VMs with GitHub Actions or Azure Pipeline, we
>>> > must set up self-hosted runners. I am not sure if that would be an
>>> > acceptable workflow for the numpy community. If that could work we
>>> > could potentially find ways to fund the required VMs for NumPy project.
>>>
>>
> I don't think integration in the main NumPy CI is an option right now,
> however I also don't think it is necessary. A standalone daily or weekly
> scheduled job that would notify interested devs should already be very
> helpful.
>
> Cheers,
> Ralf
>
>
>
>> >
>>> > Also, we could request access to new Volterra machines for Numpy
>>> > CI/CD. I know it is not easy to maintain them as part of CI/CD
>>> > workflow, but if any maintainers are interested in using them for
>>> > CI/CD purposes, we can progress on that discussion.
>>> >
>>> > Let me know what you think.
>>> >
>>> > Thanks
>>> > Niyas
>>> >
>>> > [1] https://github.com/pypa/cibuildwheel/pull/920
>>> > [2] https://github.com/pypa/cibuildwheel/pull/1108
>>> > [3]
>>> >
>>> https://azure.microsoft.com/en-us/blog/now-in-preview-azure-virtual-machines-with-ampere-altra-armbased-processors/
>>> > [4]
>>> >
>>> https://blogs.windows.com/windowsdeveloper/2022/05/24/create-next-generation-experiences-at-scale-with-windows/
>>> ___
>>> 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: niyas.s...@linaro.org
>>>
>> ___

[Numpy-discussion] Re: Numpy binary wheels and CI for win/arm64 platform

2022-06-22 Thread Ralf Gommers 
On Wed, Jun 22, 2022 at 11:35 AM Niyas Sait  wrote:

> Hi Niyas, I'd be interested in remote access to a development machine.
>> This will help with NumPy and SciPy; and it would allow testing binaries
>> resulting from a cross-compilation step.
>> I don't have a preference for a Volterra box or an Azure VM - as long as
>> it can be used for development purposes the details of getting access are
>> not that important I'd say.
>
>
> Thanks, Ralf for the interest. I will sort it out and will let you know.
>

Thanks Niyas


>
> I don't think integration in the main NumPy CI is an option right now,
>> however I also don't think it is necessary. A standalone daily or weekly
>> scheduled job that would notify interested devs should already be very
>> helpful.
>
>
> FYI, Linaro has set up a downstream CI (Nightly) to track NumPy. See log
> for one of the previous runs here -
> https://gitlab.com/Linaro/windowsonarm/nightly/-/jobs/2622310764.
> Hopefully, that will help.
>

Nice! I see you have Matplotlib and Pillow as well in
https://gitlab.com/Linaro/windowsonarm/packages. In case you plan to add
SciPy, please feel free to ping me there (Gitlab username ralfgommers,
GitHub rgommers). I have also added the Windows on ARM use case to our
cross-compiling tracker issue: https://github.com/scipy/scipy/issues/14812.

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] NumPy 1.23.0 released

2022-06-22 Thread Charles R Harris 
Hi All,

On behalf of the NumPy team, I'm pleased to announce the release of NumPy
1.23.0. The NumPy 1.23.0 release continues the ongoing work to improve the
handling and promotion of dtypes, increase the execution speed, clarify the
documentation, and expire old deprecations. The highlights are:


   - Implementation of ``loadtxt`` in C, greatly improving its performance.
   - Exposing DLPack at the Python level for easy data exchange.
   - Changes to the promotion and comparisons of structured dtypes.
   - Improvements to f2py.

The Python versions supported in this release are 3.8-3.10, 3.11 will be
supported when it comes out. Note that 32 bit wheels are only provided for
Windows, all other wheels are 64 bits on account of Ubuntu, Fedora, and
other Linux distributions dropping 32 bit support. All 64 bit wheels are
also linked with 64 bit OpenBLAS. Wheels can be downloaded from PyPI
; source archives, release notes,
and wheel hashes are available on Github
.

*Contributors*

A total of 151 people contributed to this release.  People with a "+" by
their
names contributed a patch for the first time.

   - @DWesl
   - @GalaxySnail +
   - @code-review-doctor +
   - @h-vetinari
   - Aaron Meurer
   - Alexander Shadchin
   - Alexandre de Siqueira
   - Allan Haldane
   - Amrit Krishnan
   - Andrei Batomunkuev
   - Andrew J. Hesford +
   - Andrew Murray +
   - Andrey Andreyevich Bienkowski +
   - André Elimelek de Weber +
   - Andy Wharton +
   - Arryan Singh
   - Arushi Sharma
   - Bas van Beek
   - Bharat Raghunathan
   - Bhavuk Kalra +
   - Brigitta Sipőcz
   - Brénainn Woodsend +
   - Burlen Loring +
   - Caio Agiani +
   - Charles Harris
   - Chiara Marmo
   - Cornelius Roemer +
   - Dahyun Kim +
   - Damien Caliste
   - David Prosin +
   - Denis Laxalde
   - Developer-Ecosystem-Engineering
   - Devin Shanahan +
   - Diego Wang +
   - Dimitri Papadopoulos Orfanos
   - Ding Liu +
   - Diwakar Gupta +
   - Don Kirkby +
   - Emma Simon +
   - Eric Wieser
   - Evan Miller +
   - Evgeni Burovski
   - Evgeny Posenitskiy +
   - Ewout ter Hoeven +
   - Felix Divo
   - Francesco Andreuzzi +
   - Ganesh Kathiresan
   - Gaëtan de Menten
   - Geoffrey Gunter +
   - Hans Meine
   - Harsh Mishra +
   - Henry Schreiner
   - Hood Chatham +
   - I-Shen Leong
   - Ilhan Polat
   - Inessa Pawson
   - Isuru Fernando
   - Ivan Gonzalez +
   - Ivan Meleshko +
   - Ivan Yashchuk +
   - Janus Heide +
   - Jarrod Millman
   - Jason Thai +
   - Jeremy Volkman +
   - Jesús Carrete Montaña +
   - Jhong-Ken Chen (陳仲肯) +
   - John Kirkham
   - John-Mark Gurney +
   - Jonathan Deng +
   - Joseph Fox-Rabinovitz
   - Jouke Witteveen +
   - Junyan Ou +
   - Jérôme Richard +
   - Kassian Sun +
   - Kazuki Sakamoto +
   - Kenichi Maehashi
   - Kevin Sheppard
   - Kilian Lieret +
   - Kushal Beniwal +
   - Leo Singer
   - Logan Thomas +
   - Lorenzo Mammana +
   - Margret Pax
   - Mariusz Felisiak +
   - Markus Mohrhard +
   - Mars Lee
   - Marten van Kerkwijk
   - Masamichi Hosoda +
   - Matthew Barber
   - Matthew Brett
   - Matthias Bussonnier
   - Matthieu Darbois
   - Matti Picus
   - Melissa Weber Mendonça
   - Michael Burkhart +
   - Morteza Mirzai +
   - Motahhar Mokf +
   - Muataz Attaia +
   - Muhammad Motawe +
   - Mukulika Pahari
   - Márton Gunyhó +
   - Namami Shanker +
   - Nihaal Sangha +
   - Niyas Sait
   - Omid Rajaei +
   - Oscar Gustafsson +
   - Ovee Jawdekar +
   - P. L. Lim +
   - Pamphile Roy +
   - Pantelis Antonoudiou +
   - Pearu Peterson
   - Peter Andreas Entschev
   - Peter Hawkins
   - Pierre de Buyl
   - Pieter Eendebak +
   - Pradipta Ghosh +
   - Rafael Cardoso Fernandes Sousa +
   - Raghuveer Devulapalli
   - Ralf Gommers
   - Raphael Kruse
   - Raúl Montón Pinillos
   - Robert Kern
   - Rohit Goswami
   - Ross Barnowski
   - Ruben Garcia +
   - Sadie Louise Bartholomew +
   - Saswat Das +
   - Sayed Adel
   - Sebastian Berg
   - Serge Guelton
   - Simon Surland Andersen +
   - Siyabend Ürün +
   - Somasree Majumder +
   - Soumya +
   - Stefan van der Walt
   - Stefano Miccoli +
   - Stephan Hoyer
   - Stephen Worsley +
   - Tania Allard
   - Thomas Duvernay +
   - Thomas Green +
   - Thomas J. Fan
   - Thomas Li +
   - Tim Hoffmann
   - Ting Sun +
   - Tirth Patel
   - Toshiki Kataoka
   - Tyler Reddy
   - Warren Weckesser
   - Yang Hau
   - Yoon, Jee Seok +

Cheers,

Charles Harris
___
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: NumPy 1.23.0 released

2022-06-22 Thread Charles R Harris 
On Wed, Jun 22, 2022 at 6:49 PM Charles R Harris 
wrote:

> Hi All,
>
> On behalf of the NumPy team, I'm pleased to announce the release of NumPy
> 1.23.0. The NumPy 1.23.0 release continues the ongoing work to improve the
> handling and promotion of dtypes, increase the execution speed, clarify the
> documentation, and expire old deprecations. The highlights are:
>
>
>- Implementation of ``loadtxt`` in C, greatly improving its
>performance.
>- Exposing DLPack at the Python level for easy data exchange.
>- Changes to the promotion and comparisons of structured dtypes.
>- Improvements to f2py.
>
> The Python versions supported in this release are 3.8-3.10, 3.11 will be
> supported when it comes out. Note that 32 bit wheels are only provided for
> Windows, all other wheels are 64 bits on account of Ubuntu, Fedora, and
> other Linux distributions dropping 32 bit support. All 64 bit wheels are
> also linked with 64 bit OpenBLAS. Wheels can be downloaded from PyPI
> ; source archives, release notes,
> and wheel hashes are available on Github
> .
>

 I included the buggy pdf doc files in the documentation. As
discussed before, we should probably just drop those from the website. It
looks like deleting two lines will remove the links, I'm not sure how to
remove the content and didn't try. It was enough trouble editing
the Makefile to ignore the bugs and run with Python 3.10. Deleting those
files has got to help the growing size of the numpy.org repo, which is
enormous these days.

Chuck
___
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