Update to latest upstream HGS-CVRP and auto-upload sdist+wheels to PyPI#34
Update to latest upstream HGS-CVRP and auto-upload sdist+wheels to PyPI#34mdealencar wants to merge 9 commits intochkwon:masterfrom
Conversation
…nd PyPI upload as GitHub action; bump version to 0.0.0.11
|
Setting up Trusted Publisher for PyHygese in PyPI: After you push a new version tag to any branch, e.g. 'v0.0.1', the action will do its thing and the project will be published and ready for |
…ith the compiled libs (ci.yml)
|
The auto release to PyPI is already setup with Do you think distributing wheels is a good idea for this package? I think the source distribution works with |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #34 +/- ##
==========================================
- Coverage 97.67% 0.00% -97.68%
==========================================
Files 4 4
Lines 215 219 +4
==========================================
- Hits 210 0 -210
- Misses 5 219 +214 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
I think wheels are a great advantage to any project, particularly when there are compiled extensions such as here. With wheels the target system does not need a C++ compiler set up and the installation is much faster. There is always the sdist as a fallback if the platform is not covered. |
…e the installed package instead of local folder
|
There was a nasty issue resulting from the dropping of There are three possible solutions to that:
If you are ok with using the first option, I think this PR is ready to merge. |
|
FYI: PyHygese is now available as hybgensea both in PyPI and conda-forge:
|
Supersedes #33
The HGS-CVRP changes from v2.0.0 to vidalt/HGS-CVRP@1a92795 involve a few extra args to AlgorithmParameters(), incorporated in PyHygese by this PR.
The build+publish workflow will build wheels for several 64bit platforms and is triggered manually or when a version tag is pushed ('v[0-9]+.[0-9]+.[0-9]+') to any PyHygese branch. The PyPI uploading uses the Trusted Publisher mechanism (the owner of project
hygeseneeds to set it up - see next message for instructions).It is possible to have the build system fetch the tag for setting project.version's value instead of using a hard-coded one in pyproject.toml, but that is not pursued in this PR.
This PR will also bump version to 0.0.0.11.