that np.allclose()
> cannot be directly applied.
>
> Is there any way to check for cycles in this situation?
>
> Thanks for any advice,
> Manolo
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> https://mail
ts are always better than global invariants -- the
> most well known example is local variables versus global variables, but the
> principle is much broader.
>
> -n
>
> --
> *Kang Wang, Ph.D.*
> Highland Ave., Room 1113
> Madison, WI 53705-2275
>
>
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>
>
--
Daniel Sank
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Could you please explain why you need 'F' ordering? It's pretty unlikely
that you actually care about the internal memory layout, and you'll get
better advice if you explain why you think you do care.
> My first Python project is to somehow modify NumPy source
> code such that everything is Fortra
Sturia,
> Change the name of keyword arguments?
> This would be evil.
Yes, I see this now. It is really a shame these were defined as keyword
arguments. I've shown the docstring to a few people and so far they all
agree that it is unnecessarily convoluted.
n't explain how to run the tests (in fact it doesn't even
mention them).
How can I make the proposed change without breaking the tests, or
equivalently how do I find out how to run the tests myself so I can find an
acceptable way of making the change on my own?
[1] https://github.co
