https://pantsbuild.org/ logo
Join Slack
Powered by
If I'm building my own Pants wheels, how do I avoi...
# development
f
If I'm building my own Pants wheels, how do I avoid this:
Copy code
19:46:48.38 [ERROR] 1 Exception encountered:

  BuildConfigurationError: Version mismatch: Requested version was 2.13.0a0, our version is 2.13.0a0+gitd1dd32a2.
Why is that wheel getting marked with a dirty tag?
built with 
USE_PY39=true build-support/bin/release.sh build-wheels
on commit 
release_2.13.0a0
w
the wheel building code marks the wheels that it builds as unstable, and then during releases we “reversion” the wheels to a stable version
👍🏻 1
but… i wouldn’t really recommend publishing stable versions privately. that could get very confusing
f
then how can I use a wheel that I build?
w
request the appropriate version… i think
f
doing this on arm
w
i.e., put 
2.13.0a0+gitd1dd32a2
in 
pants.toml
f
okay that works... just will mean that if I do this in the future, I'll need to build for both architectures so I can have these "unstable" wheels at the same version... or I guess I could hack the 
./pants
script
👍 1
quick other question for this: if I'm testing against a 
pants_requirements()
from this... I guess I need to add my find-links thing to 
python-repos.repos
?
w
yep. when running using 
PANTS_SHA
with the standard 
pants
script, we do exactly that
f
ah okay that works
Copy code
PANTS_PYTHON_REPOS_REPOS=$HOME ./pants lint test --no-pytest-config-discovery pants-plugins::
sweet, figured these use cases existed internally, so #development was the place to ask
Open in Slack
PreviousNext
Powered by