Closed jakewilliami closed 3 years ago
Hi @jakewilliami !
Thanks for the PR. Do you really think this is necessary? The tests are passing on Windows. I have never found a single problem related to the paths.
@ronisbr,
Huh, good point. I donât know why paths separated with /
would work on a Windows machineâit seems safer to use joinpath
, but if itâs working with forward slashes, then I guess itâs fine. Up to you!
If you are using Windows, can you please see if the tests pass locally? I really do not have any computer with Windows right now.
Sorry, I also donât have a windows computer! However, I can test this on a Windows computer later today (I will use one of my flatmateâs đ). Iâll let you know what I find
Thanks! I will wait for the result.
@ronisbr, sorry for the delayâbusy week. Youâre absolutely rightâtested on a Windows machine, and the unix paths work.
I did some digging, and the reason for this is because I believe it uses abspath
or normpath
.
When include
is called (whose method is in base/client.jl
), Base._include
is called (defined in base/loading.jl
). To get the path name, it calls Base._include_dependency
(also in loading.jl
), which calls abspath
or normpath
, both of which are defined in base/path.jl
(here and here respectively), and both of which will correct the path separators.
Sorry about this! All the best, Jake.
Nice! Thanks for the info @jakewilliami!
Use
joinpath
ininclude
s for consideration for non-unix paths