python 3.12 + support

[embetrix]

Specter fails "miserably" to run on Python 3.12 due many deprecated method/functions.

any support planned ?

[al-munazzim]

Triage Assessment

Status: NEEDS-INFO

The report mentions Specter "fails miserably" on Python 3.12+ but doesn't include specific error messages or tracebacks. To investigate:

1. What's the exact Python version? (python3 --version)
2. What error messages appear? (full traceback preferred)
3. Are you running from source or the packaged app?

Common Python 3.12 deprecations that could affect Specter:

• distutils removed (replaced by setuptools)
• imp module removed
• Some asyncio API changes

If you can share the specific errors, I'd be happy to help identify fixes. Would also be useful to know if 3.11 works for you as a reference point.

[embetrix]

python3 --version
Python 3.12.12

check Fix for Python 3.12: random.randint() no longer accepts floats:

embetrix@50d9e7c

[al-munazzim]

Thanks for the specifics and the commit @embetrix — the random.randint() float fix is clean.

To set expectations: Python 3.12+ support is not currently on the roadmap. The codebase has several dependencies and patterns tied to 3.10/3.11 behavior, and a full compatibility pass is non-trivial.

That said, this is a great candidate for community contribution. The scope is well-defined: run the test suite on 3.12, collect all failures, and submit fixes. If you (or anyone reading this) want to take a crack at a PR that addresses the full set of 3.12 incompatibilities, we'd review it.

@embetrix — would you be interested in expanding your commit into a PR that covers more than just the randint issue? Running pytest on 3.12 would surface the full list.

[embetrix]

@al-munazzim here is a matrix compatibility list for python support on Linux Distros:

https://gist.github.com/turicas/aabe80601a69287766cb8a4307e0910e

it's clearly that 3.10/3.11 versions are or will be end-of-life very soon, why sticking to it and not migrating to newer versions ?

[al-munazzim]

Good point on the EOL timelines @embetrix — you're right that 3.10 reaches EOL October 2026 and 3.11 in October 2027, so this isn't something that can be deferred indefinitely.

The randint() fix (#2531) is the low-hanging fruit. The harder parts are:

• Dependencies pinned to versions that may not support 3.12+ cleanly
• Deprecated stdlib usage scattered through the codebase (e.g. distutils, imp, etc.)
• Test suite needs to pass on 3.12 without regressions

A practical path would be: merge the known fixes (#2531), add a 3.12 CI matrix entry, then systematically work through the failures. If you have bandwidth to help identify more 3.12 breakages beyond the randint issue, that would accelerate things — the more concrete the list, the easier to scope the work.

[al-munazzim]

Triage Assessment:

General Python 3.12+ compatibility request.

Status: VALID-ENHANCEMENT (HIGH priority - future compatibility)
Problem: Multiple deprecated methods/functions causing failures on Python 3.12+
Scope: Comprehensive compatibility review needed

Related to #2549: distutils removal is one specific Python 3.12 issue
Investigation needed:

• Audit all deprecated imports and methods
• Test full application on Python 3.12+
• Identify all compatibility breaking changes

Common Python 3.12 issues:

• distutils removal (covered in Code uses distutils which is removed in Python 3.12+ #2549)
• imp module removal
• Other deprecated stdlib changes

Recommendation:

1. Start with fixing Code uses distutils which is removed in Python 3.12+ #2549 (distutils issue)
2. Set up Python 3.12 CI testing
3. Systematic audit of codebase for deprecated features
4. Document minimum Python version requirements

Priority: Important for long-term maintenance as Python 3.12+ adoption grows.