Re: [Numpy-discussion] Officially drop Python 3.6 from NumPy 1.20 (was: NumPy 1.20.x branch in two weeks)

stable support for 3.7 yet? > > > > > Although > > > > > PyPy is maybe not a big priority. > > > > > > > > > > We don't have to support 3.6 and I don't care if we do. Until > > > > > this > > > > > discus

Re: [Numpy-discussion] NumPy 1.20.x branch in two weeks

op support for old version of Python and NumPy too soon. On Sun, Nov 1, 2020 at 6:44 PM Jarrod Millman wrote: > > NetworkX is currently planning to support 3.6 for our coming 2.6 > release (dec 2020) and 3.0 release (early 2021). We had originally > thought about following NEP 29. But

Re: [Numpy-discussion] NumPy 1.20.x branch in two weeks

NetworkX is currently planning to support 3.6 for our coming 2.6 release (dec 2020) and 3.0 release (early 2021). We had originally thought about following NEP 29. But I assumed it had been abandoned, since neither NumPy nor SciPy dropped Python 3.6 on Jun 23, 2020. NetworkX is likely to continu

Re: [Numpy-discussion] Cleaning up Python 2.7 code.

Sounds good! Jarrod On Thu, Jan 2, 2020 at 4:53 PM Charles R Harris wrote: > > > > On Thu, Jan 2, 2020 at 5:20 PM Jarrod Millman wrote: >> >> Hi Chuck, >> >> I just finished doing that for NetworkX and would be happy to start a >> PR for NumPy

Re: [Numpy-discussion] Cleaning up Python 2.7 code.

Hi Chuck, I just finished doing that for NetworkX and would be happy to start a PR for NumPy tomorrow (assuming there are no objections). Best regards, Jarrod On Thu, Jan 2, 2020 at 3:53 PM Charles R Harris wrote: > > Hi All, > > Just want to propose cleaning up the Python 2.7 compatibility co

[Numpy-discussion] NetworkX 2.3rc3 released (Python 3 only)

I am happy to announce the third **release candidate** for NetworkX 2.3! NetworkX is a Python package for the creation, manipulation, and study of the structure, dynamics, and functions of complex networks. This release supports Python 3.5-3.7 (i.e., this is our first **Python 3 only** release).

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

+1 Jarrod On Tue, Aug 14, 2018 at 9:30 PM, Ralf Gommers wrote: > > > On Fri, Aug 3, 2018 at 1:02 PM, Charles R Harris > wrote: >> >> >> >> On Fri, Aug 3, 2018 at 1:45 PM, Peter Creasey >> wrote: >>> >>> +1 for keeping the same CoC as Scipy, making a new thing just seems a >>> bigger surface ar

Re: [Numpy-discussion] Dropping Python 3.4 support for NumPy 1.16

+1 On Wed, Jun 13, 2018 at 2:27 PM, Charles R Harris wrote: > Hi All, > > I think NumPy 1.16 would be a good time to drop Python 3.4 support. We will > want to do that anyway once we drop 2.7 so that we will only be using recent > Windows compilers, and with Python 3.7 due at the end of the month

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

I like the idea of a random/controversial ideas section. On Fri, Jun 1, 2018 at 12:11 PM, Ralf Gommers wrote: > > > 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": MaskedArra

Re: [Numpy-discussion] Python 3 compatible examples

+1 On Fri, Jun 1, 2018 at 1:43 PM, Juan Nunez-Iglesias wrote: > > On Sat, Jun 2, 2018, at 6:22 AM, Pauli Virtanen wrote: >> For Scipy, we converted the examples in the documentation to Python 3, >> and have essentially ignored Python 2 compatibility. So far, I remember >> no complaints about it.

Re: [Numpy-discussion] NumPy sprint May 24-25 at BIDS

hotel, so the farthest you probably need to travel is from the hotel to BIDS and back. Best regards, Jarrod On Sun, May 13, 2018 at 10:59 AM, Charles R Harris wrote: > > > On Sat, May 12, 2018 at 4:27 PM, Jarrod Millman > wrote: >> >> Hi Chuck, >> >&g

Re: [Numpy-discussion] NumPy sprint May 24-25 at BIDS

Hi Chuck, A few more bits of advice from a local ... Oakland airport is smaller and closer, so I try to use it when I can. But SFO probably has more options and isn't too far away. I prefer Hotel Shattuck Plaza to Hotel Durant. Shattuck is close to BART. So you can get on the BART at either SF

[Numpy-discussion] NEP process PR

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 You can see how I modified PEP 1 here: https://github.com/numpy/numpy/pull/10213/commits/eaf78

Re: [Numpy-discussion] NEP process update

Gommers >> wrote: >> > On Wed, Dec 6, 2017 at 12:31 PM, Jarrod Millman >> > wrote: >> >> Assuming that sounds good, my tentative next steps are: >> >> >> >> - I'll draft a purpose and process NEP based on PEP 1 and a few

[Numpy-discussion] NEP process update

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 I'm thinking of putting together some better tools and documentation, a

[Numpy-discussion] NetworkX 2.0b1 released

Hi All, I am happy to announce the **beta** release of NetworkX 2.0! NetworkX is a Python package for the creation, manipulation, and study of the structure, dynamics, and functions of complex networks. This release supports Python 2.7 and 3.4-3.6 and contains many new features. This release is