splunk / splunk/splunk-sdk-python

Splunk core -> python3.13

Offen
#785 0 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Vorherrschende Sprache
Python
Sterne
743
Forks
387
Ø Merge
42 Min.
Gemergte PRs (30 T.)
4

Beschreibung

Hi all,

Thank you for your efforts in getting some work done in the SDK.

Unfortunately, the requirement for Python 3.13, driven by the libraries used in the ai subpackage, renders all new SDK releases unusable for app developers. This is simply because there are multiple still-supported Splunk Enterprise versions that cannot use Python 3.13.

https://www.splunk.com/en_us/legal/splunk-software-support-policy.html#core

Version End of Support Date
9.3 Jul 24 2026
9.4 Dec 16 2026
10.0 Jul 28 2027

I propose creating a second project for the AI-related work and keeping splunk-sdk-python focused on its core purpose. Then you could do something like:

# splunk-sdk
[project]
name = "splunk-sdk"
requires-python = ">=3.9"

[project.optional-dependencies]
ai = [
  "splunk-sdk-ai==1.0.0",
]

# splunk-sdk-ai
[project]
name = "splunk-sdk-ai"
requires-python = ">=3.13"

dependencies = [
  "splunk-sdk>=3.0.0",
  "httpx==0.28.1",
  "langchain>=1.2.18",
  "mcp>=1.27.1",
  "pydantic>=2.13.4",
]

With this, it would be possible to just install the required package for 3.9 as well as pip install "splunk-sdk[ai]" that would fail on python3.9.

Best,
Simon

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Rechercherichtung

Start by reviewing the current dependency metadata and the ai subpackage to understand how Python 3.13 is imposed on the SDK. The proposed outcome is a core package that remains usable on Python 3.9 and a separately installable AI package with the newer requirement; the issue does not name specific files or tests.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
python
Bereich
build-system, developer-experience
Issue-Typ
Refactoring
Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Aktivitätsstatus
Ruhig
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.