First ideas on modify the GIMP Python interpreter to be more interactive.
As for now, code from two sources has been grabbed:
- GIMP's Python Console under GPLv3
- SvenFestersen's GtkPyInterpreter under GPLv3
Update (28/03/21):
-
Huge refactor in original source codes.
-
A namespace python package structure has been implemented, adapted to GIMPs needs.
-
Logic from pure GTK3 is being split from GIMPs logic, then "apps" should have an isolated layer which runs outside GIMP.
-
Running 4 different Python Console approaches only changing a flag, to explore them:
- console.ConsoleDialog.run: The current GIMP python console with the GIMP logic.
- pyconsole.run: Only the widget of the python console of the current GIMP pyhthon console.
- gtkpyinterpreter.run: SvenFestersen's Python Console. Has a problem with a constant
None: Noneoutput. - gtkmatplotlibshell.run: SvenFestersen's Python Console with matplotlib integration!
-
The main problem integrating IPython is that the current approach (by importing it and call
IPython.embed()) yields to a problem with the parsing of the inputs. For example:
In [1]: import os
File "<ipython-input-1-5c84a8230b9f>", line 1
invalid syntax (<string>, line 1)
^
SyntaxError: invalid syntax
In [2]: a = 10
File "<ipython-input-2-5c84a8230b9f>", line 1
invalid syntax (<string>, line 1)
^
SyntaxError: invalid syntax
In [3]: hola
File "<ipython-input-3-74399d33e912>", line 1
name 'hola' is not defined
^
SyntaxError: invalid syntax
Metadata
Release files for gimp-console 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| gimp-console-0.2.0.tar.gz | 16.5 kB | Without provenance | Details for gimp-console-0.2.0.tar.gz |
Release files / gimp-console-0.2.0.tar.gz
| Download URL | gimp-console-0.2.0.tar.gz |
|---|---|
| Size | 16.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2e64a051f9d93311ab343a0105b15575e6cca76b2d4f5a0a6963087d5422560c
|
|
BLAKE2b-256 checksum How to use checksums |
73c54daf25275089558bea54493798a99ac813d51608fca7a2252cfd12ba5ba2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.3.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.0 CPython/3.8.6
|
Security for gimp-console 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.