View Issue Details

IDProjectCategoryView StatusLast Update
0017530ScribusScripterpublic2025-05-29 06:45
ReporterFoxy Assigned To 
PrioritynormalSeverityfeatureReproducibilityalways
Status newResolutionopen 
Product Version1.6.4 
Summary0017530: Devtools support for script development
DescriptionLinters, language servers, and other external dev tools cannot access the "scribus" Python package.
Steps To Reproduce1. Open a Scibus file with any code editor with Python support
2. The "scribus" package cannot be found, and hence there is no devtools support for names defined in such a package
Additional InformationI am not familiar with C FFI in Python, but I seem to understand the Scribus Python API is being developed at /scribus/plugins/scriptplugin. It would be enough to generate a *.pyi file (https://typing.python.org/en/latest/guides/writing_stubs.html). Those work with most Python LSPs/linters.
Tagsscripter
PatchNo

Relationships

child of 0017536 new Metabug: improvements to the Scripter for Scribus 1.8 

Activities

cbradney

2025-05-24 12:47

administrator   ~0052648

There is no Scribus Python package. The python API is for internal use with scripts run within Scribus or its console, not externally.

Foxy

2025-05-24 13:23

reporter   ~0052650

Yes, I am aware of that. My proposal is to allow script authors to be able to use their DevTools' features (e.g., autocomplete of function names from the Scribus Python API).

ale

2025-05-24 15:27

manager   ~0052652

i will have a look at it...

ale

2025-05-24 19:36

manager   ~0052654

since the scripter is not available as a python package, i think that it will not be possible to use one of the tools on the linked page.

but, if i understand it correctly, the format is pretty simple and it should be possible to create "manually".

... time to finish the new script for the export of the scripter documentation.... and then check if i can produce the pyi file, too.

Foxy

2025-05-24 20:38

reporter   ~0052655

Yes, there's no .h -> .pyi automatic converter that I am aware of. Ideally, the first line from each QT_TR_NOOP annotation could be used to also document the types pf the parameters and of the return value, whereas the rest could be used as a plain doc comment.

Issue History

Date Modified Username Field Change
2025-05-24 11:52 Foxy New Issue
2025-05-24 11:52 Foxy Tag Attached: plugin
2025-05-24 11:52 Foxy Tag Attached: plugins
2025-05-24 11:52 Foxy Tag Attached: python
2025-05-24 11:52 Foxy Tag Attached: scripter
2025-05-24 12:47 cbradney Note Added: 0052648
2025-05-24 13:23 Foxy Note Added: 0052650
2025-05-24 15:27 ale Note Added: 0052652
2025-05-24 19:36 ale Note Added: 0052654
2025-05-24 20:38 Foxy Note Added: 0052655
2025-05-29 06:40 ale Tag Detached: plugins
2025-05-29 06:40 ale Tag Detached: plugin
2025-05-29 06:40 ale Tag Detached: python
2025-05-29 06:45 ale Relationship added child of 0017536