https://pantsbuild.org/ logo
Join Slack
Powered by
hi folks, when moving from 1.25.x to 1.26.x it see...
# general
w
hi folks, when moving from 1.25.x to 1.26.x it seems as if 
pants test
my 
[python-repos] indexes;
settings as it cant seem to find a privately published dependency i cannot find anything related to this in the release notes. Any advice?
w
1.26.0 doesn't have a stable release yet, but one of the big changes is that it uses pex 2
if options names changed, you should have seen deprecations, and i don't think they did. so it's more likely something to do with how pex 2 (which uses pip to resolve) resolves things.
which dev release of 1.26.x are you using?
w
1.26.0rc1
been talking to Eric and he asked me to upgrade to 1.27.x . So i've been taking it one version at a time
w
hm.
yea, that's wise. there are no stable releases of 1.26.x or 1.27.x yet though, so will need your help in filing bugs for the things you find.
w
yup -- trying to do a little root causingn
h
Hm, one thing we could try to do to reproduce is to invoke Pex directly on the command line and confirm it fails there so that we can isolate between this being a Pex failure vs. Pants failure. Steps to do this: 1. 
pip install pex
(I use the tool 
pipx
for this) 2. 
pex --index=my_custom_url req1==1.84 req2>20.1
w
i'll give that a shot
seems to have worked on pex 2.1.7
Untitled
didn't have boto3 but if its not installing transitive dependcies that's to be expected
h
Huh, it should be installing transitive dependencies. Pex works similar to Pip that if you say 
install thanos
, it will read in the metadata from 
thanos
to install all transitive dependencies. This might mean that `thanos`’s metadata is off But, okay, good, glad the index is working with Pex. Likely this is a Pants issue, then. I’ll dig right now.
w
here's the error dump if that's helpful
test_error.txt
i put a 
self._<http://log.info|log.info>(python_repos_subsystem.indexes)
in line 178 of 
~/.cache/pants/setup/bootstrap-Darwin-x86_64/1.27.0.dev2_py37/lib/python3.7/site-packages/pants/python/pex_build_<http://util.py|util.py>
but i don't see that output anywhere
h
Ohhh that is very helpful. It looks like you’re using the V2 implementation of test? Awesome! Did you recently turn that on or you’ve had it on for some time? (Turning it on means that you have 
pants.backend.python
in 
backend_packages2
and you have 
--v2
enabled, which became the default in 1.26.0.dev1) 
--python-repo-indexes
isn’t respected with the V2 implementation yet due to an oversight, but I’m putting up a fix today to wire it up. For now, the solution would be to remove 
pants.backend.python
from 
backend_packages2
until we come out with 1.27.0.dev3 tomorrow to fix this.
w
ok let me check on all that
i deffo know that we're using a combo of v1 and v2
yeah we're using v2 for 
black
h
We fixed it so that you can have Black enabled without 
pants.backend.python
enabled at the same time
w
😙 👌🏼 perfect
h
For exactly this reason. You might be ready to use V2 Black and Isort, but want to keep using V1 
test
, 
run
, etc
Cool. So, yes, keep the default of 
--v2
because you’ll need it for 
./pants fmt
and 
./pants lint
to know that it should run Black, but for now remove 
pants.backend.python
from your config file
w
running now
yup output looks much more familiar now 🙂
h
Awesome, glad it’s working again
Open in Slack
PreviousNext
Powered by