Hi All,
Just to raise the question if these two options should be removed at some point? The current default value for both is 0, so we have separate compilation and relaxed strides checking by default.
Chuck
On Fri, Apr 3, 2015 at 9:00 PM, Charles R Harris charlesr.harris@gmail.com wrote:
Hi All,
Just to raise the question if these two options should be removed at some point? The current default value for both is 0, so we have separate compilation and relaxed strides checking by default.
Oops, default value is 1, not 0.
Chuck
IIRC there allegedly exist platforms where separate compilation doesn't work right? I'm happy to get rid of it if no one speaks up to defend such platforms, though, we can always add it back later. One case was for statically linking numpy into the interpreter, but I'm skeptical about how much we should care about that case, since that's already a hacky kind of process and there are simple alternative hacks that could be used to strip the offending symbols.
Depends on how much it lets us simplify things, I guess. Would we get to remove all the no-export attributes on everything? On Apr 3, 2015 8:01 PM, "Charles R Harris" charlesr.harris@gmail.com wrote:
On Fri, Apr 3, 2015 at 9:00 PM, Charles R Harris < charlesr.harris@gmail.com> wrote:
Hi All,
Just to raise the question if these two options should be removed at some point? The current default value for both is 0, so we have separate compilation and relaxed strides checking by default.
Oops, default value is 1, not 0.
Chuck
NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Sat, Apr 4, 2015 at 4:25 AM, Nathaniel Smith njs@pobox.com wrote:
IIRC there allegedly exist platforms where separate compilation doesn't work right? I'm happy to get rid of it if no one speaks up to defend such platforms, though, we can always add it back later. One case was for statically linking numpy into the interpreter, but I'm skeptical about how much we should care about that case, since that's already a hacky kind of process and there are simple alternative hacks that could be used to strip the offending symbols.
Depends on how much it lets us simplify things, I guess. Would we get to remove all the no-export attributes on everything?
No, the whole point of the no-export is to support the separate compilation use case.
David
On Apr 3, 2015 8:01 PM, "Charles R Harris" charlesr.harris@gmail.com wrote:
On Fri, Apr 3, 2015 at 9:00 PM, Charles R Harris < charlesr.harris@gmail.com> wrote:
Hi All,
Just to raise the question if these two options should be removed at some point? The current default value for both is 0, so we have separate compilation and relaxed strides checking by default.
Oops, default value is 1, not 0.
Chuck
NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Apr 5, 2015 3:09 AM, "David Cournapeau" cournape@gmail.com wrote:
On Sat, Apr 4, 2015 at 4:25 AM, Nathaniel Smith njs@pobox.com wrote:
IIRC there allegedly exist platforms where separate compilation doesn't
work right? I'm happy to get rid of it if no one speaks up to defend such platforms, though, we can always add it back later. One case was for statically linking numpy into the interpreter, but I'm skeptical about how much we should care about that case, since that's already a hacky kind of process and there are simple alternative hacks that could be used to strip the offending symbols.
Depends on how much it lets us simplify things, I guess. Would we get to
remove all the no-export attributes on everything?
No, the whole point of the no-export is to support the separate
compilation use case.
Oog, on further checking I guess this is still true as long as we are using our heirloom mingw compiler on Windows. AFAIK all other compilers we care about support -fvisibility=hidden or equivalent.
-n
On Fr, 2015-04-03 at 21:00 -0600, Charles R Harris wrote:
Hi All,
Just to raise the question if these two options should be removed at some point? The current default value for both is 0, so we have separate compilation and relaxed strides checking by default.
I still have some small doubts that leaving relaxed strides as default will work out for 1.10, plus we will have to make "debugging mode" switchable (default off), and abusing the flag with different values for it is probably simplest. So my guess is, we should wait at least one version with it.
- Sebastian
Chuck
NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Sun, Apr 5, 2015 at 4:37 AM, Sebastian Berg sebastian@sipsolutions.net wrote:
On Fr, 2015-04-03 at 21:00 -0600, Charles R Harris wrote:
Hi All,
Just to raise the question if these two options should be removed at some point? The current default value for both is 0, so we have separate compilation and relaxed strides checking by default.
I still have some small doubts that leaving relaxed strides as default will work out for 1.10, plus we will have to make "debugging mode" switchable (default off), and abusing the flag with different values for it is probably simplest. So my guess is, we should wait at least one version with it.
Agree, I'm thinking one or two release down the road.
Chuck
On So, 2015-04-05 at 07:08 -0600, Charles R Harris wrote:
On Sun, Apr 5, 2015 at 4:37 AM, Sebastian Berg sebastian@sipsolutions.net wrote: On Fr, 2015-04-03 at 21:00 -0600, Charles R Harris wrote: > Hi All, > > > Just to raise the question if these two options should be removed at > some point? The current default value for both is 0, so we have > separate compilation and relaxed strides checking by default. >
I still have some small doubts that leaving relaxed strides as default will work out for 1.10, plus we will have to make "debugging mode" switchable (default off), and abusing the flag with different values for it is probably simplest. So my guess is, we should wait at least one version with it.
Agree, I'm thinking one or two release down the road.
Ah ok, misunderstood it. I suppose it will depend on whether the debug feature of messing up strides will be used. I don't think we will have to support it for disabling relaxed strides at that point though (so maybe a rename makes sense by then).
Chuck
NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion