-
Notifications
You must be signed in to change notification settings - Fork 726
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FileNotFoundError on Windows 10 #455
Comments
Thanks for reporting this @thomasbridge74. Can you try using the |
Hi @jmcgill298 - that does appear to have done the trick.
Resolves the issue. I assume you'll merge the branch back into the master tree at some point. |
Thanks for confirming; I have submitted #456 |
charlesmonson
pushed a commit
to charlesmonson/ntc-templates
that referenced
this issue
Oct 11, 2019
…dows - Fixes networktocode#455 (networktocode#456) * Update template directory search to pseudo-work with Windows
thomasblass
pushed a commit
to thomasblass/ntc-templates
that referenced
this issue
Oct 25, 2020
…dows - Fixes networktocode#455 (networktocode#456) * Update template directory search to pseudo-work with Windows
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ISSUE TYPE
TEMPLATE USING
Error does not appear to be template specific (unless the index file counts)
SAMPLE COMMAND OUTPUT
SUMMARY
It would appear that the templates files are not copied when installing in Windows from a local copy of the repository.
STEPS TO REPRODUCE
On a Windows 10 desktop with git bash
Then in a python console (having set up the variable topology):_
EXPECTED RESULTS
I expected it to find the find the template from the index and proceed.
ACTUAL RESULTS
Comments
I investigated the contents of my user site-packages folder and there were no templates installed. I'm not an expert with python packaging, but I suspect the issue might be that the templates folder is symlinked which would work on Macs + Linux but is probably causing Windows to not copy the template files into the relevant folder.
The text was updated successfully, but these errors were encountered: