rough-vase-83553
10/19/2022, 2:43 AMpython_requirement
and python_requirements
is, in case there's some misuse going on that's messing things up.rough-vase-83553
10/19/2022, 2:43 AMpython_requirements
for each requirements file. I'm setting the resolve of all these to the same resolve, and I've done work to ensure the dependency specifiers are all compatible.rough-vase-83553
10/19/2022, 2:44 AM//project/n:reqs
into the dependencies
of every Python target in //project/n/**
via __defaults__
. I still get warnings and apparently this bloats all the Pex files, but things usually run successfully.
2. I constantly get warnings of the form "The target project/whatever/file.py imports six.iteritems
, but Pants cannot safely infer a dependency because more than one target owns this module, so it is ambiguous which to use: ['project/1:reqs#six', 'project/1:reqs#types-six', 'project/1:reqs1#six', 'project1:reqs1#types-six', 'project2:reqs#six', 'project_group:reqs#six', 'project_group:reqs#types-six']". I don't understand how to "disambiguate" because (1) I'm not even sure how requirements are "bound" to individual Python targets beyond resolve
and (2) I'm already manually trying to disambiguate by explicitly adding project/1:reqs
to dependencies
everywhere. It seems like Pants is upset that I have multiple python_requirements
bound to the same resolve
, but I'm not sure how else you'd expect python_requirements
to work.
3. I often get warnings that core modules like pyyaml can't be resolved. AFAIK these are false positives but not sure why this is happening.rough-vase-83553
10/19/2022, 2:49 AMhappy-kitchen-89482
10/19/2022, 5:10 AMhappy-kitchen-89482
10/19/2022, 5:11 AMhigh-magician-46188
10/19/2022, 6:11 AMhappy-kitchen-89482
10/19/2022, 11:27 PM