[Numpy-discussion] NPY_SEPARATE_COMPILATION and RELAXED_STRIDES_CHECKING
cournape at gmail.com
Sun Apr 5 06:09:08 EDT 2015
On Sat, Apr 4, 2015 at 4:25 AM, Nathaniel Smith <njs at 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
> On Apr 3, 2015 8:01 PM, "Charles R Harris" <charlesr.harris at gmail.com>
>> On Fri, Apr 3, 2015 at 9:00 PM, Charles R Harris <
>> charlesr.harris at 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.
>> NumPy-Discussion mailing list
>> NumPy-Discussion at scipy.org
> NumPy-Discussion mailing list
> NumPy-Discussion at scipy.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion