Re: [GNC-dev] WebKitGtk now defaults to Gtk4

[Adrien Monteleone]

Thank you for the explanation John. I seem to recall a bit of that from 
an older discussion.


While it seems there is no ideal all-in-one solution, might two of your 
last three suggestions be doable or is each one a serious pile of work 
on its own?


That is:

*Send the HTML/JS/CSS to the default browser
*Write reports directly to PDF

The drill-down links I think get lost either way, and maybe that is 
unacceptable, but View, Print, PDF export, and get charts. (The writing 
to PDF would just be for export)


And I'm not quite following the loss of drill-down links on the first 
option. Certainly, I can open a local HTML file in my browser and it can 
contain links to local resources. Is there a way to expose a URI to a 
GnuCash transaction or other resource that might work? Or is the fact 
that it has to leave 'GTK land' for 'native land' in the browser and 
back in such a case the problem? Or is it that targeting anything within 
the data file is the tricky/impossible part? (I admit, while I've used 
local HTML to access local files, I've never tried to access only a 
portion of a file or even a marker in a file)


Apologies if my lack of understanding the guts of it all is noise.

Regards,
Adrien

On 11/19/23 11:20 PM, john wrote:

The reason for selecting WebKitGtk is the Gtk: It had WebKitWebView and was 
supported in most distros and Mingw.

The Mozilla team seem to have stopped maintaining their embedding facility 
around 2015 and it is apparently badly bit-rotted.

Blink is Chromium's rendering engine so that's the same as Sherlock's suggested 
CEF, i.e. Chromium Embedded Framework. It supports Gtk only on Linux; on macOS 
and Windows it build to the native toolkits, so we'd have to hack the build to 
provide Gtk3 on macOS and Windows. There's no mention of support for MinGW, so 
that might not be possible. The level of effort needed both to get and keep the 
ports working might make it impractical even if it is possible, but the only 
way to find that out is to try.

Note that while most repos have a Chromium package, only Arch and Nix have CEF 
packages. Adding it as a GnuCash dependency is likely to get most distros to 
drop us, so nearly everybody on Linux/BSD would be forced to use flatpak.


___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Windows Build VM

[john]

> On Nov 19, 2023, at 10:23, Manfred Usselmann  wrote:
> 
> Am 2023-11-19 18:26, schrieb john:
> 
>> 
>> 
>>> On Nov 19, 2023, at 08:02, Manfred Usselmann  wrote:
>>> 
>>> Am 2023-11-18 20:32, schrieb john:
>>> 
>>> 
>>> 
>>> On Nov 17, 2023, at 17:23, Manfred Usselmann  wrote:
>>> 
>>> Am 2023-11-17 05:58, schrieb john:
>>> 
>>> 
>>> 
>>> On Nov 16, 2023, at 14:25, Manfred Usselmann  wrote:
>>> 
>>> Am 2023-11-16 18:41, schrieb john:
>>> 
>>> 
>>> 
>>> On Nov 16, 2023, at 03:50, Manfred Usselmann  wrote:
>>> 
>>> Hi,
>>> 
>>> Am 2023-11-07 04:53, schrieb john:
>>> 
>>> 
>>> 
>>> On Nov 6, 2023, at 16:12, Manfred Usselmann  wrote:
>>> 
>>> Hi John,
>>> 
>>> Am 2023-11-06 19:31, schrieb john:
>>> On Nov 6, 2023, at 05:11, Manfred Usselmann  wrote:
>>> Hi,
>>> Am 2023-10-01 17:47, schrieb john:
>>> On Oct 1, 2023, at 06:00, Derek Atkins  wrote:
>>> On Sun, October 1, 2023 12:00 am, flywire wrote:
>>> https://lists.gnucash.org/pipermail/gnucash-user/2023-April/106619.html
>>> John wrote:
>>> we don't have a Windows CI action, the nightly builds are done with the
>>> https://github.com/gnucash/GnuCash-on-windows powershell scripts on a
>>> Windows VM in Derek's basement.
>>> The nightly builds are those on 
>>> https://code.gnucash.org/builds/win32/stable/, right?
>>> Would it be possible to additonally provide a version there which includes 
>>> the Python bindings?
>>> No, there's no way to make that work with an installed package.
>>> Since there already exists a working build environment, I would hope that 
>>> it's not too much work?
>>> That depends on what you want to use for your Python. If you can use the 
>>> MSYS2 environment from Powershell (some MSYS2 things work directly in 
>>> Powershell, others need a Bash shell) then you can simply add 
>>> -DWITH_PYTHON=ON to the CMakeArgs in jhbuild and build it. Don't run the 
>>> installer, just add 
>>> c:\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages to PYTHONPATH 
>>> and run your scripts.
>>>  
>>> After starting from scratch I'm now able to run a successful build 
>>> including the Python bindings.
>>>  
>>> After adding
>>> C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages
>>> to PYTHONPATH my script now starts and does no longer complain about the 
>>> gnucash imports.
>>>  
>>> But the script aborts and it looks like Python does not find 
>>> _gnucash_core_c.dll in this folder. :-(
>>>  
>>> I also added 
>>> C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages\gnucash
>>>  to the Windows Path, but this does not help.
>>> Traceback (most recent call last):
>>>   File 
>>> "C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages\gnucash\gnucash_core_c.py",
>>>  line 14, in swig_import_helper
>>> return importlib.import_module(mname)
>>>^^
>>>   File 
>>> "C:\Users\mu\AppData\Local\Programs\Python\Python312\Lib\importlib\__init__.py",
>>>  line 90, in import_module
>>> return _bootstrap._gcd_import(name[level:], package, level)
>>>
>>>   File "", line 1381, in _gcd_import
>>>   File "", line 1354, in _find_and_load
>>>   File "", line 1318, in 
>>> _find_and_load_unlocked
>>> ModuleNotFoundError: No module named 'gnucash._gnucash_core_c'
>>> 
>>> During handling of the above exception, another exception occurred:
>>> 
>>> Traceback (most recent call last):
>>>   File "C:\Users\mu\Documents\Nextcloud_Manfred\Manfred 
>>> Entwicklung\USS\Projects\GCToolbox\GCImport\gcimport.py", line 18, in 
>>> 
>>> from gnucash import Session, Account, Transaction, Split, GncNumeric, 
>>> GUID, GUIDString, gnucash_core_c
>>>   File 
>>> "C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages\gnucash\__init__.py",
>>>  line 6, in 
>>> from gnucash.gnucash_core import *
>>>   File 
>>> "C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages\gnucash\gnucash_core.py",
>>>  line 36, in 
>>> from gnucash import gnucash_core_c
>>>   File 
>>> "C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages\gnucash\gnucash_core_c.py",
>>>  line 17, in 
>>> _gnucash_core_c = swig_import_helper()
>>>   
>>>   File 
>>> "C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages\gnucash\gnucash_core_c.py",
>>>  line 16, in swig_import_helper
>>> return importlib.import_module('_gnucash_core_c')
>>>^^
>>>   File 
>>> "C:\Users\mu\AppData\Local\Programs\Python\Python312\Lib\importlib\__init__.py",
>>>  line 90, in import_module
>>> return _bootstrap._gcd_import(name[level:], package, level)
>>>
>>> ModuleNotFoundError: No module named 

Re: [GNC-dev] WebKitGtk now defaults to Gtk4

[john]

The reason for selecting WebKitGtk is the Gtk: It had WebKitWebView and was 
supported in most distros and Mingw. 

The Mozilla team seem to have stopped maintaining their embedding facility 
around 2015 and it is apparently badly bit-rotted. 

Blink is Chromium's rendering engine so that's the same as Sherlock's suggested 
CEF, i.e. Chromium Embedded Framework. It supports Gtk only on Linux; on macOS 
and Windows it build to the native toolkits, so we'd have to hack the build to 
provide Gtk3 on macOS and Windows. There's no mention of support for MinGW, so 
that might not be possible. The level of effort needed both to get and keep the 
ports working might make it impractical even if it is possible, but the only 
way to find that out is to try.

Note that while most repos have a Chromium package, only Arch and Nix have CEF 
packages. Adding it as a GnuCash dependency is likely to get most distros to 
drop us, so nearly everybody on Linux/BSD would be forced to use flatpak.

Regards,
John Ralls

> On Nov 19, 2023, at 11:16, Adrien Monteleone  
> wrote:
> 
> Gecko? Blink?
> 
> I'm sure there was a reason for selecting WebKit originally. Does that still 
> hold true?
> 
> Regards,
> Adrien
> 
> On 11/18/23 10:00 PM, john wrote:
>> I spent some time this afternoon poking at webkit replacement. The options I 
>> found are:
>> * Keep using WebKitGtk
>> * Figure out how to wrap a native (meaning Apple AppKit or Microsoft) 
>> WebView in a GtkWidget
>> * Send the HTML/JS/CSS to the default browser. This will lose the links to 
>> GnuCash objects like transactions
>> * Configure a GtkTextView to understand HTML tags. This doesn't support 
>> charts, printing, or PDF export.
>> * Write reports directly to PDF. There are libraries out there but I didn't 
>> find any FLOSS ones that mention CSS styling or drawing charts in their 
>> feature sets.
>> Any other ideas?
> 
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] WebKitGtk now defaults to Gtk4

[Adrien Monteleone]

Gecko? Blink?

I'm sure there was a reason for selecting WebKit originally. Does that 
still hold true?


Regards,
Adrien

On 11/18/23 10:00 PM, john wrote:

I spent some time this afternoon poking at webkit replacement. The options I 
found are:
* Keep using WebKitGtk
* Figure out how to wrap a native (meaning Apple AppKit or Microsoft) WebView 
in a GtkWidget
* Send the HTML/JS/CSS to the default browser. This will lose the links to 
GnuCash objects like transactions
* Configure a GtkTextView to understand HTML tags. This doesn't support charts, 
printing, or PDF export.
* Write reports directly to PDF. There are libraries out there but I didn't 
find any FLOSS ones that mention CSS styling or drawing charts in their feature 
sets.

Any other ideas?


___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] WebKitGtk now defaults to Gtk4

[Sherlock]

CEF?

> On Nov 18, 2023, at 8:00 PM, john  wrote:
> 
> I spent some time this afternoon poking at webkit replacement. The options I 
> found are:
> * Keep using WebKitGtk
> * Figure out how to wrap a native (meaning Apple AppKit or Microsoft) WebView 
> in a GtkWidget
> * Send the HTML/JS/CSS to the default browser. This will lose the links to 
> GnuCash objects like transactions
> * Configure a GtkTextView to understand HTML tags. This doesn't support 
> charts, printing, or PDF export.
> * Write reports directly to PDF. There are libraries out there but I didn't 
> find any FLOSS ones that mention CSS styling or drawing charts in their 
> feature sets.
> 
> Any other ideas?
> 
> Regards,
> John Ralls
> 
>> On Nov 18, 2023, at 11:03, john  wrote:
>> 
>> 
>> WebKitGtk. When I wrote that I was thinking Gtk4, but that won't work on 
>> Windows because WebKitGtk 2.4, the last release before they ripped out all 
>> of the Windows support code, obviously doesn't support Gtk4.
>> 
>> I don't know that we have until 2026 because I don't know what are the other 
>> WebKitGtk based applications Carlos referred to so I don't know where they 
>> are on migrating. We know from experience that nobody's going to wait for us.
>> 
>> I couldn't find the earlier discussion about release cycles either. The 
>> options are to keep doing what we're doing or to switch to a more continuous 
>> model where stable is the only central branch and feature branches are 
>> merged in when they're ready. We'd switch to a year-based versioning similar 
>> to Ubuntu's; I proposed -n, e.g. 2024-1, 2024-2, etc. on the same 
>> quarterly schedule. There would be no beta releases; the few users willing 
>> to test could do so with nightly builds.
>> 
>> If we don't change to the continuous model, 6.0 would drop 29 March 2026, 
>> see https://wiki.gnucash.org/wiki/Release_Schedule#Goals_for_6.0. 8 March is 
>> string freeze.
>> 
>> Regards,
>> John Ralls
>> 
>> 
>>> On Nov 18, 2023, at 02:54, Robert Fewell <14ubo...@gmail.com> wrote:
>>> 
>>> Can I get clarification, is that migrating to Gtk4 or move away from 
>>> WebKitGtk ?
>>> 
>>> I suppose either change would be a major one so that would be version 6.0 I 
>>> assume.
>>> I seem to recall there was a question on release cycles but can not find 
>>> where, so if 6.0 is that still 08/03/2026 ?
>>> 
>>> Regards,
>>> Bob
>>> 
>>> On Fri, 17 Nov 2023 at 17:15, john >> > wrote:
 WebKitGtk 2.43.1 was just released and one of its changes is that it's 
 Gtk4 by default and one must specify a build option, -DGTK4=OFF, to use it 
 with Gtk3. I asked on the webkitgtk mailing list if there's a schedule for 
 dropping Gtk3 support. Carlos Garcia Campos replied "No, but it will take 
 a while I'm afraid. Most of the WebKitGTK based
 applications are still GTK3, I think."
 
 So we don't have a firm deadline yet, but this is a warning that we need 
 to get serious about migrating.
 
 Regards,
 John Ralls
 
 ___
 gnucash-devel mailing list
 gnucash-devel@gnucash.org 
 https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>> 
>> ___
>> gnucash-devel mailing list
>> gnucash-devel@gnucash.org
>> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
> 
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Windows Build VM

[john]

> On Nov 19, 2023, at 08:02, Manfred Usselmann  wrote:
> 
> Am 2023-11-18 20:32, schrieb john:
> 
>> 
>> 
>>> On Nov 17, 2023, at 17:23, Manfred Usselmann  wrote:
>>> 
>>> Am 2023-11-17 05:58, schrieb john:
>>> 
>>> 
>>> 
>>> On Nov 16, 2023, at 14:25, Manfred Usselmann  wrote:
>>> 
>>> Am 2023-11-16 18:41, schrieb john:
>>> 
>>> 
>>> 
>>> On Nov 16, 2023, at 03:50, Manfred Usselmann  wrote:
>>> 
>>> Hi,
>>> 
>>> Am 2023-11-07 04:53, schrieb john:
>>> 
>>> 
>>> 
>>> On Nov 6, 2023, at 16:12, Manfred Usselmann  wrote:
>>> 
>>> Hi John,
>>> 
>>> Am 2023-11-06 19:31, schrieb john:
>>> On Nov 6, 2023, at 05:11, Manfred Usselmann  wrote:
>>> Hi,
>>> Am 2023-10-01 17:47, schrieb john:
>>> On Oct 1, 2023, at 06:00, Derek Atkins  wrote:
>>> On Sun, October 1, 2023 12:00 am, flywire wrote:
>>> https://lists.gnucash.org/pipermail/gnucash-user/2023-April/106619.html
>>> John wrote:
>>> we don't have a Windows CI action, the nightly builds are done with the
>>> https://github.com/gnucash/GnuCash-on-windows powershell scripts on a
>>> Windows VM in Derek's basement.
>>> The nightly builds are those on 
>>> https://code.gnucash.org/builds/win32/stable/, right?
>>> Would it be possible to additonally provide a version there which includes 
>>> the Python bindings?
>>> No, there's no way to make that work with an installed package.
>>> Since there already exists a working build environment, I would hope that 
>>> it's not too much work?
>>> That depends on what you want to use for your Python. If you can use the 
>>> MSYS2 environment from Powershell (some MSYS2 things work directly in 
>>> Powershell, others need a Bash shell) then you can simply add 
>>> -DWITH_PYTHON=ON to the CMakeArgs in jhbuild and build it. Don't run the 
>>> installer, just add 
>>> c:\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages to PYTHONPATH 
>>> and run your scripts.
>>>  
>>> After starting from scratch I'm now able to run a successful build 
>>> including the Python bindings.
>>>  
>>> After adding
>>> C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages
>>> to PYTHONPATH my script now starts and does no longer complain about the 
>>> gnucash imports.
>>>  
>>> But the script aborts and it looks like Python does not find 
>>> _gnucash_core_c.dll in this folder. :-(
>>>  
>>> I also added 
>>> C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages\gnucash
>>>  to the Windows Path, but this does not help.
>>> Traceback (most recent call last):
>>>   File 
>>> "C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages\gnucash\gnucash_core_c.py",
>>>  line 14, in swig_import_helper
>>> return importlib.import_module(mname)
>>>^^
>>>   File 
>>> "C:\Users\mu\AppData\Local\Programs\Python\Python312\Lib\importlib\__init__.py",
>>>  line 90, in import_module
>>> return _bootstrap._gcd_import(name[level:], package, level)
>>>
>>>   File "", line 1381, in _gcd_import
>>>   File "", line 1354, in _find_and_load
>>>   File "", line 1318, in 
>>> _find_and_load_unlocked
>>> ModuleNotFoundError: No module named 'gnucash._gnucash_core_c'
>>> 
>>> During handling of the above exception, another exception occurred:
>>> 
>>> Traceback (most recent call last):
>>>   File "C:\Users\mu\Documents\Nextcloud_Manfred\Manfred 
>>> Entwicklung\USS\Projects\GCToolbox\GCImport\gcimport.py", line 18, in 
>>> 
>>> from gnucash import Session, Account, Transaction, Split, GncNumeric, 
>>> GUID, GUIDString, gnucash_core_c
>>>   File 
>>> "C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages\gnucash\__init__.py",
>>>  line 6, in 
>>> from gnucash.gnucash_core import *
>>>   File 
>>> "C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages\gnucash\gnucash_core.py",
>>>  line 36, in 
>>> from gnucash import gnucash_core_c
>>>   File 
>>> "C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages\gnucash\gnucash_core_c.py",
>>>  line 17, in 
>>> _gnucash_core_c = swig_import_helper()
>>>   
>>>   File 
>>> "C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages\gnucash\gnucash_core_c.py",
>>>  line 16, in swig_import_helper
>>> return importlib.import_module('_gnucash_core_c')
>>>^^
>>>   File 
>>> "C:\Users\mu\AppData\Local\Programs\Python\Python312\Lib\importlib\__init__.py",
>>>  line 90, in import_module
>>> return _bootstrap._gcd_import(name[level:], package, level)
>>>
>>> ModuleNotFoundError: No module named '_gnucash_core_c'
>>> 
>>> Process finished with exit code 1
>>> 
>>> Do you also have 
>>> 

Re: [GNC-dev] Windows Build VM

[Manfred Usselmann]

Am 2023-11-18 20:32, schrieb john:

On Nov 17, 2023, at 17:23, Manfred Usselmann  
wrote:


Am 2023-11-17 05:58, schrieb john:

On Nov 16, 2023, at 14:25, Manfred Usselmann  
wrote:


Am 2023-11-16 18:41, schrieb john:

On Nov 16, 2023, at 03:50, Manfred Usselmann  
wrote:


Hi,

Am 2023-11-07 04:53, schrieb john:

On Nov 6, 2023, at 16:12, Manfred Usselmann  
wrote:

Hi John,

Am 2023-11-06 19:31, schrieb john:
On Nov 6, 2023, at 05:11, Manfred Usselmann  
wrote:

Hi,
Am 2023-10-01 17:47, schrieb john:
On Oct 1, 2023, at 06:00, Derek Atkins  wrote:
On Sun, October 1, 2023 12:00 am, flywire wrote:
https://lists.gnucash.org/pipermail/gnucash-user/2023-April/106619.html
John wrote:
we don't have a Windows CI action, the nightly builds are done with the
https://github.com/gnucash/GnuCash-on-windows powershell scripts on a
Windows VM in Derek's basement.
 The nightly builds are those on 
https://code.gnucash.org/builds/win32/stable/, right?
Would it be possible to additonally provide a version there which 
includes the Python bindings? No, there's no way to make that work with 
an installed package.


Since there already exists a working build environment, I would hope 
that it's not too much work?
 That depends on what you want to use for your Python. If you can use 
the MSYS2 environment from Powershell (some MSYS2 things work directly 
in Powershell, others need a Bash shell) then you can simply add 
-DWITH_PYTHON=ON to the CMakeArgs in jhbuild and build it. Don't run the 
installer, just add 
c:\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages to 
PYTHONPATH and run your scripts.


After starting from scratch I'm now able to run a successful build 
including the Python bindings.


After adding
C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages
to PYTHONPATH my script now starts and does no longer complain about the 
gnucash imports.


But the script aborts and it looks like Python does not find 
_gnucash_core_c.dll in this folder. :-(


I also added 
C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages\gnucash 
to the Windows Path, but this does not help.


Traceback (most recent call last):
  File 
"C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages\gnucash\gnucash_core_c.py", 
line 14, in swig_import_helper

return importlib.import_module(mname)
   ^^
  File 
"C:\Users\mu\AppData\Local\Programs\Python\Python312\Lib\importlib\__init__.py", 
line 90, in import_module

return _bootstrap._gcd_import(name[level:], package, level)
   
  File "", line 1381, in _gcd_import
  File "", line 1354, in _find_and_load
  File "", line 1318, in 
_find_and_load_unlocked

ModuleNotFoundError: No module named 'gnucash._gnucash_core_c'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Users\mu\Documents\Nextcloud_Manfred\Manfred 
Entwicklung\USS\Projects\GCToolbox\GCImport\gcimport.py", line 18, in 

from gnucash import Session, Account, Transaction, Split, 
GncNumeric, GUID, GUIDString, gnucash_core_c
  File 
"C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages\gnucash\__init__.py", 
line 6, in 

from gnucash.gnucash_core import *
  File 
"C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages\gnucash\gnucash_core.py", 
line 36, in 

from gnucash import gnucash_core_c
  File 
"C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages\gnucash\gnucash_core_c.py", 
line 17, in 

_gnucash_core_c = swig_import_helper()
  
  File 
"C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages\gnucash\gnucash_core_c.py", 
line 16, in swig_import_helper

return importlib.import_module('_gnucash_core_c')
   ^^
  File 
"C:\Users\mu\AppData\Local\Programs\Python\Python312\Lib\importlib\__init__.py", 
line 90, in import_module

return _bootstrap._gcd_import(name[level:], package, level)
   
ModuleNotFoundError: No module named '_gnucash_core_c'

Process finished with exit code 1
Do you also have 
C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib and 
C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib\gnucash 
in %PATH% ?


I've added them now, but it makes no difference.

Does 
C:\Users\mu\Entwicklung\GnuCash\gcdev64\gnucash\stable\inst\lib\python3.11\site-packages\gnucash\_gnucash_core_c.dll 
exist?


BTW the bindings also need _sw_app_utils.dll and _sw_core_utils.dll in 
that directory along with _gnucash_core_c.dll and various python files.


Yes, they are there the following files:

__init__.py
_gnucash_core_c.dll