Add support and distribution for Python Wheels

[pmisik]

Hi,

We started using pygit2 because we it gives us much better performance comparing to executing git commands with parsing its outputs from pipes on Windows. Unfortunately our build environment (several build machines) does not use vs2008. So it is little trickier to distribute the current version of pygit2 on all machines.

I would really appreciate if pygit2 will start distributing pygit2 also as wheel package. See http:https://pythonwheels.com/

I think much more people would appreciate. It would simplify usage and distribution.
I’ve found http:https://www.lfd.uci.edu/~gohlke/pythonlibs/#pygit2 did it for some versions.

Have you considered to add support for Python Wheels a in the near future?

Thanks

Palo

[jdavid]

Hi Palo,

I will gladly review a Pull Request adding support for Python Wheels, but there is not yet such PR.

(Personally I have never used Python wheels.)

[chason]

Making Wheels is not a code change, but an operational change. Python Wheels as distributed by PyPI would need to be generated on the target platforms. Currently only Mac OS X and Windows are supported by PyPI. I'm not sure how the build process is managed right now.

This would be useful for people installing libgit2 on Windows in particular, as compiling the C parts of the code would no longer be necessary.

[beniwohli]

In a recent development, support for binary wheels for Linux has been added do pip/pypi, see https://github.com/pypa/manylinux

I'll play around with this a bit to see if we could get a binary wheel for pygit2 going.

[affixalex]

Big ol' +1 for this, it'd be a huge feather in the proverbial cap!

[beniwohli]

FYI, my current state is here: beniwohli/mygit2@ed4aa030b

It builds the manylinux1 binary wheels correctly as far as I can tell, but there is still some cleaning up to do

[techtonik]

If AppVeyor is enabled #652 then fresh wheels could be found in its artifacts tab.

[techtonik]

Fixed by #662.

[jdavid]

It remains to automate the process of uploading the wheels from AppVeyor to Pypi on release.
These links have been provided by @techtonik in issue #662

• http:https://refi64.com/posts/using-appveyor-to-distribute-python-wheels.html
• https://www.appveyor.com/docs/deployment/
• https://www.appveyor.com/docs/appveyor-yml/

[jdavid]

Finally did set up to automatically upload the wheels from Appveyor. Working fine!

Closing this.

[webknjaz]

FTR it looks like AppVeyor builds windows wheels without SSH support:

-- Disabled features:
 * debugpool, debug pool allocator
 * tracing, tracing support
 * SSH, SSH transport support
 * SPNEGO, SPNEGO authentication support
 * iconv, iconv encoding conversion support

[cjolowicz]

macOS wheels are also built without SSH support:

-- Disabled features:
 * debugpool, debug pool allocator
 * SSH, SSH transport support
 * SPNEGO, SPNEGO authentication support

https://github.com/libgit2/pygit2/runs/638662265?check_suite_focus=true#step:7:111

pygit2/.github/workflows/macos.yml

Line 80 in 83b63cd

-DUSE_SSH=NO

[webknjaz]

@cjolowicz I believe that the PR submitter who added that GHA workflow just went for a simple initial solution and it should be easy enough to iterate on this. You may try sending a PR that enables this flag and adds something like brew install libssh2 to that workflow.