Is there a way to deal with colons in file names? ...
# general
f
Is there a way to deal with colons in file names? It seems to throw some commands through a loop (in this case the file is named `path/to/wip:_new_rules.yaml`:
Copy code
❯ ./pants --changed-since=HEAD --changed-dependees=transitive list
17:27:29.91 [ERROR] 1 Exception encountered:

  ResolveError: The file or directory 'path/to/wip' does not exist on disk in the workspace, so the address 'path/to/wip:_new_rules.yaml' cannot be resolved.
h
Oh boy
Pants interprets that as "the target named
_new_rules.yaml
in `path/to/wip/BUILD`"
Offhand I can't think of a way to bypass that
f
Yeah, I'm kinda okay disallowing
:
in files, although it's possible here that the underlying tool wants that filename, in which case we might have to do that translation in pants later
h
fwiw, macos (and maybe linux?) don’t allow filenames with colons, for much the same reason windows doesn’t allow filenames with slashes
f
it's fully legal in linux, just not usually used
👍 1