On Mon, Sep 14, 2015 at 9:32 AM, Matthew Brett <firstname.lastname@example.org> wrote:
> On Mon, Sep 14, 2015 at 1:22 AM, David Cournapeau <email@example.com> wrote:
> > On Mon, Sep 14, 2015 at 9:18 AM, Matthew Brett <firstname.lastname@example.org>
> > wrote:
> >> Hi,
> >> I'm just building numpy 1.9.2 for Python 3.5 (just released).
> >> In order to get the tests to pass on Python 3.5, I need to cherry pick
> >> commit 7d6aa8c onto the 1.9.2 tag position.
> >> Does anyone object to me uploading a wheel built from this patched
> >> version to pypi as 1.9.2 for Python 3.5 on OSX? It would help to get
> >> the ball rolling for Python 3.5 binary wheels.
> > Why not releasing this as 1.9.3 ? It does not need to be a full release
> > (with binaries and all), but having multiple sources for a given tag is
> > confusing.
> Generally OK with me, but it's quite a bit of extra work for very
> little gain. We'd have to tag, release a source tarball and OSX
> wheels, at least.
I think it's highly desirable that we also have a *source* release that builds on Python 3.5, irrespective of whether or not we have binary wheels for a couple of platforms up for Python 3.5. So I would encourage a quick 1.9.3 release that incorporates this patch.
NumPy-Discussion mailing list