<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Feb 2, 2012, at 12:58 PM, Ralf Gommers wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><br><br><div class="gmail_quote">On Thu, Feb 2, 2012 at 6:36 PM, Charles R Harris <span dir="ltr"><<a href="mailto:charlesr.harris@gmail.com">charlesr.harris@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br><br><div class="gmail_quote"><div class="im">On Thu, Feb 2, 2012 at 9:58 AM, Bruce Southey <span dir="ltr"><<a href="mailto:bsouthey@gmail.com" target="_blank">bsouthey@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><div>
On 02/01/2012 02:53 PM, Charles R Harris wrote:
<blockquote type="cite">Hi All,<br>
<br>
Two things here.<br>
<br>
1) Some macros for threading and the iterator now require a
trailing semicolon. This change will be reverted before the 1.7
release so that scipy 0.10 will compile, but because it is
desirable in the long term it would be helpful if folks
maintaining c extensions using numpy would try compiling them
against current development and adding the semicolon where needed.
The added semicolon will be backward compatible with earlier
versions of numpy.<br>
</blockquote>
<br></div>
Why do the changes need to "be reverted before the 1.7 release'?<br>
Scipy 0.10 was released nearly three months ago so we should be
moving forward. I think this is not the first time a released scipy
would not build with the 'future' numpy. But most of the scipy 0.10
downloads are binaries so I presume that this change should not
affect those users. But if this is such a major downstream problem,
just have a very, very minor bug-fix very much restricted to this
issue. If the changes do not affect binary users then perhaps just a
re-release of the source archives would be needed rather than a full
bug release.<div><br></div></div></blockquote></div></div></blockquote><div><br>I don't think that it has happened in the recent past that the last released version of scipy wouldn't build with the last released numpy. And it would be a problem IMHO. The alternative would be to do a 0.10.1 release for this.<br></div></div></blockquote><div><br></div>The latest released version of SciPy should definitely build with the latest released version of NumPy. I like the idea of a 0.10.1 release to get these changes out there and supported. </div><div><br></div><div>-Travis</div><div><br></div><div><br><blockquote type="cite"><div class="gmail_quote"><div>
<br>Ralf<br><br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><div></div></div></blockquote></div><div><br>That was Ralph's preference. <br></div><div class="im"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><div>
<blockquote type="cite">
<br>
2) It is proposed to deprecate all of the macros in the
old_defines.h file and require the use of their replacements.
Numpy itself will have made this change after <a href="https://github.com/numpy/numpy/pull/189" target="_blank">pull-189</a> is
merged and getting rid of the surplus macros will help clean up
the historical detritus that has built up over the years, easing
maintenance, clarifying code, and making the eventual transition
to 2.0 a bit easier. There is a sed script in the tools directory
as part of the pull request that can be used to make the needed
substitutions.<br>
</blockquote>
<br></div>
Isn't this just formalizing the name changes that has been happening
for some time in 'core/include/numpy/old_defines.h'?<br>
That is people have really been using the 'new macros' for ages,
just that these have been 'called' with the old names. If so, I
would be support an aggressive stance for those changes are just
renaming and the slow depreciation cycle for other cases.<br>
<br></div></blockquote></div><div><br>Yes, the macro functionality is the same, just the names have changed.<br><br>I'm also going to update all the noprefix macro uses in numpy in a separate pull request. I expect that will be more disruptive.<br>
<br>Chuck<br></div></div>
<br>_______________________________________________<br>
NumPy-Discussion mailing list<br>
<a href="mailto:NumPy-Discussion@scipy.org">NumPy-Discussion@scipy.org</a><br>
<a href="http://mail.scipy.org/mailman/listinfo/numpy-discussion" target="_blank">http://mail.scipy.org/mailman/listinfo/numpy-discussion</a><br>
<br></blockquote></div><br>
_______________________________________________<br>NumPy-Discussion mailing list<br><a href="mailto:NumPy-Discussion@scipy.org">NumPy-Discussion@scipy.org</a><br>http://mail.scipy.org/mailman/listinfo/numpy-discussion<br></blockquote></div><br></body></html>