私は、一般的にちょうどExceptions
へWarnings
を促進警告のルートを検索する場合。
あなたの場合は、単にwarnings.simplefilter
またはwarnings.filterwarnings
を使用することができます。例えば
:
import warnings
def func():
warnings.warn('abc', UserWarning)
def func2():
func()
# Here I promote all UserWarnings to exceptions, but you could also use "warnings.filterwarnings"
# to only promote warnings from a specified module or matching a specified message.
# You may need to check which is most useful/appropriate for you.
warnings.simplefilter("error", UserWarning) # you might need to reset this later :)
func2()
完全なトレースバック与える:
---------------------------------------------------------------------------
UserWarning Traceback (most recent call last)
<ipython-input-11-be791e1071e7> in <module>()
8
9 warnings.simplefilter("error", UserWarning)
---> 10 func2()
<ipython-input-11-be791e1071e7> in func2()
5
6 def func2():
----> 7 func()
8
9 warnings.simplefilter("error", UserWarning)
<ipython-input-11-be791e1071e7> in func()
2
3 def func():
----> 4 warnings.warn('abc', UserWarning)
5
6 def func2():
UserWarning: abc
をそして、あなたはこれをデバッグしたい場合は、簡単にニシキヘビに最後に発生した例外のpdb
Sフックできます
を
import pdb
pdb.pm()
結果:
> <ipython-input-11-be791e1071e7>(4)func()
-> warnings.warn('abc', UserWarning)
(Pdb) _________________
これにより、最後に発生した例外の死後解析が開始されます。どのフレームを通じて掘ることができますし、変数を検査しなければならない、など
またフラグについて尋ね、そして実際に「警告処理」、-W
flagを可能フラグがあります。これは、warnings.filterwarnings
と非常によく似ています。便宜上、-W
フラグのドキュメントをここにコピーしました。
Warning control. Python’s warning machinery by default prints warning messages to sys.stderr. A typical warning message has the following form:
file:line: category: message
By default, each warning is printed once for each source line where it occurs. This option controls how often warnings are printed.
Multiple -W options may be given; when a warning matches more than one option, the action for the last matching option is performed. Invalid -W options are ignored (though, a warning message is printed about invalid options when the first warning is issued).
Starting from Python 2.7, DeprecationWarning and its descendants are ignored by default. The -Wd option can be used to re-enable them.
Warnings can also be controlled from within a Python program using the warnings module.
The simplest form of argument is one of the following action strings (or a unique abbreviation) by themselves:
ignore
Ignore all warnings.
default
Explicitly request the default behavior (printing each warning once per source line).
all
Print a warning each time it occurs (this may generate many messages if a warning is triggered repeatedly for the same source line, such as inside a loop).
module
Print each warning only the first time it occurs in each module.
once
Print each warning only the first time it occurs in the program.
error:
Raise an exception instead of printing a warning message.
The full form of argument is:
action:message:category:module:line
Here, action is as explained above but only applies to messages that match the remaining fields. Empty fields match all values; trailing empty fields may be omitted. The message field matches the start of the warning message printed; this match is case-insensitive. The category field matches the warning category. This must be a class name; the match tests whether the actual warning category of the message is a subclass of the specified warning category. The full class name must be given. The module field matches the (fully-qualified) module name; this match is case-sensitive. The line field matches the line number, where zero matches all line numbers and is thus equivalent to an omitted line number.
わかりました。 AFAIKこれは猿のパッチと呼ばれます。はい、私はusercustomize.pyがこのような猿のパッチを当てるのに良い場所だと思います。ありがとうございました。 – guettli
@guettli、それは、monkeypatchingです。ソースが変更されず、侵入によってロジックが変更されないので、これを使用すると正当なケースかもしれませんが、ロギングを効果的に追加するだけです。 – RebelWithoutAPulse