In Github action, pip installs from pypi instead of dist
#1680
Replies: 3 comments 7 replies
-
Hey, Any idea on how I can debug this? I've tried reverting to a prior version of maturin, but that didn't do anything. I also tried using find to find the exact wheel, but that only works for the target where the first package found matches the current target. It's a total blocker on any of my work, I wasted the whole weekend trying to fix this. Seriously, at this stage, any tip would help. Thanks |
Beta Was this translation helpful? Give feedback.
-
Oh, good find! Thanks, I'll ask them.
…On Mon, Jun 26, 2023, 08:04 messense ***@***.***> wrote:
Found link file:///home/runner/work/nyx/nyx/dist/nyx_space-2.0.0a2-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl, version: 2.0.0a2
Local files found: /home/runner/work/nyx/nyx/dist/nyx_space-2.0.0a2-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Given no hashes to check 7 links for project 'nyx-space': discarding no candidates
Looks like pip found it but decided to discard it for some reason, maybe
you should ask pypa/pip.
—
Reply to this email directly, view it on GitHub
<#1680 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABEZV2BQQ22U4H7OOPC6DL3XNGJFFANCNFSM6AAAAAAZSSOTQI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
The only solution I have found is to change the version of the crate to one that does not exist on pypi. For example, since I'm developing version 2.0.0-beta, I have changed the crate version to be 2.0.0-beta-dev. Then, it works.
|
Beta Was this translation helpful? Give feedback.
-
Hi there,
This is an odd behavior I haven't seen before. With the CI file generated by maturin, one of the steps includes
pip install pkg_name --find-links dist --force-reinstall
. This typically works without issue.However, without changing the github action, a PR on my repo does not work anymore:
pip
now doesn't seem to find the package in thedist
folder and instead downloads it from pypi it seems. This behavior happens on windows, mac, and linux.The culprit is shown at the top of the build:
Version 2.0.0a2 is indeed what's currently on pypi, but I am expecting the CI to install the package built for this run.
Any idea what could be happening?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions