-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Some errors in test.py for training on Windows #90
Comments
Thanks for the feedback! I fixed your #2, yes good catch. The dictionary was named the same as the string, poor coding on my part. #1 will take a bit of effort to resolve, as there are various areas around the code that stitch together path names under the linux assumption. But you are not the first one to mention this. I will leave the comment open until I resolve this, presumably through the more liberal use of, About your last comment I had not heard this from anyone else yet, so I will leave as is for now. Thanks again. |
we can use pathlib of standard library instead of os in python3(>=3.4). |
@Ttayu thanks for the article, I was not aware of the new pathlib functionality. This seems like a good solution, I'll see what I can do to integrate it. |
@rtrahms I updated Lines 25 to 26 in 7d58788
Are there any other incompatibilities in |
Hi all -
Nice job on implementing YoloV3 in PyTorch/CUDA! I am using it in a Windows Python 3.7 environment, and have successfully trained and tested a custom network using this framework!
I did find some bugs in the master though.
A somewhat unrelated bug is the use of the name test.py. I was unable to debug this with spyder until I changed the name of this module to a more unique type (I used yolo_test.py, and debugging worked). I am wondering if there is a reserved word conflict with the name test.
Thanks!
Rob
The text was updated successfully, but these errors were encountered: