Describe the bug
logging.warn() was deprecated in Python 3.2 and removed in Python 3.12. The following call sites still use it:
owtf/shell/base.py line 204: logging.warn(out.decode("utf-8"))
owtf/shell/interactive.py line 38: logging.warn("ERROR - Communication channel closed - %s", abort_message)
owtf/shell/interactive.py line 56: logging.warn("ERROR: read - The Communication channel is down!")
owtf/shell/interactive.py line 100: logging.warn("ERROR: Run - The Communication Channel is down!")
Since the project targets python >= 3.11, these calls will raise AttributeError on any Python 3.12+ environment.
Note: owtf/shell/pexpect_sh.py has the same issue (lines 36, 57, 101, 126, 128).
Expected behavior
All calls should use logging.warning(), which has been the correct method since Python 3.2.
Environment
- Python 3.12+ (AttributeError on removed method)
Describe the bug
logging.warn()was deprecated in Python 3.2 and removed in Python 3.12. The following call sites still use it:owtf/shell/base.pyline 204:logging.warn(out.decode("utf-8"))owtf/shell/interactive.pyline 38:logging.warn("ERROR - Communication channel closed - %s", abort_message)owtf/shell/interactive.pyline 56:logging.warn("ERROR: read - The Communication channel is down!")owtf/shell/interactive.pyline 100:logging.warn("ERROR: Run - The Communication Channel is down!")Since the project targets
python >= 3.11, these calls will raiseAttributeErroron any Python 3.12+ environment.Note:
owtf/shell/pexpect_sh.pyhas the same issue (lines 36, 57, 101, 126, 128).Expected behavior
All calls should use
logging.warning(), which has been the correct method since Python 3.2.Environment