Documenting Working Codes - Windows Powershell Trash?

in #python4 years ago (edited)

Too many cooks stirring the pot is definitely a big issue when it comes to learning programming

After going through Bucky's beginner friendly introduction to Django, I was very confident that his teaching style alone will get me what I want

Then, on slack, a Python Tutor dropped a Django PDF also for beginners, and right from the beginning it looked very palatable, then somewhere along the line, it dropped this line:

On Windows machines there are actually two built-in command shells: the Command shell and PowerShell. You should use PowerShell, which is the more powerful of the two.

This is what frustrated me throughout yesterday using the Powershell

It turns no matter how well you follow what you are being taught, it wont give you the output of your desire, even if you are 'correct'

We are now establishing this very fact in front of us:

For whatever reason that might be discovered someday soon, Windows Powershell is currently a poor alternative to Windows Command Prompt.

Tried it this morning.

Same code, different prompts

One gave me what I wanted and the other one flat out didn't

Easy to see the one I'm sticking with.

Screenshot (279).pngWindows Powershell

Screenshot (278).pngWindows Command Prompt