I don't see it anywhere in the doc, but it looks l...
# general
p
I don't see it anywhere in the doc, but it looks like pants doesn't work well with directories that contain ":" in the name. Is there a workaround for that? I have test resources that contain directory named "vessellatestposition" with a bunch of parquet files, that I want to add as resources to my test. I can define a resource including that dir, but pants list doesn't show it, and running tests crashes with:
Copy code
AddressParseException: Failed to parse address spec `(...) /vessel:latest:position:(id)/ (...)`: error at 1:137: expected EOF
e
Ah, yeah - you've stepped on a land mine there.
p
I thought so:)
e
Pants reserves
:
as a special address delimiter.
h
Grrrr
That is... unfortunate
A choice we made fairly arbitrarily ~13 years ago is biting you now 😞
e
I think there is no single choice that wouldn't bite someone. This would need an option I think.
h
Yeah, I mean, we did go 13 years until it blew up (that we know of)
e
I think the idea here @powerful-eye-58407 is no one in their right mind uses PATHSEP in a path.
I mean, thinking more, this is exactly why it was chosen.
p
yep, I get that, this is the data we get from the customer, and we are testing a parser as it has to split the path by ":" to extract some ids, not the best choice here... 😄
OK, if this is expected, I will work around this by creating the path in the test on the fly. I just wanted to confirm that's a known issue
thanks for claryfing
f
Can you just adjust the data received from the customer as part of any ETL process to not have a colon in the directory name?
s/:/__/
i.e., maybe have a helper script to unpack and adjust the customer data when committing it to the repo?
p
it's not that easy, but I agree that would be the simplest solution 🙂