conda/pycosat

Why the un-pythonic API?

asmeurer opened this issue · 2 comments

asmeurer commented

It may be too late to change this, but I'm curious why pycosat uses the un-Pythonic API of returning strings, instead of returning False when the cnf is unsatisfiable and raising an exception when the propagation limit is reached?

github-actions commented

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

  1. Verify that you can still reproduce the issue at hand
  2. Comment that the issue is still reproducible and include:
    - What OS and version you reproduced the issue on
    - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!

github-actions commented

Hi again!

This issue has been closed since it has not had recent activity.

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!