Replies: 2 comments 3 replies
-
@bmcandr - I hope you were able to solve this, but if not, Slack is the best approach for troubleshooting questions. Discussions are currently used moreso for larger feature/design-specific questions where we want to keep a history. All the one-off questions are nailed pretty quick in Slack |
Beta Was this translation helpful? Give feedback.
1 reply
-
Hi there, @bmcandr - pardon the delay response! Thanks @sureshjoshi for the reply. This is expected behavior, but I can see why it's confusing. What would you expect Pants to do in this situation? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We are in the process of introducing
pants
to our Python monorepo, but I ran into an issue where./pants tailor
throws the following error when a file referenced in a BUILD file has been deleted or moved to a new location:Assume the following initial structure:
Then, we delete or move
file.py
to some other location.At this point BUILD still contains a reference to the deleted/moved file:
Running
./pants tailor
throws the error shown above and I can resolve this by deleting the BUILD file and regenerating it.Is there a way to force
./pants tailor
to overwrite existing BUILD files?Beta Was this translation helpful? Give feedback.
All reactions