/
On Mon, May 6, 2024 at 9:10 AM Stanley Seibert
wrote:
> The Beeware (https://beeware.org/) developers build NumPy (and other
> binary extension packages) for mobile operating systems, both iOS and
> Android. You can see their scripts and build recipes here:
>
> https://github.com
The Beeware (https://beeware.org/) developers build NumPy (and other binary
extension packages) for mobile operating systems, both iOS and Android.
You can see their scripts and build recipes here:
https://github.com/beeware/mobile-forge
In particular, you can see the patch they need to make to t
On Thu, Aug 19, 2021 at 2:13 AM Jerry Morrison <
jerry.morrison+nu...@gmail.com> wrote:
>
> I'll put forth an expectation that after installing a specific set of
> libraries, the floating point results would be identical across platforms
> and into the future. Ideally developers could install libr
The development version of NumPy from Github requires Python 3.7 or later.
On Fri, Dec 11, 2020 at 1:35 PM Lianyuan Zheng wrote:
> Hello,
>
> On my linux server, I downloaded the NUMPY package from GitHub (git clone
> https://github.com/numpy/numpy.git) and then accessed the directory
> "numpy".
I think it is important to acknowledge that, regardless of the merits of
such a license change on its own, NumPy's position in the dependency stack
of PyData makes a license change that restricts an existing class of users
impossible without causing a lot of chaos for non-NumPy developers who may
n
In addition to what Sebastian said about memory fragmentation and OS limits
about memory allocations, I do think it will be hard to work with an array
that close to the memory limit in NumPy regardless. Almost any operation
will need to make a temporary array and exceed your memory limit. You
mig
Just to chime in: Numba would definitely appreciate C functions to access
the random distribution implementations, and have a side-project
(numba-scipy) that is making the Cython wrapped functions in SciPy visible
to Numba.
On Thu, Sep 19, 2019 at 5:41 AM Kevin Sheppard
wrote:
>
>
> On Thu, Sep
(Full disclosure: I work on Numba...)
Just to note, the NumPy implementation will allocate (and free) more than 2
arrays to compute that expression. It has to allocate the result array for
each operation as Python executes. That expression is equivalent to:
s1 = newfactor * x
s2 = np.exp(s1)
s3
On Thu, Sep 13, 2018 at 9:48 AM, Charles R Harris wrote:
>
> On Thu, Sep 13, 2018 at 8:30 AM Stanley Seibert
> wrote:
>
>> Another minor annoyance is that the link on the Github "Checks" page that
>> says "View More Details on Azure Pipelines" takes
u can view the build
results for public projects without a Microsoft account, so you'll probably
want to put a build status badge with a direct link somewhere prominent in
the README.
On Thu, Sep 13, 2018 at 9:25 AM, Stanley Seibert
wrote:
> I'm still trying to wrap my head aro
ser's account,
or by installing it as an "app" in the Github organization, which is the
route I opted for.
On Thu, Sep 13, 2018 at 8:13 AM, Charles R Harris wrote:
>
>
> On Wed, Sep 12, 2018 at 7:30 PM Stanley Seibert
> wrote:
>
>>
>>
>> On Wed, Sep 12, 201
On Wed, Sep 12, 2018 at 7:32 PM, Charles R Harris wrote:
>
>
> On Wed, Sep 12, 2018 at 6:26 PM Stanley Seibert
> wrote:
>
>> If you go beyond the free tier, you can connect self-managed build
>> workers to the same system, but the build agent is written in C#, so I&#x
Also, if anyone is curious what the CI interface looks like for the results
of a finished build, here's the Numba build from that PR:
https://dev.azure.com/numba/numba/_build/results?buildId=34&view=logs
On Wed, Sep 12, 2018 at 7:25 PM, Stanley Seibert
wrote:
> I just finished ad
I just finished adding support to the Numba repo for Azure Pipelines:
https://github.com/numba/numba/pull/3303
The "free for open source" tier is 10 concurrent jobs that can run up to 60
minutes each (although the website says 30 minutes), and no limit on
minutes per month. Like the other CI ser
14 matches
Mail list logo
