Open ArnaudBelcour opened 2 years ago
Your diagnostic is right ; this changes a lot for clyngor, which suddenly doesn't need a large part of its source code and will be simplifiable, once the difference between clingo module and binary will be worked out (especially, as you point it out, time limit and constants options).
For the moment, please use your fix, or call clyngor.use_clingo_binary()
right after importing the clyngor package.
Hi,
While using powergrasp in metage2metabo, I encountered the following error:
This issue occurs recently (with Python
3.8.10
and the github version of powergrasp0.8.19.dev0
) and I think it is linked to the release of clyngor0.4.1
and especially the fact the clingo python package is now a dependency of clyngor. Due to this, the clingo package is always available so the variableuse_clingo_module
is always set toTrue
and leads to this error.Putting a
use_clingo_module=False
in clyngor call solves the issue for me. But maybe there is a better way to handle this.