threatq: fix py2-style artifacts resulting in SyntaxError

[Andrej730]

Contributing to Cortex XSOAR Content

Make sure to register your contribution by filling the contribution registration form

The Pull Request will be reviewed only after the contribution registration form is filled.

Status

• In Progress
• Ready
• In Hold - (Reason for hold)

Description

This file is the only syntax error present in the repo, see below.

content/Packs/ThreatQ/Integrations/ThreatQ/ThreatQ.py

Lines 106 to 108 in dc86e1f

	except Exception, e:
	results = {'ContentsFormat': formats['markdown'], 'Type': entryTypes['note'], 'Contents': "No results from ThreatQ"}
	return results

content/Packs/ThreatQ/Integrations/ThreatQ/ThreatQ.py

Lines 325 to 327 in dc86e1f

	except Exception, e:
	raise
	return_error(e)

uv run --no-project --python 3.10 -m compileall . -q
# ** Error compiling './Packs/ThreatQ/Integrations/ThreatQ/ThreatQ.py'...
#  File "./Packs/ThreatQ/Integrations/ThreatQ/ThreatQ.py", line 106
#    except Exception, e:
#           ^^^^^^^^^^^^
# SyntaxError: multiple exception types must be parenthesized

except Exception, e: looked like either artifact from Python 2 (Python was using this syntax instead of except Exception as e) or just a typo. To fix the issue I've dropped unused e in one case and replaced with as e in another.

Must have

• Tests
• Documentation

relates: https://jira-dc.paloaltonetworks.com/browse/CIAC-17494

[Copilot]

Pull request overview

This PR fixes remaining Python 2-style exception syntax in the ThreatQ integration that causes SyntaxError under Python 3, allowing the file to compile cleanly in the Cortex Content repo.

Changes:

• Replaced except Exception, e: with Python 3-compatible exception handlers.
• Removed an unused exception binding in one handler and added as e where the exception object is referenced.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[content-bot]

Thank you for your contribution. Your generosity and caring are unrivaled! Make sure to register your contribution by filling the Contribution Registration form, so our content wizard @kamalq97 will know the proposed changes are ready to be reviewed.
For your convenience, here is a link to the contributions SLAs document.

[content-bot]

Hi @Andrej730, thanks for contributing to the XSOAR marketplace. To receive credit for your generous contribution please follow this link.

[content-bot]

🤖 AI-Powered Code Review Available

Hi @kamalq97, you can leverage AI-powered code review to assist with this PR!

Available Commands:

• @marketplace-ai-reviewer start review - Initiate a full AI code review
• @marketplace-ai-reviewer re-review - Incremental review for new commits

[github-actions]

Thank you for your contribution. Your external PR has been merged and the changes are now included in one or more internal PRs for further review.

Note

Contributions containing XSIAM content (Modeling Rules, Parsing Rules, Correlation Rules, or Dashboards) are subject to an additional review process and may take longer to be merged to master.