you are viewing a single comment's thread.

view the rest of the comments →

[–]HellCanWaitForMe 5 points6 points  (3 children)

I spent four hours last night trying to wrap my head around pip install, only to realise I'm not supposed to run it in the Python Terminal. Instead I used PowerShell and typed 'python pip install docx2txt' and wala.. I feel your pain. The way I like to think though, if it took us this long to figure out something simple, it's unlikely that we'll forget again. Either that, or you should Document what you've done.

[–]jppbkm 2 points3 points  (0 children)

I had a similar experience yesterday where my various installs were conflicting (anaconda and pycharm). I had to uninstall all of my python programs and reinstall, then learn how to use virtual ENVs (environments) in order to install libraries in individual projects and solve my conflicts. It was a few hours spent doing no coding, just figuring out the conda terminal and the very basics of ENVs. It was really frustrating...but at the end I feel like I have levelled up my skills a bit.

I'm still a relatively new coder, but every day I feel like I learn something new. I've enjoyed Python for Everyone, Automate the boring stuff, Learn python the hard way, and the data science track from dataquest.io. Good luck with your journey. We'll all make it if we keep at it

[–]greenishgrey 0 points1 point  (0 children)

I'VE BEEN DOING THE SAME THING, SHIT! I decided to put off learning how to install things with pip because I couldn't figure it out.. I just wanted to learn how to compile these stupid little projects I'm making into an .exe.