[Numpy-discussion] updated 1.5.1 release schedule

[Russell E. Owen]

In article 
<AANLkTimfgckbG8CprYGuKcvWVQzxQyCYkgeXVX_=8fGB at mail.gmail.com>,
 Ralf Gommers <ralf.gommers at googlemail.com> wrote:

> On Mon, Nov 8, 2010 at 5:16 AM, Vincent Davis <vincent at vincentdavis.net> 
> wrote:
> >
> >
> > On Sun, Nov 7, 2010 at 1:51 AM, Ralf Gommers <ralf.gommers at googlemail.com>
> > wrote:
> >>
> >> Hi,
> >>
> >> Since we weren't able to stick to the original schedule for 1.5.1,
> >> here's a short note about the current status. There are two changes
> >> that need to go in before RC2:
> >> https://github.com/numpy/numpy/pull/11
> >> https://github.com/numpy/numpy/pull/9
> >> If no one has time for a review I'll commit those to 1.5.x by Tuesday
> >> and tag RC2. Final release should be one week after that, unless an
> >> RC3 is necessary.
> >
> > Since we will have 2 different dmgs for python2.7 (osx10.3 and osx10.5) and
> > I don't think there is any check in the installer to make sure the right
> > python2.7 version is present when installing. The installer only check that
> > python2.7 is present. I think a check should be added. I am missing 
> > somthing
> > or there are other suggestions I would like to get this in 1.5.1rc2. I not
> > sure the best way to make this check but I think I can come up with a
> > solution. Also would need a useful error message.
> > Vincent
> 
> To let the user know if there's a mismatch may be helpful, but we
> shouldn't prevent installation. In many cases mixing installers will
> just work. If you have a patch it's welcome, but I think it's not
> critical for this release.

I am strongly in favor of such a check and refusing to install on the 
mismatched version of Python.

I am be concerned about hidden problems that emerge later -- for 
instance when the user bundles an application and somebody else tries to 
use it.

That said, I don't know how to perform such a test.

-- Russell