-
-
Notifications
You must be signed in to change notification settings - Fork 12.4k
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
gpgme: package python3 bindings as well - require python3 for build #33129
Conversation
When building Python bindings, we usually make the |
@fxcoudert ; I'd propose an exception in this case because the package is useful if you only want the C bindings but the other language bindings have already been included. If you want to use it with python then, obviously, you need to have python installed. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
@Stale bot please don't mark this issue as stale; It's waiting for @fxcoudert to have time to reply. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Oops. Completely forgot about that one. I suppose it's okay-ish. |
@BrewTestBot test this please |
Currently gpgme doesn't package the python3 bindings, only the python2.7 ones. By adding a build dependency to python (== python 3) we ensure that the python3 bindings are also built and packaged.
brew install --build-from-source <formula>
, where<formula>
is the name of the formula you're submitting?brew audit --strict <formula>
(after doingbrew install <formula>
)?A note on this PR; during testing I discovered that if you have standard python.org python installed then it does't find the bindings. I wonder if there is anything that could be easily done to make homebrew bindings automatically visible to python.org python. The debian solution is to have a dist-packages directory which is supposed to be visible in all python versions but come after the site-packages allowing packages there to be used but overridden as needed.