Closed leptoid closed 2 years ago
This is most likely due to how Windows handles the subprocess
command via Python:
I'll try to reproduce this on Windows in the next couple of days and put up a patch if possible (I develop on macOS and the lib is tested on CI against Linux) so this wasn't discovered earlier. I'll keep you posted with what I find.
Interesting. That is windows for you. I will test it on my Linux box (no MacOS for this guy). :) Thanks!
I did consider this was because I was using Anaconda in Windows and not true Python.
Ah, interesting. Are you able to try with normal Python? I have tested the script on windows before when fixing another windows specific bug and didn't come across this which was why this initially took me by surprise, though I was using Python which could explain the error here.
Since i will have to install it, what version would you recommend?
The app is compatible with Python 3.7 and newer so any of those should do.
Hey... update:
Removed Anaconda (my friend always says it sucks)... installed Python 3.10 and now it works fine.
I thought there was an issue as I expected it to save data in the folder I was in at the CLI... it saved data... somewhere. Once I specified location, I was all set.
Lesson: Anaconda may be neat but sometimes it just doesn't work out.
So the problem isn't really a problem... it is just a quirk with Anaconda. Thanks for looking into this with me.
Glad you got it working! Thanks for all the info.
Getting errors while pulling labs from some ECCouncil content: What file would it be looking for? I installed via pip (today)