JuliaPy / JuliaPy/PyCall.jl

replace `py_str` with `py_cmd` literal?

Offen
#793 3 Kommentare 2 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Julia
Sterne
1.5k
Forks
186
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

I think, semantically it makes more sense to use custom command literals instead of string literals for code in other languages, since I think it is important to distinguish code from plain strings. The default shell is already a different language within Julia, so I think it is reasonable to extend this concept to interop with other languages. This could also then be used by editors to customize syntax highlighting for Python code inside Julia, as already proposed in https://github.com/JuliaEditorSupport/julia-emacs/issues/132. The current string syntax could still be kept around, of course, and perhaps deprecated eventually. I would be curious to hear others' opinions on this.

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Rechercherichtung

No implementation files or tests are identified. Start by reviewing current `py_str` usage and the linked Julia Emacs discussion, then clarify the proposed `py_cmd` syntax, compatibility expectations, and editor integration. Done requires an agreed design before implementation can be scoped.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
julia, python
Bereich
api
Issue-Typ
Feature
Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Aktivitätsstatus
Veraltet
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
25/100

Neue Issues direkt in Ihr Postfach

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