Closed SilenZcience closed 1 year ago
this way the kernel can be started bei either "python3 -m prolog_kernel", or simply "prolog_kernel", which then solves the problem of different python-executable commands, like "python3", "python", or "py"
This is definetly not a good solution, i apologize. The console-entry point seems to do some weird recursive stuff when building the package
this way the kernel can be started bei either "python3 -m prolog_kernel", or simply "prolog_kernel", which then solves the problem of different python-executable commands, like "python3", "python", or "py"