Some of the Python instructions on setup are not very beginner friendly

I’m in the Python portion of the Data Science career path. Specifically, at this video on Virtual Environments with Pipenv. (https://www.codecademy.com/paths/data-science/tracks/dscp-python-fundamentals/modules/dscp-python-modules/videos/learn-python3-pipenv)

Now let me preface this, I have absolutely 0 coding experience. None. Wouldn’t even know where to begin writing a code, let alone actually doing it. So to jump into this video and at 12:00, be told to “open a text editor, preferably one with a terminal, where you can see files at the side”, I was immediately lost. What text editor? What terminal? What application is he even using? I had to do a lot of pausing and Googling.

On top of that, we had one lesson on how to set up Anaconda prompt and Jupyter Notebook, both I have not used since the exercises specifically telling us to use them. I still don’t really know what to do with them and just do all my practice in the Codecademy page.

I really want to understand and learn, so I have been trying to do some research myself outside Codecademy but I’m still not sure how to apply it. I’m hoping there may be some additional lessons on setup that really start from the ground up. Super basic stuff for us complete newbies out there. That would be fantastic.

I can definitely understand your confusion and frustration.

Let me say that you did the exact thing you should have done when confronted with a coding concept that you’re unfamiliar with: you Googled it. (everyone does that, and if they say they don’t, they’re fibbing :wink: )

Are you on a Mac or Windows? On a Mac the terminal is called, “Terminal”. It’s your C drive and file system. It just doesn’t have a fancy User Interface (UI) (like if you click on the “My Mac” icon on your desktop you can navigate through applications, downloads, files, etc). And, knowing some basic Unix commands helps when using the command line prompt in your terminal so you can navigate around, create files, directories, etc. (I see that he uses commands like pipenv and cd, etc. in the video).
Have you taken the command line course by any chance or ever poked around in the file system on your computer via Terminal? It might be worth looking into. If I recall correctly, it’s a short course.

I can see how the video would be confusing b/c he discusses having different versions of Python and different versions of Python libraries installed in different environments. (an aside–Python 2 is no longer supported and any company who uses it would, or, should have reconfigured their code over to Python 3 by now). And, through your research you would have read that like software is updated, Python libraries are updated from time to time (certain methods are deprecated, or, no longer used but replaced by something else).

Anyway…When you’re in the learning environment, doing lessons on the DS path, the py.script window—where you write and execute python commands–that’s exactly what you would use Jupyter Notebook for: writing and executing python commands and sharing your notebooks (code) with others. (there are code cells and markdown/text cells for notes.) You can also write and execute Python–like in the video–in a virtual environment using a text editor (there are tons of free text editors out there for Mac, Windows and Linux). In the video, I believe he’s using Visual Studio. https://www.lifewire.com/best-free-text-editors-4155819

Did you successfully download Jupyter and can you initiate it via typing in “jupyter notebook” in the terminal/command prompt window? Open a new Jupyter Notebook session and create a new file. Create some variables and print() them out:

It’s the same as if you’re typing in the script.py window in Codecademy.
You can also import any Python library—pandas, numpy, scipy, seaborn, etc. You have the option to do off-platform projects (import csv files, etc) on the DS path, I recommend doing it.

I hope I didn’t add to any confusion. If you have more questions, reach out to me. :slight_smile:

4 Likes

Thank you so much for this reply! I really appreciate all of the encouragement and tips you’ve given me and it certainly helps me feel a little less lost in this!

I’m on Windows. I think I did do the command line module, I believe it came a little earlier in the DS path. That’s also the same one where I downloaded the Anaconda prompt. I will definitely look up some basic UNIX! I also downloaded a program called Visual Studio Basic, which I heard is a pretty user-friendly text editor. I will need to poke around in it though. I wasn’t sure if this was the same as writing things in a command prompt, but it looks more closely like the ‘coding applications’ I’ve seen developers use!

I did successfully download Jupyter Notebook and seem to be able to open it no problem. Guess I’m just not as used to the interface as I’ve been using the Codecademy window, but I’ll try doing some more exercises in it to get a hang of it. Good to know that it practically operates the same way :slight_smile:

Really appreciate all of this information! I’ll keep at it until I figure it out!

2 Likes

Just wanted to jump in here and say that I share your frustrations a little. I am also completely new to programming, up until I started the codecademy course I’d basically never worked with the command line (which is why I am thankful that there’s a course for that).

I’m doing the CS career path, because I want to gain a deeper understanding of how the stuff I’m doing works, so I guess it is expected that it can be a bit much, even if the explanations are usually top notch - after all, that is what I signed up for.

Anyway, here comes the but:
Not sure how to implement this exactly, but I feel like codecademy has you install lots of things on your own computer to be able to follow along with the course. I was fine installing python (obviously lol) and jupyter notebooks, because it was used fairly consistently after that. (Though I don’t really like working in it, truth be told, I usually just write my code in the codecademy workspace and then transfer it when I’m done.)

It starts to get overwhelming when you can still barely write 10 lines of code that work and the career path starts teaching you git at a very early stage as well as has you set up pipenv etc. I am aware that this is probably realistic - you will run into something, have to figure it out, update something, that’s probably just the reality of doing anything tech-related. But I feel like the structure could be improved here to first teach you the absolute bare necessities and then start adding additional things. Figuring out this additional stuff cost me a lot of time and robbed me of momentum, and it feels like quite the commitment and also slightly scary to mess around so much in the command line when you have barely any idea what you’re doing.

I don’t want to advocate for completely scrubbing the course of these elements because I assume that codecademy never teaches you useless things, but I thought I would leave my perspective as a complete beginner here, because I am honestly very happy with how approachable the python/CS course has been thus far, with the aforementioned being my only complaint. I think I would be better able to appreciate codecademy teaching me this stuff when I’m not still struggling so much on ever other count, but feel like I’m missing out on valuable practice if I can’t access the notebook/whatever it is.

As a general rule to the forums, please don’t revive threads older than a year (I believe that’s written somewhere in the rules section). Please start a new thread that has a constructive suggestion.

Anyway…
You can skip around in whatever course or path you’re on & come back to installing things if it becomes overwhelming.

As an alternative to Jupyter, try Google Colab. It’s an app you add to your GDrive, so it’s cloud-based and accessible anywhere you have access to your google account log in. Plus, it’s based on Jupyter so it’s similar with the code and text boxes. You can write & execute python in it.

Hi, very sorry about that, I’ll make sure to remember in the future.

Thanks for the tip!

1 Like