Re: [Numpy-discussion] Proposal of timeline for dropping Python 2.7 support

On Fri, Nov 10, 2017 at 2:52 PM, Nathaniel Smith wrote: > Fortunately we can wait until we're a bit closer before we have to > make any final decision on the version numbering :-) > > Right now though it would be good to start communicating to > users/downstreams about whatever our plans our thou

Re: [Numpy-discussion] Proposal of timeline for dropping Python 2.7 support

On Tue, Nov 14, 2017 at 7:58 AM, Thomas Caswell wrote: > 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 a

Re: [Numpy-discussion] Deprecate matrices in 1.15 and remove in 1.17?

On Fri, Dec 1, 2017 at 7:17 AM, Matthew Rocklin wrote: > How would the community handle the scipy.sparse matrix subclasses? These > are still in common use. > They're not going anywhere for quite a while (until the sparse ndarrays materialize at least). Hence np.matrix needs to be moved, not de

Re: [Numpy-discussion] Deprecate matrices in 1.15 and remove in 1.17?

On Fri, Dec 1, 2017 at 8:39 AM, Charles R Harris wrote: > > > On Thu, Nov 30, 2017 at 11:43 AM, Ralf Gommers > wrote: > >> >> >> On Fri, Dec 1, 2017 at 7:17 AM, Matthew Rocklin >> wrote: >> >>> How would the community handle the scipy.spars

Re: [Numpy-discussion] Deprecate matrices in 1.15 and remove in 1.17?

On Sat, Dec 2, 2017 at 7:03 AM, Chris Barker wrote: > On Thu, Nov 30, 2017 at 11:58 AM, Marten van Kerkwijk < > m.h.vankerkw...@gmail.com> wrote: > >> Your point about not doing things in the python 2->3 move makes sense; >> > > But this is NOT the 2->3 move -- numpy as been py3 compatible for ye

Re: [Numpy-discussion] NEP process update

On Wed, Dec 6, 2017 at 12:31 PM, Jarrod Millman wrote: > Hi all, > > Since we expect to be writing some NEPs in the near future, Nathaniel > and I were looking at how they're organized, and realized that the > process is a bit underspecified and it's a hard to tell the status of > things. > > So

Re: [Numpy-discussion] NEP process update

On Wed, Dec 6, 2017 at 1:49 PM, Nathaniel Smith wrote: > On Tue, Dec 5, 2017 at 4:12 PM, Ralf Gommers > wrote: > > On Wed, Dec 6, 2017 at 12:31 PM, Jarrod Millman > > wrote: > >> Assuming that sounds good, my tentative next steps are: > >> > >> -

Re: [Numpy-discussion] NEP process update

On Wed, Dec 6, 2017 at 2:58 PM, Jarrod Millman wrote: > I was planning on looking at/working on the main doc generating system > and the main webpage (for numpy and scipy) soon (over the winter > break), but I didn't want to get too many things in the discussion > right now. My immediate interes

Re: [Numpy-discussion] NEP process update

On Wed, Dec 6, 2017 at 5:39 PM, wrote: > > > On Tue, Dec 5, 2017 at 10:44 PM, Nathaniel Smith wrote: > >> On Tue, Dec 5, 2017 at 5:32 PM, Ralf Gommers >> wrote: >> > >> > >> > On Wed, Dec 6, 2017 at 1:49 PM, Nathaniel Smith wrote: >>

Re: [Numpy-discussion] Numpy 1.14.x has been branch, master is open for 1.15 development.

On Sat, Dec 9, 2017 at 9:28 AM, Charles R Harris wrote: > Hi All, > > Just a heads up that NumPy 1.14.x has been branched. > Thanks Chuck! Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/nump

Re: [Numpy-discussion] Directives in numpy docstring convention

On Mon, Dec 25, 2017 at 7:51 AM, Marc Garcia wrote: > Hi there, > > Is there a reason why the numpy docstring convention doesn't use the > sphinx directives .. deprecated:: [1] and .. seealso:: [2]? > > I see that the numpy convention [3] uses the .. note:: directive for the > deprecation notes,

[Numpy-discussion] GSoC'18 participation

Hi all, It's the time of the year again where projects start preparing for GSoC. So I wanted to bring it up here. Last year I wrote: "in practice working on NumPy is just far too hard for most GSoC students. Previous years we've registered and generated ideas, but not gotten any students. We're al

Re: [Numpy-discussion] NEP process PR

On Wed, Dec 13, 2017 at 11:45 AM, Jarrod Millman wrote: > Hi all, > > I've started working on the proposal discussed in this thread: > https://mail.python.org/pipermail/numpy-discussion/ > 2017-December/077481.html > here: > https://github.com/numpy/numpy/pull/10213 Thanks Jarrod! Stefan,

Re: [Numpy-discussion] NumPy 1.14.0 release

On Sun, Jan 7, 2018 at 2:00 PM, Charles R Harris wrote: > Hi All, > > On behalf of the NumPy team, I am pleased to announce NumPy 1.14.0. > Thanks for doing the heavy lifting to get this release out the door Chuck! Ralf ___ NumPy-Discussion mailing li

Re: [Numpy-discussion] improving arange()? introducing fma()?

On Wed, Feb 7, 2018 at 2:57 AM, Benjamin Root wrote: > Note, the following is partly to document my explorations in computing > lat/on grids in numpy lately, in case others come across these issues in > the future. It is partly a plea for some development of numerically > accurate functions for c

Re: [Numpy-discussion] Hoop jumping, and other sports

On Wed, Feb 7, 2018 at 11:29 PM, Stefan van der Walt wrote: > On Wed, 07 Feb 2018 14:26:37 -0700, Charles R Harris wrote: > > I was thinking about things to do to simplify the NumPy development > > process. One thing that came to mind was our use of prefixes on commits, > > BUG, TST, etc. Those p

Re: [Numpy-discussion] Hoop jumping, and other sports

On Thu, Feb 8, 2018 at 11:32 AM, Peter Cock wrote: > On Thu, Feb 8, 2018 at 11:22 AM, Ralf Gommers > wrote: > > On Wed, Feb 7, 2018 at 11:29 PM, Stefan van der Walt < > stef...@berkeley.edu> > > wrote: > >> > >> For scikit-image, we've star

Re: [Numpy-discussion] @xoviat

On Mon, Feb 12, 2018 at 7:42 PM, Charles R Harris wrote: > Anyone know what happened to xoviat? He seems to have been disappeared. > His account was flagged by GitHub after scipy issue gh-8373. Flagging means your profile, and all your issue comments, PRs, etc. are all made private. It is quite

Re: [Numpy-discussion] Permissable NumPy logo usage

On Fri, Feb 16, 2018 at 12:28 PM, Stephan Hoyer wrote: > I don't know the history of the NumPy logo, or who officially owns the > rights to NumPy's branding at this point. In principle, that might be > NumFOCUS, but the logo far predates NumFOCUS and NumFOCUS's fiscal > sponsorship of NumPy. Look

Re: [Numpy-discussion] Where to discuss NEPs (was: Re: new NEP: np.AbstractArray and np.asabstractarray)

On Thu, Mar 8, 2018 at 8:22 PM, Nathaniel Smith wrote: > On Thu, Mar 8, 2018 at 7:06 AM, Marten van Kerkwijk > wrote: > > Hi Nathaniel, > > > > Overall, hugely in favour! For detailed comments, it would be good to > > have a link to a PR; could you put that up? > > Well, there's a PR here: http

Re: [Numpy-discussion] Where to discuss NEPs (was: Re: new NEP: np.AbstractArray and np.asabstractarray)

On Fri, Mar 9, 2018 at 12:00 AM, Nathaniel Smith wrote: > On Thu, Mar 8, 2018 at 10:26 PM, Ralf Gommers > wrote: > > > > > > On Thu, Mar 8, 2018 at 8:22 PM, Nathaniel Smith wrote: > >> > >> On Thu, Mar 8, 2018 at 7:06 AM, Marten van

Re: [Numpy-discussion] ENH: softmax

On Wed, Mar 14, 2018 at 1:41 AM, Robert Kern wrote: > On Wed, Mar 14, 2018 at 5:22 PM, Warren Weckesser < > warren.weckes...@gmail.com> wrote: > > > > On Wed, Mar 14, 2018 at 4:05 AM, Kulick, Johannes > wrote: > >> > >> Hi, > >> > >> I regularly need the softmax function (https://en.wikipedia.or

Re: [Numpy-discussion] NumPy 1.15 release schedule

On Mon, Mar 12, 2018 at 11:44 AM, Charles R Harris < charlesr.har...@gmail.com> wrote: > Hi All, > > I'm thinking of branching NumPy in the middle/end of April. That is > quicker than usual, but there don't seem to be any major changes proposed > for the near future, we have merged a reasonable nu

[Numpy-discussion] ANN: SciPy 1.0.1 released

compared to 1.0.0. Probably the most important change is a fix for an incompatibility between SciPy 1.0.0 and ``numpy.f2py`` in the NumPy master branch. Authors === * Saurabh Agarwal + * Alessandro Pietro Bardelli * Philip DeBoer * Ralf Gommers * Matt Haberland * Eric Larson * Denis Laxalde

[Numpy-discussion] ANN: numpydoc 0.8.0 release

Hi all, I'm pleased to announce that a new release of numpydoc is available: - package: https://pypi.python.org/pypi/numpydoc - documentation (new in this release): https://numpydoc.readthedocs.io/en/latest/ This is a maintenance release with many small improvements. Likely your documentation wil

Re: [Numpy-discussion] NumPy sprint May 24-25 at BIDS and virtual meetup tomorrow

On Tue, Apr 24, 2018 at 7:07 AM, Charles R Harris wrote: > > > On Tue, Apr 24, 2018 at 12:55 AM, Matti Picus > wrote: > >> We will take advantage of a few NumPy developers being at Berkeley to >> hold a two day sprint May 24-25 https://scisprints.github.io/# >> may-numpy-developer-sprint. >> Eve

Re: [Numpy-discussion] Changing the return type of np.histogramdd

On Mon, Apr 9, 2018 at 10:24 PM, Eric Wieser wrote: > Numpy has three histogram functions - histogram, histogram2d, and > histogramdd. > > histogram is by far the most widely used, and in the absence of weights > and normalization, returns an np.intp count for each bin. > > histogramdd (for which

Re: [Numpy-discussion] Changing the return type of np.histogramdd

t I suppose that can be dealt with separately. > > Eric > ​ > > On Wed, 25 Apr 2018 at 21:57 Ralf Gommers wrote: > >> On Mon, Apr 9, 2018 at 10:24 PM, Eric Wieser > > wrote: >> >>> Numpy has three histogram functions - histogram, histogram2d, and >>

Re: [Numpy-discussion] Changing the return type of np.histogramdd

ross-link for convolve: https://docs.scipy.org/doc/numpy-1.14.0/reference/generated/numpy.convolve.html Ralf > ​ > > On Wed, 25 Apr 2018 at 22:51 Ralf Gommers wrote: > >> On Wed, Apr 25, 2018 at 10:07 PM, Eric Wieser < >> wieser.eric+nu...@gmail.com> wrote: >> &g

Re: [Numpy-discussion] Splitting MaskedArray into a separate package

On Wed, May 23, 2018 at 12:06 PM, Matti Picus wrote: > MaskedArray is a strange but useful creature. This NEP proposes to > distribute it as a separate package under the NumPy brand. > > As I understand the process, a proposed NEP should be first discussed here > to gauge general acceptance, then

Re: [Numpy-discussion] Splitting MaskedArray into a separate package

On Wed, May 23, 2018 at 1:03 PM, Stefan van der Walt wrote: > On Wed, 23 May 2018 12:29:32 -0700, Ralf Gommers wrote: > > >> * Compatibility: MaskedArray objects, being subclasses of `ndarrays`, > > >>often cause complications when being used with other packa

Re: [Numpy-discussion] Where to discuss NEPs (was: Re: new NEP: np.AbstractArray and np.asabstractarray)

On Tue, May 29, 2018 at 9:24 AM, Charles R Harris wrote: > > > On Tue, May 29, 2018 at 9:46 AM, Stephan Hoyer wrote: > >> Reviving this discussion -- >> I don't really care what our policy is, but can we make a decision one >> way or the other about where we discuss NEPs? We've had a revival of

Re: [Numpy-discussion] A roadmap for NumPy - longer term planning

On Thu, May 31, 2018 at 4:50 PM, Matti Picus wrote: > At the recent NumPy sprint at BIDS (thanks to those who made the trip) we > spent some time brainstorming about a roadmap for NumPy, in the spirit of > similar work that was done for Jupyter. The idea is that a document with > wide community a

Re: [Numpy-discussion] A roadmap for NumPy - longer term planning

On Fri, Jun 1, 2018 at 9:57 AM, Stefan van der Walt wrote: > Hi Ralf, > > On Thu, 31 May 2018 21:57:06 -0700, Ralf Gommers wrote: > > - "internal refactorings": MaskedArray yes, but the other ones no. > > numpy.distutils and f2py are very hard to test, a big refact

Re: [Numpy-discussion] NEP: Random Number Generator Policy

On Sun, Jun 3, 2018 at 6:54 PM, wrote: > > > On Sun, Jun 3, 2018 at 9:08 PM, Robert Kern wrote: > >> On Sun, Jun 3, 2018 at 5:46 PM wrote: >> >>> >>> >>> On Sun, Jun 3, 2018 at 8:21 PM, Robert Kern >>> wrote: >>> The list of ``StableRandom`` methods should be chosen to support unit >

Re: [Numpy-discussion] NEP: Random Number Generator Policy

On Mon, Jun 4, 2018 at 3:18 PM, Robert Kern wrote: > On Sun, Jun 3, 2018 at 8:22 PM Ralf Gommers > wrote: > >> It may be worth having a look at test suites for scipy, statsmodels, >> scikit-learn, etc. and estimate how much work this NEP causes those >> projects. If

Re: [Numpy-discussion] NEP: Random Number Generator Policy

On Sun, Jun 3, 2018 at 9:23 PM, Warren Weckesser wrote: > > > On Sun, Jun 3, 2018 at 11:20 PM, Ralf Gommers > wrote: > >> >> >> On Sun, Jun 3, 2018 at 6:54 PM, wrote: >> >>> >>> >>> On Sun, Jun 3, 2018 at 9:08 PM, Robe

Re: [Numpy-discussion] NEP: Random Number Generator Policy

On Sun, Jun 10, 2018 at 6:08 PM, Robert Kern wrote: > On Sun, Jun 10, 2018 at 5:27 PM Ralf Gommers > wrote: > > > > On Mon, Jun 4, 2018 at 3:18 PM, Robert Kern > wrote: > >> > >> On Sun, Jun 3, 2018 at 8:22 PM Ralf Gommers > wrote: > >>>

Re: [Numpy-discussion] NEP: Random Number Generator Policy

On Sun, Jun 10, 2018 at 5:57 PM, Robert Kern wrote: > On Sun, Jun 10, 2018 at 5:47 PM Ralf Gommers > wrote: > > > > On Sun, Jun 3, 2018 at 9:23 PM, Warren Weckesser < > warren.weckes...@gmail.com> wrote: > > >> I suspect many of the tests will be easy to u

Re: [Numpy-discussion] NEP: Random Number Generator Policy

On Sun, Jun 10, 2018 at 10:36 PM, Robert Kern wrote: > On Sun, Jun 10, 2018 at 8:04 PM Ralf Gommers > wrote: > > > > On Sun, Jun 10, 2018 at 6:08 PM, Robert Kern > wrote: > >> > >> On Sun, Jun 10, 2018 at 5:27 PM Ralf Gommers > wrote: > >> &

Re: [Numpy-discussion] NEP: Random Number Generator Policy

On Sun, Jun 10, 2018 at 11:15 PM, Robert Kern wrote: > On Sun, Jun 10, 2018 at 8:11 PM Ralf Gommers > wrote: > > > > On Sun, Jun 10, 2018 at 5:57 PM, Robert Kern > wrote: > >> > >> On Sun, Jun 10, 2018 at 5:47 PM Ralf Gommers > wrote: > >&

Re: [Numpy-discussion] NEP: Random Number Generator Policy

On Sat, Jun 16, 2018 at 12:38 AM, Robert Kern wrote: > I have incorporated the feedback from this thread, and have significantly > altered the proposal. I think this version will be more palatable to > everyone. > > https://github.com/numpy/numpy/pull/11356 > https://github.com/rkern/numpy/bl

[Numpy-discussion] Fwd: [NumFOCUS Projects] NumFOCUS Summit Registration

Hi all, In September the NumFOCUS Summit for 2018 will be held in New York. NumPy can send one representative (or a couple, but costs are only covered for one person). We opened this opportunity up to members of the Steering Council first, however it doesn't look like anyone is in the position to

Re: [Numpy-discussion] NumPy 1.15.0rc1 released

On Sun, Jul 8, 2018 at 7:35 PM, Sandro Tosi wrote: > > The Python versions supported by this release are 2.7, 3.4-3.6. The > wheels are linked with > > OpenBLAS 3.0, which should fix some of the linalg problems reported for > NumPy 1.14, > > and the source archives were created using Cython 0.28

Re: [Numpy-discussion] Proposal to accept NEP 19: Random Number Generator Policy

On Tue, Jul 3, 2018 at 4:34 PM, Robert Kern wrote: > There has been one clarification to the text: > > https://github.com/numpy/numpy/pull/11488 > > For the legacy RandomState, we will *not* be fixing correctness bugs if > they doing so would break the stream; this is in contrast with the curre

Re: [Numpy-discussion] Fwd: [NumFOCUS Projects] NumFOCUS Summit Registration

On Wed, Jul 11, 2018 at 3:49 PM, Matti Picus wrote: > On 06/07/18 00:54, Ralf Gommers wrote: > >> Hi all, >> >> In September the NumFOCUS Summit for 2018 will be held in New York. NumPy >> can send one representative (or a couple, but costs are only covered for

Re: [Numpy-discussion] Fwd: [NumFOCUS Projects] NumFOCUS Summit Registration

On Sun, Jul 15, 2018 at 3:02 PM, Ralf Gommers wrote: > > > On Wed, Jul 11, 2018 at 3:49 PM, Matti Picus > wrote: > >> On 06/07/18 00:54, Ralf Gommers wrote: >> >>> Hi all, >>> >>> In September the NumFOCUS Summit for 2018 will be held in

[Numpy-discussion] nominations sought for NumFOCUS board of directors

Hi all, Not everyone may be on a NumFOCUS mailing list or read Planet SciPy/Python, so I thought it'd be good to point this out: https://www.numfocus.org/blog/numfocus-to-hold-2018-elections-for-board-of-directors >From my perspective, it would be great to see some candidates who are actively inv

[Numpy-discussion] backwards compatibility and deprecation policy NEP

ion policy === :Author: Ralf Gommers :Status: Draft :Type: Process :Created: 2018-07-14 :Resolution: (required for Accepted | Rejected | Withdrawn) Abstract In this NEP we describe NumPy's approach to backwards compatibility, its deprecation and removal policy, and the

Re: [Numpy-discussion] backwards compatibility and deprecation policy NEP

needed a few iterations. That points to gradual evolution being a better model. Cheers. Ralf > Best regards, > Hameer Abbasi > Sent from Astro <https://www.helloastro.com> for Mac > > On 22. Jul 2018 at 01:48, Ralf Gommers wrote: > > > Hi all, > > Here is a

Re: [Numpy-discussion] backwards compatibility and deprecation policy NEP

Hi Marten, Thanks for the thoughtful reply. On Sat, Jul 21, 2018 at 6:39 PM, Marten van Kerkwijk < m.h.vankerkw...@gmail.com> wrote: > Hi Ralf, > > Overall, this looks good. But I think the subclassing section is somewhat > misleading in suggesting `ndarray` is not well designed to be subclasse

Re: [Numpy-discussion] backwards compatibility and deprecation policy NEP

On Sat, Jul 21, 2018 at 7:06 PM, Marten van Kerkwijk < m.h.vankerkw...@gmail.com> wrote: > Hi Ralf, > > Maybe as a concrete example of something that has been discussed, for > which your proposed text makes (I think) clear what should or should not be > done: > > Many of us hate that `np.array` (l

Re: [Numpy-discussion] backwards compatibility and deprecation policy NEP

On Sat, Jul 21, 2018 at 7:25 PM, Nathaniel Smith wrote: > On Sat, Jul 21, 2018 at 5:46 PM, Hameer Abbasi > wrote: > > The possibility of another major version change (possibly the same one) > > where we re-write all portions that were agreed upon (via NEPs) to be > > re-written, with a longer LT

Re: [Numpy-discussion] backwards compatibility and deprecation policy NEP

On Sat, Jul 21, 2018 at 7:15 PM, Nathaniel Smith wrote: > On Sat, Jul 21, 2018 at 4:48 PM, Ralf Gommers > wrote: > > Hi all, > > > > Here is a first draft of a NEP on backwards compatibility and deprecation > > policy. This I think mostly formalized what we'v

Re: [Numpy-discussion] Commit privileges

On Mon, Jul 23, 2018 at 3:24 PM, Matti Picus wrote: > On 19/07/18 14:08, Charles R Harris wrote: > >> Hi All, >> >> The NumPy Steering Council has been looking at commit rights for the >> NumPy developers hired at BIDS. We would like them to be able to label PRs, >> close issues, and merge simple

Re: [Numpy-discussion] backwards compatibility and deprecation policy NEP

On Mon, Jul 23, 2018 at 1:43 PM, Marten van Kerkwijk < m.h.vankerkw...@gmail.com> wrote: > >> Rather, we might state that "At some point in the future, the NumPy >> development team may no longer interested in maintaining workarounds for >> specific subclasses, because other interfaces for extendi

Re: [Numpy-discussion] backwards compatibility and deprecation policy NEP

On Mon, Jul 23, 2018 at 11:46 AM, Stephan Hoyer wrote: > On Sun, Jul 22, 2018 at 12:28 PM Ralf Gommers > wrote: > >> Then, I think it's not unreasonable to draw a couple of hard lines. For >> example, removing complete submodules like linalg or random has ended up o

Re: [Numpy-discussion] backwards compatibility and deprecation policy NEP

On Tue, Jul 24, 2018 at 8:07 PM, Nathaniel Smith wrote: > On Sun, Jul 22, 2018 at 12:28 PM, Ralf Gommers > wrote: > > On Sat, Jul 21, 2018 at 7:15 PM, Nathaniel Smith wrote: > >> Speaking of examples: I hate to say this because in general I think > >> using exam

Re: [Numpy-discussion] update to numpy-1.5.0 gives new warnings from scipy

On Wed, Jul 25, 2018 at 11:44 AM, Neal Becker wrote: > After update to numpy-1.5.0, I'm getting warnings from scipy. > These probably come from my code using convolve. Does scipy need updating? > Should already be fixed in scipy master. Cheers, Ralf > /home/nbecker/.local/lib/python3.6/site

Re: [Numpy-discussion] Roadmap proposal, v3

On Thu, Jul 26, 2018 at 12:41 AM, Chris Barker - NOAA Federal < chris.bar...@noaa.gov> wrote: > > Obviously the string dtype proposal in the roadmap is only a sketch at > this point :). > > > > I do think that options listed currently (encoded strings with > fixed-width storage and variable length

Re: [Numpy-discussion] Adoption of a Code of Conduct

On Fri, Jul 27, 2018 at 10:02 PM, Stefan van der Walt wrote: > Hi everyone, > > A while ago, SciPy (the library) adopted its Code of Conduct: > https://docs.scipy.org/doc/scipy/reference/dev/conduct/code_ > of_conduct.html > > We worked hard to make that document friendly, while at the same time

Re: [Numpy-discussion] Roadmap proposal, v3

On Wed, Jul 25, 2018 at 9:19 PM, Ralf Gommers wrote: > > > On Thu, Jul 26, 2018 at 12:41 AM, Chris Barker - NOAA Federal < > chris.bar...@noaa.gov> wrote: > >> > Obviously the string dtype proposal in the roadmap is only a sketch at >> this point :). >

Re: [Numpy-discussion] Adoption of a Code of Conduct

On Wed, Aug 1, 2018 at 12:20 AM, Nathan Goldbaum wrote: > I realize this was probably brought up in the discussions about the scipy > code of conduct which I have not looked at, but I’m troubled by the > inclusion of “political beliefs” in the document. > It was not brought up explicitly as far

Re: [Numpy-discussion] Adoption of a Code of Conduct

On Wed, Aug 1, 2018 at 8:12 AM, Nathan Goldbaum wrote: > > > On Wed, Aug 1, 2018 at 9:49 AM, Ralf Gommers > wrote: > >> >> >> On Wed, Aug 1, 2018 at 12:20 AM, Nathan Goldbaum >> wrote: >> >>> I realize this was probably brought up in the d

Re: [Numpy-discussion] Roadmap proposal, v3

On Tue, Jul 24, 2018 at 12:04 PM, Stefan van der Walt wrote: > Hi everyone, > > Please take a look at the latest roadmap proposal: > > https://github.com/numpy/numpy/pull/11611 > > This is a living document, so can easily be modified in the future, but > we'd like to get in place a document that

Re: [Numpy-discussion] Adoption of a Code of Conduct

On Wed, Aug 1, 2018 at 10:04 PM, Robert Kern wrote: > On Wed, Aug 1, 2018 at 8:35 PM Ryan May wrote: > >> When experts say that something is a bad idea, and when the people who >>> a CoC is supposed to protect says it makes them feel unsafe, I feel >>> like we should listen to that. >>> >>> I al

Re: [Numpy-discussion] Adoption of a Code of Conduct

On Wed, Aug 1, 2018 at 5:57 PM, Nathaniel Smith wrote: > On Wed, Aug 1, 2018 at 8:37 AM, Ralf Gommers > wrote: > > > > >> For another perspective on this issue see > >> https://where.coraline.codes/blog/oscon/, where Coraline Ada describes > her > >>

Re: [Numpy-discussion] Adoption of a Code of Conduct

On Thu, Aug 2, 2018 at 3:35 AM, Marten van Kerkwijk < m.h.vankerkw...@gmail.com> wrote: > I think a legalistic focus on the letter rather than the spirit of the > code of conduct is not that helpful (and probably what makes if feel US > centric - funny how court systems end up shaping countries).

Re: [Numpy-discussion] Adoption of a Code of Conduct

On Fri, Aug 3, 2018 at 2:04 AM, Matthew Brett wrote: > Hi, > > On Fri, Aug 3, 2018 at 9:35 AM, Stefan van der Walt > wrote: > > On August 3, 2018 09:50:38 Robert Kern wrote: > >> > >> On Thu, Aug 2, 2018 at 11:01 PM Robert Kern > wrote: > >>> > >>> Nope, concision is definitely not my strengt

Re: [Numpy-discussion] Adoption of a Code of Conduct

On Fri, Aug 3, 2018 at 11:39 AM, Chris Barker wrote: > On Fri, Aug 3, 2018 at 11:20 AM, Chris Barker > wrote: > >> Given Jupyter, numpy, scipy, matplotlib?, etc, are all working on a CoC >> -- maybe we could have NumFocus take a lead on this for the whole community? >> > Nelle is right about the

Re: [Numpy-discussion] Taking back control of the #numpy irc channel

On Mon, Aug 6, 2018 at 7:15 PM, Nathan Goldbaum wrote: > Hi, > > I idle in #scipy and have op in there. I’m happy start idling in #numpy > and be op if the community is willing to let me. > Thanks Nathan. Sounds useful. There's also a Gitter numpy channel. AFAIK few/none core devs are regularly

Re: [Numpy-discussion] Taking back control of the #numpy irc channel

On Tue, Aug 7, 2018 at 4:34 AM, Sebastian Berg wrote: > On Mon, 2018-08-06 at 21:52 -0700, Ralf Gommers wrote: > > > > > > On Mon, Aug 6, 2018 at 7:15 PM, Nathan Goldbaum > m> wrote: > > > Hi, > > > > > > I idle in #scipy and have op in ther

Re: [Numpy-discussion] pytest, fixture and parametrize

On Wed, Aug 8, 2018 at 8:27 AM, Hameer Abbasi wrote: > > On 8. Aug 2018, at 17:23, Charles R Harris > wrote: > > > > Hi All, > > > > I'm writing some tests and would like to come to a common understanding > as to whether we are should use pytest fixtures and parametrized classes > and functions.

Re: [Numpy-discussion] Taking back control of the #numpy irc channel

On Wed, Aug 8, 2018 at 1:23 AM, Sebastian Berg wrote: > On Tue, 2018-08-07 at 22:07 -0700, Ralf Gommers wrote: > > > > > > On Tue, Aug 7, 2018 at 4:34 AM, Sebastian Berg > s.net> wrote: > > > On Mon, 2018-08-06 at 21:52 -0700, Ralf Gommers wrote: > > &g

Re: [Numpy-discussion] Taking back control of the #numpy irc channel

On Wed, Aug 8, 2018 at 9:06 AM, Sebastian Berg wrote: > On Wed, 2018-08-08 at 08:55 -0700, Ralf Gommers wrote: > > > > > > On Wed, Aug 8, 2018 at 1:23 AM, Sebastian Berg > s.net> wrote: > > > > > > > > > Will do, just realized looking at

Re: [Numpy-discussion] Stacklevel for warnings.

On Sat, Aug 11, 2018 at 1:22 AM, Sebastian Berg wrote: > On Fri, 2018-08-10 at 16:05 -0600, Charles R Harris wrote: > > Hi All, > > > > Do we have a policy for the stacklevel that should be used in NumPy? > > How far back should the stack be displayed? I note that the optimum > > stacklevel may v

Re: [Numpy-discussion] Does numpy need a *.dist-info directory? What is the status of setuptools?

On Sat, Aug 11, 2018 at 11:29 AM, Charles R Harris < charlesr.har...@gmail.com> wrote: > Hi All, > > A question for any packaging gurus out there, should NumPy have a > *.dist-info directory? I note > that currently we have a *.egg-info directory. > Tho

Re: [Numpy-discussion] Does numpy need a *.dist-info directory? What is the status of setuptools?

On Sat, Aug 11, 2018 at 12:17 PM, Charles R Harris < charlesr.har...@gmail.com> wrote: > > > On Sat, Aug 11, 2018 at 1:13 PM, Ralf Gommers > wrote: > >> >> >> On Sat, Aug 11, 2018 at 11:29 AM, Charles R Harris < >> charlesr.har...@gmail.com&g

Re: [Numpy-discussion] Adoption of a Code of Conduct

On Fri, Aug 3, 2018 at 1:02 PM, Charles R Harris wrote: > > > On Fri, Aug 3, 2018 at 1:45 PM, Peter Creasey < > p.e.creasey...@googlemail.com> wrote: > >> +1 for keeping the same CoC as Scipy, making a new thing just seems a >> bigger surface area to maintain. Personally I already assumed Scipy's

Re: [Numpy-discussion] The http://planet.scipy.org/ site is down.

On Mon, Aug 20, 2018 at 4:39 AM Andy Ray Terrel wrote: > Unfortunately the machine that was hosting planet.scipy.org has died. > > The volunteer that was supporting it, Sheila Miguez, had warned the scipy > leadership for over a year that it was going down. Over the last six months > after the Ra

Re: [Numpy-discussion] Proposal to accept NEP-18, __array_function__ protocol

On Wed, Aug 22, 2018 at 4:22 AM Hameer Abbasi wrote: > May I propose an alternative that was already discussed, and one that I > think everyone will be okay with: > That's a dangerous assumption on this list:) We put all overridable functions inside a new submodule, numpy.api, that > will initi

Re: [Numpy-discussion] Possible Deprecation of np.ediff1d

On Tue, Aug 28, 2018 at 8:04 AM Charles R Harris wrote: > > > On Mon, Aug 27, 2018 at 8:05 PM Stephan Hoyer wrote: > >> On Mon, Aug 27, 2018 at 10:30 AM Tyler Reddy >> wrote: >> >>> Chuck suggested ( >>> https://github.com/numpy/numpy/pull/11805#issuecomment-416069436 ) that >>> we may want to

Re: [Numpy-discussion] Possible Deprecation of np.ediff1d

On Tue, Aug 28, 2018 at 12:21 PM Marten van Kerkwijk < m.h.vankerkw...@gmail.com> wrote: > > > On Mon, Aug 27, 2018 at 10:05 PM Stephan Hoyer wrote: > > - It appears in astropy, dask, pandas, pint, scipy and TensorFlow. >> > > The only reason it appears in astropy is because of tests that Quantit

Re: [Numpy-discussion] Adoption of a Code of Conduct

On Wed, Aug 15, 2018 at 12:59 PM Sebastian Berg wrote: > On Tue, 2018-08-14 at 21:30 -0700, Ralf Gommers wrote: > > > > > > On Fri, Aug 3, 2018 at 1:02 PM, Charles R Harris < > > charlesr.har...@gmail.com> wrote: > > > > > > On Fri, Aug 3,

[Numpy-discussion] rescuing missing data documents

Hi all, Recently a few people (Tyler, Matti, myself, maybe others?) were discussing the history of missing data in the context of custom dtypes. I mentioned that there was a good write-up, but couldn't find it at the time. I just stumbled across it, it's hidden in the numpy.org repo: http://www.nu

Re: [Numpy-discussion] ARMv8 / shippable addition to CI

On Wed, Sep 5, 2018 at 3:15 PM Tyler Reddy wrote: > Hi, > > Stefan & Matti wanted me to check on the mailing list about about adding > ARMv8 (free / shippable service) to NumPy CI on github -- is anyone opposed > to that? > sounds fine (and useful) to me. > > Only obvious drawback seems to be

Re: [Numpy-discussion] C99

On Sat, Sep 8, 2018 at 6:07 AM Charles R Harris wrote: > > > On Sat, Sep 8, 2018 at 12:02 AM Eric Wieser > wrote: > >> Thanks for the first step on this! >> >> Should we allow // style comments >> >> I don’t think it matters too much. I think it might be a little messy to >> have a mix of the tw

Re: [Numpy-discussion] C99

On Sat, Sep 8, 2018 at 12:24 PM Charles R Harris wrote: > > > On Sat, Sep 8, 2018 at 11:02 AM Ralf Gommers > wrote: > >> >> >> On Sat, Sep 8, 2018 at 6:07 AM Charles R Harris < >> charlesr.har...@gmail.com> wrote: >> >>> &g

Re: [Numpy-discussion] The http://planet.scipy.org/ site is down.

On Sun, Sep 9, 2018 at 2:16 PM Pauli Virtanen wrote: > ti, 2018-08-21 kello 01:02 +0200, Pauli Virtanen kirjoitti: > [clip] > > Not volunteering to take this into completion, though. > > Well, turns out otherwise: > Awesome, thanks a lot Pauli! > https://planetscipy.netlify.com/ > > https://gi

Re: [Numpy-discussion] CI Testing

On Wed, Sep 12, 2018 at 8:33 PM Tyler Reddy wrote: > Hi Allan, > > That's pretty cool -- I should follow-up on the CI part of it! > It's quite nice to have access to more exotic hardware, but I'd recommend not to add anything to our CI setup that's not a fully hosted service that we control via

Re: [Numpy-discussion] CI Testing

On Wed, Sep 12, 2018 at 5:15 PM Tyler Reddy wrote: > Could initially try just adding some "bonus" jobs (that are useful / nice, > but we can't afford to add to current CI load) as a trial maybe, and if > the free version or a deal / offer on better services proves more > expedient than what we cu

Re: [Numpy-discussion] Tidelift

On Tue, Sep 18, 2018 at 8:30 PM Andy Ray Terrel wrote: > > > On Tue, Sep 18, 2018 at 10:01 PM Nathaniel Smith wrote: > >> On Tue, Sep 18, 2018 at 6:04 PM, Stefan van der Walt >> wrote: >> > On Tue, 18 Sep 2018 16:54:16 -0500, Andy Ray Terrel wrote: >> >> FYI, Donald Fischer will be at the NumFO

Re: [Numpy-discussion] rescuing missing data documents

On Sun, Sep 2, 2018 at 8:15 AM Stefan van der Walt wrote: > On September 2, 2018 06:16:36 Ralf Gommers wrote: > >> I'd like to see the NEPs rescued, and the summary moved from the >> numpy.org repo (maybe into yet another NEP?). It would be best if the >> original a

Re: [Numpy-discussion] PR Cleanup

On Tue, Sep 25, 2018 at 5:35 PM Marten van Kerkwijk < m.h.vankerkw...@gmail.com> wrote: > Hi Chuck, > > Over at astropy we have a bot that sends a warning to PRs that have not > received any commits for 5 months [1] and closes them if nothing happens in > the next month, asking to open an issue in

Re: [Numpy-discussion] Adding a hex version like PY_VERSION_HEX

On Sat, Oct 6, 2018 at 11:24 PM Matti Picus wrote: > On 05/10/18 11:46, Jerome Kieffer wrote: > > On Fri, 5 Oct 2018 11:31:20 +0300 > > Matti Picus wrote: > > > >> In PR 12074 https://github.com/numpy/numpy/pull/12074 I propose adding > a > >> function `version.get_numpy_version_as_hex()` which

Re: [Numpy-discussion] BIDS/NumPy dev meetings, Wednesdays 12pm Pacific

On Thu, Oct 11, 2018 at 10:44 PM Stefan van der Walt wrote: > Hi everyone, > > The team at BIDS meets once a week to discuss progress, priorities, and > roadblocks. While our priorities are broadly determined by the project > roadmap [0], we would like to provide an opportunity for the community

[Numpy-discussion] summary of NumFOCUS Summit & roadmap presentations

Hi all, At the end of September the NumFOCUS Summit was held; Allan and I both attended on behalf of NumPy. I've written up a summary of the event from a NumPy perspective: https://rgommers.github.io/2018/10/2018-numfocus-summit---a-summary/. I also link in that post to both of the presentations I

Re: [Numpy-discussion] Removing priority labels from github

On Fri, Oct 19, 2018 at 4:49 PM Stephan Hoyer wrote: > > > On Fri, Oct 19, 2018 at 2:22 AM Sebastian Berg > wrote: > >> On Fri, 2018-10-19 at 11:02 +0300, Matti Picus wrote: >> > We currently have highest, high, normal, low, and lowest priority >> > labels >> > for github issues/PRs. At the rece

Re: [Numpy-discussion] asanyarray vs. asarray

On Fri, Oct 19, 2018 at 4:15 PM Hameer Abbasi wrote: > Hi! > > On Friday, Oct 19, 2018 at 6:09 PM, Stephan Hoyer > wrote: > I don't think it makes much sense to change NumPy's existing usage of > asarray() to asanyarray() unless we add subok=True arguments (which default > to False). But this en

Re: [Numpy-discussion] asanyarray vs. asarray

On Fri, Oct 19, 2018 at 10:28 PM Ralf Gommers wrote: > > > On Fri, Oct 19, 2018 at 4:15 PM Hameer Abbasi > wrote: > >> Hi! >> >> On Friday, Oct 19, 2018 at 6:09 PM, Stephan Hoyer >> wrote: >> I don't think it makes much sense to change Nu

<    1   2   3   4   5   6   7   8   >