Hi! You can use a context manager: with np.errstate(all=”ignore”): … Best regards, Hameer Abbasi Von meinem iPhone gesendet
> Am 18.02.2023 um 16:00 schrieb David Pine <[email protected]>: > > I agree. The problem can be avoided in a very inelegant way by turning > warnings off before calling where() and turning them back on afterward, like > this > > warnings.filterwarnings("ignore", category=RuntimeWarning) > result = np.where(x == 0.0, 0.0, 1./data) > warnings.filterwarnings("always", category=RuntimeWarning) > > But it would be MUCH nicer if there were an optional keyword argument in the > where() call. > > Thanks, > Dave > _______________________________________________ > NumPy-Discussion mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ > Member address: [email protected] _______________________________________________ NumPy-Discussion mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: [email protected]
