-
-
Notifications
You must be signed in to change notification settings - Fork 632
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TargetDefinitionException
when using globs with resources=
in a PythonLibrary
#3506
Comments
From the code for python_target, I was under the impression that we were getting rid of resources= on python targets. Also, does anyone use the resource_targets kwarg? |
hmm, afaik |
There's a comment, but it never got documented, so I'd guess not. |
A big push in the area of deprecating resources isn't a good idea right now, because in the engine experiments, it became pretty clear that you don't actually need target types once you're consuming products by type... could just have a target with both EDIT: Opened #3560 on this topic. |
Will work on this today. |
Reviewable here: https://rbcommons.com/s/twitter/r/3979/ ... also, found #3563, as mentioned above. |
This fixes [#3506](#3506), which is caused by our conversion of the `globs/rglobs` objects without capturing them later. - Capture the `resources=globs` argument for Python targets - Open tickets to design the migration path to typed Sources Testing Done: http://jenkins.pantsbuild.org/job/pantsbuild/job/pants/branch/PR-3566/2/ Bugs closed: 3506, 3566 Reviewed at https://rbcommons.com/s/twitter/r/3979/
Merged as 04e4457 |
with a target like:
the following error is seen on a
./pants --enable-v2-engine list
:commenting out the
resources = rglobs('*.yaml', '*.zip')
eliminates the error.The text was updated successfully, but these errors were encountered: