[Numpy-discussion] Stacklevel for warnings. (original) (raw)
Ralf Gommers ralf.gommers at gmail.com
Sat Aug 11 14:11:01 EDT 2018
- Previous message (by thread): [Numpy-discussion] Stacklevel for warnings.
- Next message (by thread): [Numpy-discussion] Stacklevel for warnings.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Aug 11, 2018 at 1:22 AM, Sebastian Berg <sebastian at sipsolutions.net> wrote:
On Fri, 2018-08-10 at 16:05 -0600, Charles R Harris wrote: > Hi All, > > Do we have a policy for the stacklevel that should be used in NumPy? > How far back should the stack be displayed? I note that the optimum > stacklevel may vary between users and developers. >
I thought it was so that it will point to the correct user line (or tend to point there). So stacklevel=2 for exposed and higher for private (python) functions IIRC. As for developers, I would hope they are OK with (and know how to) turning the warning into an error. Not sure we discussed it much, I seem to have a vague memory of asking if we are sure this is what we want and at least Ralf agreeing. Also I don't know how consistent it is overall.
That sounds right to me. I think when it was introduced it was quite consistent, because Sebastian replace warning filters everywhere with suppress_warnings. Would be good to document this in the devguide.
Ralf -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20180811/620df441/attachment.html>
- Previous message (by thread): [Numpy-discussion] Stacklevel for warnings.
- Next message (by thread): [Numpy-discussion] Stacklevel for warnings.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]