-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release boolector as a PyPi package #49
Comments
Hi Matthew, Thanks for the offer! Would you be also willing to take care and maintain PyPi releases for new versions of Boolector? As soon as there is a PyPi package users probably expect it to be up-to-date and I'm not sure if we currently have the bandwidth to do it ourselves. Cheers, |
Hi Mathias,
Yes, I'd very much be willing to maintain and update the PyPi release as
new versions of Boolector become available.
Best Regards,
Matthew
…On Thu, Jun 6, 2019 at 8:58 PM Mathias Preiner ***@***.***> wrote:
Hi Matthew,
Thanks for the offer! Would you be also willing to take care and maintain
PyPi releases for new versions of Boolector? As soon as there is a PyPi
package users probably expect it to be up-to-date and I'm not sure if we
currently have the bandwidth to do it ourselves.
Cheers,
Mathias
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#49?email_source=notifications&email_token=AAKHLBKTJMFS73ZG24PXVNTPZHMHXA5CNFSM4HS5JGHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXEY64Q#issuecomment-499748722>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKHLBL5CDHI7G5EQ6JT45DPZHMHXANCNFSM4HS5JGHA>
.
|
That's great! Thanks! You can go ahead with the PyPi package. Let us know if you need anything from us! |
@mballance any progress on this? I'd be very interested in a PyPI package for Boolector as well. |
@obijywk, great to hear that you are also interested in this! This project has been lagging behind a couple of my other projects, but I expect to be able to get an initial version ready in the next week or so. Turns out Python packaging has lots of moving parts -- especially if the package involves native extensions like Boolector does. Just out of curiosity, what is your preferred platform (eg Windows, Linux, OS-X)? -Matthew |
Yeah, I don't expect this to be trivial to do :-/ let me know if there's anything I can do to help. I'm only interested in Linux. |
Okay, I have an initial version that seems to be working. Building a binary package that should work across Linux versions requires using a very old version of Centos, which required a few small patches to the Boolector and Lingeling sources.
Note that the binary packages are Linux-only at the moment, and only on the 'Testing' PyPi site. |
Worked for me! I tried it in https://colab.research.google.com by running the following:
so not sure exactly what kind of Linux it's running under, but it worked. |
That's great to hear, @obijywk! It's working for me as well, so I guess the next step is to figure out how to get this more-integrated with the CI environment that Boolector uses. |
any progress on getting this into the real PyPI (not the test instance)? looking forward to adding it to requirements.txt for my project. |
Yes, actually. I've been working on getting an Azure pipelines project setup within Boolector to automatically build and push a release to PyPi, since I believe that is the right path forward. At the moment, I believe I have everything working on a branch, with a PR to come. You should be able to install directly from PyPi now. As always, feedback is much appreciated! -Matthew |
Here's a link to the updated pull request: #72 |
Any chance for Windows support? Currently getting this:
Build on install is unlikely to work with so many dependencies so prebuilt binaries would be appreciated. |
same story on Mac:
|
Hi @skochinsky, I agree that both Windows and OS-X support are desirable. Of the two, Windows seems more difficult because Python packaging wants native packages to be compiled with Visual Studio compilers. Unfortunately, Boolector doesn't compile cleanly with VS at the moment. OS-X may be simpler, but I don't have any personal experience here. Are you able to help with either of these issues? I would ask the Boolector maintainers whether there is interest/openness to a Visual Studio build of Boolector. Based on my initial investigation I suspect it's quite doable, though it appears it will require a non-trivial number of mostly-trivial changes. -Matthew |
Added with #72. |
Hello,
I've been using Boolector via the C API, and have recently started using the Python interface. I'd like to have Boolector available via the PyPi package repository (pypi.org), and it doesn't appear to be directly available at the moment. I'm happy to volunteer to put together such a package, but wanted to check if there are concerns about doing so.
Thanks,
Matthew
The text was updated successfully, but these errors were encountered: