Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From #6578 (comment) I gather that we should not support absolute paths in
_makefile, and I agree at first, I don't see a good use case to allow that and might open up for unwanted writes to system wide files.I see two options here:
_makefileand raise an error, or warning if we want to be conservative.@RonnyPfannschmidt can correct me if I'm misinterpreting him.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nicoddemus
This is only a test for the actual behavior, yes.
See #6603 for a saner helper that also allows for this.
How should it be documented? Since it is internal that would be with the test's docstring then? Note that the commit has a reference already.
Yeah, somebody could do it on top of this, but if nobody wants to do it now I think it is better to test the given behavior.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Always failing is preferable to surprises, however this needs to be done starting with a warning
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nicoddemus how to proceed here then? I'd say to just merge it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Definitely, sorry I wasn't clear.
That's good, but I prefer to also include it into the docstring: we often move code around so it is harder to find stuff with blame.
But OK, let's merge it now and decide on the warning/error/etc on the other PR (I don't think we will lose sight of this and this comes back to bite us later).