Hi,
For what it's worth, python 3.6 is also dropped for astropy 4.2 (RC1 to be
released in the next few days). We haven't yet formally adopted NEP29, but
are very close to it peding some word smithing, and no one from the dev
team was fighting for keeping support for 3.6. or numpy 1.16.
Cheers,
Hi,
At first sight, the competition element seems a bit weird approach for the
open source setting. Do you see a way how it can work out well?
(Google also has a code-in for HS students. Has numpy ever tried it? (all
the mentors I talked to at the last gsoc summit said it takes more time to
mento
Hi,
You could consider archiving the repository (bottom at the Settings
page for folks with admin access), too. That makes it ever more
visible that it's no longer maintained or in fact to be used.
Cheers,
Brigitta
On Tue, 3 Dec 2019 at 11:33, Warren Weckesser
wrote:
>
> It looks like the repo
I'm unable to connect, "The host has another meeting in progress".
Brigitta
On Tue, 15 Oct 2019 at 07:20, Hameer Abbasi
wrote:
> My bad... It's not until later.
>
>
>
> On 15.10.19, 16:16, "NumPy-Discussion on behalf of Hameer Abbasi"
> einstein.edi...@gmail.com> wrote:
>
> Is the meeting
> 3. After merging, the release notes are copied into the wiki by the
> user or a contributor. After the copy happened, the label could/should
> be removed?
In astropy we keep our "whats-new-needed" label around, so people
doing the release can double check that everything is indeed ended up
in t
