ee above for details.
14:27:24 ERRORBuildError: The custom build system failed.
```
So the build fails whilst trying to import the "features" module here:
https://github.com/numpy/numpy/blob/main/meson_cpu/x86/meson.build#L2C1-L3C1
Where is that module meant to be located?
Cheers,
T
3.13+ and not hurt anyone
> unless there's a major development.
> >
> > Little rant finished. :)
> > ___
> > NumPy-Discussion mailing list -- numpy-discussion@python.org
> > To unsubscribe send an email to numpy
o be specific and
fail early if the configured choice is not available in the build
environment. Pkgsrc is especially trying hard to avoid locating
libraries from the host system (possibly a full GNU/Linux distro) if
not explicitly told to.
Also, my H
could link the vendored
superly with -lblas without changing the meson machinery?
Alrighty then,
Thomas
--
Dr. Thomas Orgis
HPC @ Universität Hamburg
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-di
Am Sun, 3 Dec 2023 19:54:10 +0100
schrieb "Dr. Thomas Orgis" :
> > You have to go through a "build frontend" to produce a wheel, which then
> > gets installed/repackaged for your distro.
>
> This is obviously happening in pkgsrc.
>
> I'll
x27;])
So there's this elaborate machinery that special-cases BLAS as a
library that could (not) offer certain sets of API? Well, as long as
the dynamic libcblas is used, the base BLAS API should be transparently
avaible and those meson tests will work … ?
I'll do some testing tomorro
se-ilp64` flag. It will not work to
> craft a blas.pc which points at a 64-bit BLAS.
So -Dblas=openblas64 -Dlapack=openblas64 -Duse-ilp64 would do it, right?
Alrighty then,
Thomas
PS: You might want to fix that one:
../../numpy/meson.build:124: WARNING: Project targets '>=1.2.9
ild if a 64 variant is chosen by the user. I wonder a bit if there
are possible pitfalls combining other libraries with Python and
indirectly some incompatible BLAS variant via NumPy … but one point of
our user choice is that they could ensure that all packages really use
the same BLAS.
Alrighty t
Astropy is hiring a Research Software engineer. We are looking for people
who can spend 50-100% of their time on Astropy development in the next 6-9
months.
Qualified candidates can range from software developers with open source
experience to astronomy students with software experience.
*If you
you have any concrete example that might be worth taking
> a look at in more detail? Either for performance or accuracy.
>
> --
> Robert Kern
> ___
> NumPy-Discussion mailing list -- numpy-discussion@python.org
> To unsubscribe send an e
t;
> Cheers,
>
> Matthew
> ___
> 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/nump
t (which still
>> exists),
>
>
> What discrepancy?
>
> Cheers,
> Ralf
>
> ___
> NumPy-Discussion mailing list -- numpy-discussion@python.org
> To unsubscribe send an email to numpy-discussion-le...@python.org
> http
o merge PRs. And having to
> wait longer for new Python features is also annoying.
>
> Aaron Meurer
> ___
> NumPy-Discussion mailing list -- numpy-discussion@python.org
> To unsubscribe send an email to numpy-discussion-le...@python.org
woutH)
>> ___
>> 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-discussio
Sand Point Way NE (206) 526-6329 fax
> > Seattle, WA 98115 (206) 526-6317 main reception
> >
> > chris.bar...@noaa.gov <mailto:chris.bar...@noaa.gov>
>
>
> Just an empty response since this ended up in my spam filter, and I am
> probably not the on
When I understand correctly and what you desire is equivalent to integer
overflowing, the function can indeed be applied as well.
I tested.
But to be sure, maybe some examples are better.
Am Do., 20. Mai 2021 um 03:22 Uhr schrieb ZinGer_KyoN :
> I have similar needs, but for int array and integer
this is of interest, I can contribute.
Best regards,
Thomas.
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion
> wrote:
>
>> On 24/11/2020 10:25, Thomas wrote:
>> > Like Nathaniel said, it would not improve much when compared to the
>> > modulo operator.
>> >
>> > It could handle the edge cases better, but really the biggest benefit
>> > would
ng something so
> trivial as a function to numpy: I cannot think to any commonly used
> algorithm that requires wrapping the phase, and it is going to be an
> infinite source of bikesheeding whether the wrapped range should be
> [-pi, pi) or (-pi, pi] or (0, 2*pi] or [0, 2*pi)
>
Hi,
I have a proposal for a feature and I hope this is the right place to post
this.
The idea is to have a function to map any input angle to the range of [ 0,
2*pi ] or [ - pi, pi ].
There already is a function called 'unwrap' that does the opposite, so I'd
suggest calling this function 'wrap'.
Matplotlib has also migrated to building wheels via github actions and it
has been working well.
Tom
On Mon, Nov 16, 2020, 17:48 Andrew Nelson wrote:
> For my project (refnx) I solely use GH Actions to test and make wheels. In
> my workflow (
> https://github.com/refnx/refnx/blob/master/.github
not sure it's clearer, the current NEP has a nice graphic and
>> > > literally says "a project with a major or minor version release in
>> > > November 2020 should support Python 3.7 and newer."). However happy
>> > > to adopt it if it makes others happy - in the end it comes down to
>> > > the same thing: it's recommended to drop Python 3.6 now.
>> > >
>> > > > My personal opinion is that somewhere in the range of 24-36
>> > > > months would be appropriate.
>> > >
>> > > +1
>> > >
>> > > Cheers,
>> > > Ralf
>> > >
>> > >
>> > >
>> > > ___
>> > > NumPy-Discussion mailing list
>> > > NumPy-Discussion@python.org
>> > > https://mail.python.org/mailman/listinfo/numpy-discussion
>> > >
>> >
>> > ___
>> > NumPy-Discussion mailing list
>> > NumPy-Discussion@python.org
>> > https://mail.python.org/mailman/listinfo/numpy-discussion
>>
>> ___
>> NumPy-Discussion mailing list
>> NumPy-Discussion@python.org
>> https://mail.python.org/mailman/listinfo/numpy-discussion
>>
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
--
Thomas Caswell
tcasw...@gmail.com
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion
goal? So far it is convenient that all the repos that upload
> to https://anaconda.org/multibuild-wheels-staging are under one org to
> coordinate upload token use.
>
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@python.or
; > ___
> > NumPy-Discussion mailing list
> > NumPy-Discussion@python.org
> > https://mail.python.org/mailman/listinfo/numpy-discussion
>
> ___
> NumPy-Discussion mailing l
are is
>> > used".
>> >
>> > Many thanks to all of the contributors who have put so much time and
>> > energy into NumPy. ✨ ❤️ 😃
>> >
>> > [1] https://github.com/gazprom-neft/petroflow
>> > [2] https://github.com/climate-strike/analysis
>> > [3] https://github.com/climate-strike/license
>> > ___
>> > NumPy-Discussion mailing list
>> > NumPy-Discussion@python.org
>> > https://mail.python.org/mailman/listinfo/numpy-discussion
>> >
>>
>> ___
>> NumPy-Discussion mailing list
>> NumPy-Discussion@python.org
>> https://mail.python.org/mailman/listinfo/numpy-discussion
>>
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
--
Thomas Caswell
tcasw...@gmail.com
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion
Our organization is still using CentOS-6, so my vote is for that.
Thanks,
Tom
On Tue, Feb 4, 2020 at 5:38 PM Nathaniel Smith wrote:
> Pretty sure the 2010 and 2014 images both have much newer compilers than
> that.
>
> There are still a lot of users on CentOS 6, so I'd still stick to 2010 for
>
below
for a link to the full job description and application instructions.
The timeline on this is rather short, so applications are due Jan 3.
https://discourse.matplotlib.org/t/now-hiring-matplotlib-research-software-engineering-fellow/20701
Tom and Hannah
--
Thomas Caswell
tcasw...@gmail.com
; see NEP 0 for more details.
Tom
--
Thomas Caswell
tcasw...@gmail.com
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion
as there are many interested parties (from the other
projects) that may not be subscribed to the numpy mailing list.
Tom
--
Thomas Caswell
tcasw...@gmail.com
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman
On Sat, Jun 22, 2019 at 11:51 AM Marten van Kerkwijk <
m.h.vankerkw...@gmail.com> wrote:
> Hi Allan,
>
> I'm not sure I would go too much by what the old MaskedArray class did. It
> indeed made an effort not to overwrite masked values with a new result,
> even to the extend of copying back masked
Hi Ralf,
On Sun, 6 Jan 2019 at 22:06, Ralf Gommers wrote:
>
>
>
> On Sun, Jan 6, 2019 at 12:45 PM Thomas Robitaille
> wrote:
>>
>> Hi all,
>>
>> Back in December I started getting failures in continuous integration
>> as well as reports of fai
Hi all,
Back in December I started getting failures in continuous integration
as well as reports of failures from users of installation issues for a
couple of packages. The problem can be easily reproduced in a Docker
container with:
FROM ubuntu:16.04
RUN apt-get update
RUN apt-get insta
I suspect this is due to issues with sphinx 1.8.0. Matplotlib also has
this problem (see https://github.com/matplotlib/matplotlib/pull/12183).
Tom
On Mon, Sep 17, 2018 at 10:47 AM Matti Picus wrote:
> I can enter a search term (say `ndarray`) in
> www.numpy.org/devdocs/search.html, but the res
I think the NEP does a very good job of capturing the high-level issue
around duck arrays and will serve as a solid base to build future
discussions on.
With my Matplotlib and h5py hats on, I like the discussion about how down
stream projects need to work out their issues with the support of the N
/ twice, the
browser helpfully added (1) to the name, when I when to upload everything
twine got half way through and failed out on that file. I thought it had
done everything else, but it had actually only done everything up to that
file.
On Tue, Sep 18, 2018 at 8:43 PM Thomas Caswell wrote:
> Fo
Folks,
Happy to announce Matplotlib 3.0.0!
This is the first version of Matplotlib to only support Python 3.
If you need Python 2.7 support the 2.2.x LTS series will continue to
receive critical bug-fixes until 2020.
Highlights of this release include:
- GUI backend is selected at run-time ba
Yes, meant IntFlag :sheep:
On Sat, Mar 17, 2018 at 6:02 PM Hameer Abbasi
wrote:
>
> It would be nice if there was an IntEnum [1] that was taken is an input to
> `np.asarrayish` and `np.isarrayish` to require a combination of the groups
> of attributes/methods/semantics.
>
>
> Don’t you mean IntF
It would be nice if there was an IntEnum [1] that was taken is an input to
`np.asarrayish` and `np.isarrayish` to require a combination of the groups
of attributes/methods/semantics.
Tom
[1] https://docs.python.org/3/library/enum.html#intenum
On Sat, Mar 10, 2018 at 7:14 PM Marten van Kerkwijk <
Yes I like the name.
The primary use-case for Matplotlib is that our `hist` method can take in a
list of arrays and produces N histograms in one shot. Currently with 'auto'
we only use the first data set to sort out what the bins should be and then
re-use those for the rest of the data sets. This
As commented in the OP, this would be very useful for Matplotlib.
Tom
On Fri, Mar 9, 2018 at 1:42 PM Kirit Thadaka
wrote:
> Hi!
>
> I've created a PR to add a function called "histogram_bin_edges" which
> will allow a user to calculate the bins used by the histogram for some data
> without requ
This has recently been a major point point for Matplotlib for the
implementation of string-categoricals as well.
Having numpy go to object or fail on `np.asarray([1, 2, 'foo'])` would make
things much easier for us.
Tom
On Fri, Feb 9, 2018 at 2:22 AM Stephan Hoyer wrote:
> On Thu, Feb 8, 2018
I have been building numpy master with CPython master but am also using
cython master.
My not-pretty script for doing this is:
#! /usr/bin/bash
set -e
TARGET_ENV=bleeding
OSPATH=~/source/other_source/
pushd $OSPATH/cpython/
git pull
git clean -xfd
./configure
make -j 9
./python -m venv --copies
Folks,
Happy to announce Matplotlib 2.1.1
This is primarily a bug fix release, see
https://github.com/matplotlib/matplotlib/releases/tag/v2.1.1 for details.
The next planned release is a 2.2 feature release in January/February
2018.
Thank you to everyone who worked on this release!
Tom
___
I am in very supportive of this plan.
For Matplotlib the intention is to do a mpl2.2LTS early 2018 and a mpl3.0
(no major API breaks other than dropping py2 support) summer 2018 with the
same meaning of LTS.
I also had thought about bumping the minimum numpy version of Matplotlib to
the first py3
On 08/10/17 22:50, Thomas Jollans wrote:
> On 08/10/17 09:12, Nissim Derdiger wrote:
>> Hi again,
>> I realize that my question was not clear enough, so I've refined it into one
>> runnable function (attached below)
>> My question is basically - is there a way to
On 08/10/17 09:12, Nissim Derdiger wrote:
> Hi again,
> I realize that my question was not clear enough, so I've refined it into one
> runnable function (attached below)
> My question is basically - is there a way to perform the same operation, but
> faster using NumPy (or even just by using Pyth
We are happy to announce the release of Matplotlib 2.1. This is the second
minor release in the Matplotlib 2.x series and the first release with major
new features since 1.5.
This release contains approximately 2 years worth of work by 275
contributors
across over 950 pull requests. Highlights fr
get the integers.
>
> tx.
> R.
>
>
> --
> Renato Fabbri
> GNU/Linux User #479299
> labmacambira.sourceforge.net <http://labmacambira.sourceforge.net>
>
>
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@python.org
> https://mail.python.org/mailman
It seems major versions are in the air!
For matplotlib 2.0 we put together
http://matplotlib.org/users/dflt_style_changes.html for the style changes
which shows the new behavior, the old behavior, and how to get the old
behavior back.
Tom
On Sun, Sep 17, 2017 at 10:48 AM Ilhan Polat wrote:
>
py is false, if y is a memmap and in that case return a full memmap
> object
> instead of slicing it?
>
> Best wishes
> Isaia
>
> P.S. A longer account of the issue may be found on my university blog
> http://www.im.ufrj.br/nisoli/blog/?p=131
>
> --
> Isaia Nisoli
>
>
>
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
--
Thomas Jollans
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion
Going with option 2 is probably the best option so that you can use pytest
fixtures and parameterization.
Might be worth looking at how Matplotlib re-arranged things on our master
branch to maintain back-compatibility with nose-specific tools that were
used by down-stream projects.
Tom
On Tue, J
Are you tied to ASCII files? HDF5 (via h5py or pytables) might be a
better storage format for what you are describing.
Tom
On Wed, Jul 5, 2017 at 8:42 AM wrote:
> Dear all
>
>
> I’m sorry if my question is too basic (not fully in relation to Numpy –
> while it is to build matrices and to work
note that another part of the discussion previously suggested that we
> have a dtype that wraps a native python string object -- then you'd
> get all for free. This is essentially an object array with strings in
> it, which you can do now.
>
> -CHB
>
>
> --
>
>
t; should be possible to use directly on normal integer arrays without
> conversions to other array types.
> So I personally don't realy get why the need of additional chararray type,
> Its all numbers anyway and it's up to the programmer to
> decide what size of translation tables/value ranges he wants to use.
chararray is deprecated.
> There can be some convinience methods for ascii operations,
> like eg char.toupper(), but currently they don't seem to work with integer
> arrays so why not make those potentially useful methots usable
> and make them work on normal integer arrays?
I don't know what you're doing, but I don't think numpy is normally the
right tool for text manipulation...
> [snip]
>
> as a side-note, I don't think that encoding should be assumed much for
> creating new array types, it is up to the programmer
> to decide what 'meanings' the bytes have.
Agreed!
-- Thomas
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion
On Tue, Apr 25, 2017 at 7:11 PM, Chris Barker - NOAA Federal <
chris.bar...@noaa.gov> wrote:
> > On Apr 25, 2017, at 12:38 PM, Nathaniel Smith wrote:
>
> > Eh... First, on Windows and MacOS, filenames are natively Unicode.
>
> Yeah, though once they are stored I. A text file -- who the heck
> kno
On Mon, Apr 24, 2017 at 7:11 PM, Robert Kern wrote:
> On Mon, Apr 24, 2017 at 4:06 PM, Aldcroft, Thomas <
> aldcr...@head.cfa.harvard.edu> wrote:
> >
> > On Mon, Apr 24, 2017 at 4:06 PM, Robert Kern
> wrote:
> >>
> >> I am not unfamiliar with this
On Mon, Apr 24, 2017 at 4:06 PM, Robert Kern wrote:
> I am not unfamiliar with this problem. I still work with files that have
> fields that are supposed to be in EBCDIC but actually contain text in
> ASCII, UTF-8 (if I'm lucky) or any of a variety of East European 8-bit
> encodings. In that expe
On Mon, Apr 24, 2017 at 2:47 PM, Robert Kern wrote:
> On Mon, Apr 24, 2017 at 10:51 AM, Aldcroft, Thomas <
> aldcr...@head.cfa.harvard.edu> wrote:
> >
> > On Mon, Apr 24, 2017 at 1:04 PM, Chris Barker
> wrote:
>
> >> - round-tripping of binary data (at
On Mon, Apr 24, 2017 at 1:04 PM, Chris Barker wrote:
> On Fri, Apr 21, 2017 at 2:34 PM, Stephan Hoyer wrote:
>
>
>> In this case, we want something compatible with Python's string (i.e.
>>> full Unicode supporting) and I think should be as transparent as possible.
>>> Python's string has made th
59 matches
Mail list logo
