[Python] Update the Python Installation Chapter

[JakobKlotz]

Update Python installation guide to version 3.14

Overview

Updated the Python installation chapter to recommend Python 3.14, which is fully compatible with all packages used throughout the course.

Key Changes

Windows Installation (Major Update)

• Switched to Python Install Manager (.msix): the new official tool for managing Python installations which will also replace the standalone installer (.exe) in the future
• Expanded Step 2 with more detailed instructions:
  • Added guidance for optional App execution aliases configuration
  • Included prompts users will encounter during installation

macOS Installation (Minor Updates)

• Updated download instructions to reflect Python 3.14.x
• Enhanced formatting and consistency with Windows section
• Clarified the importance of the Install Certificates.command step

[JakobKlotz]

@christinastampfer @verenitas @manuf3006 I'm interested in your thoughts on the chapter, so I've added you all as reviewers.

[verenitas]

Wow, thank you, I really like how the new installation chapter turned out. I think switching to the new Install Manager is a very good and forward-looking decision.

I just have two small points:

Windows – Step 3 (Verify Installation)
In the written explanation, I would suggest keeping the instruction to search for cmd rather than terminal, since Windows Terminal is not necessarily installed on older Windows versions. Using cmd feels slightly more robust and universally applicable.

MCI computers / PATH variables
I’m a bit unsure what we want to do about students using MCI computers. With the updated instructions, we no longer include guidance on manually setting PATH variables. It probably won’t affect more than one or two students, but we should still decide how to handle it.
One option would be to provide the original written instructions separately on Sakai for those specific cases. Personally, I would prefer not to reintroduce the legacy PATH explanation into Code Campus, since it adds complexity for the majority of students.
What do you think?

[verenitas]

Also, I really like the video instructions 🤩

[verenitas]

As mentioned I would go with cmd here.

[JakobKlotz]

How about an additional info box?

    ???+ info

        If you are using Windows 10 (installed on our MCI computers), 
        search for **Command Prompt** (`cmd`) instead of Terminal. All 
        consecutive steps stay the same.

[manuf3006]

How about an additional info box?

    ???+ info

        If you are using Windows 10 (installed on our MCI computers), 
        search for **Command Prompt** (`cmd`) instead of Terminal. All 
        consecutive steps stay the same.

I dont know, if we want to mention MCI since we are trying to separate it from the course for a broader audience?

[verenitas]

That is perfect :)

[JakobKlotz]

Great, made the change and removed the mention of MCI 😄

[JakobKlotz]

Wow, thank you, I really like how the new installation chapter turned out. I think switching to the new Install Manager is a very good and forward-looking decision.

I just have two small points:

Windows – Step 3 (Verify Installation) In the written explanation, I would suggest keeping the instruction to search for cmd rather than terminal, since Windows Terminal is not necessarily installed on older Windows versions. Using cmd feels slightly more robust and universally applicable.

MCI computers / PATH variables I’m a bit unsure what we want to do about students using MCI computers. With the updated instructions, we no longer include guidance on manually setting PATH variables. It probably won’t affect more than one or two students, but we should still decide how to handle it. One option would be to provide the original written instructions separately on Sakai for those specific cases. Personally, I would prefer not to reintroduce the legacy PATH explanation into Code Campus, since it adds complexity for the majority of students. What do you think?

Good points you brought up:

Windows – Step 3 (Verify Installation): You're right, for Windows 10 we need to mention the command prompt. Though I hope students will only have to work with an older version of Windows when using our in-house computers. 🙈 Since Win 10 reached its end of life last year, I'd suggest to keep the terminal as the "default option" for the rest of the course. But I'd definitely use an info box for Win 10 users.

MCI computers / PATH variables: Honestly, I haven't thought about the MCI computers too much. But in this case, I wouldn't bother with the Python 3.11 installation and instead encourage students to also follow the instructions to set up Python 3.14 which should have a couple of advantages:

• Students are familiar with the installation process
• Everyone works with the same Python version

In the end, installing Python should just take and additional one or two minutes than setting PATH variables.

I could:

• try the installation on an MCI computer and check if everything works
• and then add another info box to clarify how students should proceed with in-house computers

Great that you reviewed it, there are a couple of things I haven't considered 😄

[manuf3006]

How about an additional info box?

    ???+ info

        If you are using Windows 10 (installed on our MCI computers), 
        search for **Command Prompt** (`cmd`) instead of Terminal. All 
        consecutive steps stay the same.

I dont know, if we want to mention MCI since we are trying to separate it from the course for a broader audience?

[manuf3006]

Maybe we want to add the target=_blank option to open it in a new tab?

Something like: python.org :octicons-link-external-16:{target="_blank"}

[JakobKlotz]

Sure, made the appropriate changes for the links.

[verenitas]

Wow, thank you, I really like how the new installation chapter turned out. I think switching to the new Install Manager is a very good and forward-looking decision.
I just have two small points:
Windows – Step 3 (Verify Installation) In the written explanation, I would suggest keeping the instruction to search for cmd rather than terminal, since Windows Terminal is not necessarily installed on older Windows versions. Using cmd feels slightly more robust and universally applicable.
MCI computers / PATH variables I’m a bit unsure what we want to do about students using MCI computers. With the updated instructions, we no longer include guidance on manually setting PATH variables. It probably won’t affect more than one or two students, but we should still decide how to handle it. One option would be to provide the original written instructions separately on Sakai for those specific cases. Personally, I would prefer not to reintroduce the legacy PATH explanation into Code Campus, since it adds complexity for the majority of students. What do you think?

Good points you brought up:

Windows – Step 3 (Verify Installation): You're right, for Windows 10 we need to mention the command prompt. Though I hope students will only have to work with an older version of Windows when using our in-house computers. 🙈 Since Win 10 reached its end of life last year, I'd suggest to keep the terminal as the "default option" for the rest of the course. But I'd definitely use an info box for Win 10 users.

MCI computers / PATH variables: Honestly, I haven't thought about the MCI computers too much. But in this case, I wouldn't bother with the Python 3.11 installation and instead encourage students to also follow the instructions to set up Python 3.14 which should have a couple of advantages:

• Students are familiar with the installation process
• Everyone works with the same Python version

In the end, installing Python should just take and additional one or two minutes than setting PATH variables.

I could:

• try the installation on an MCI computer and check if everything works
• and then add another info box to clarify how students should proceed with in-house computers

Great that you reviewed it, there are a couple of things I haven't considered 😄

Haha, I feel you, and I totally agree. I don’t think we need to worry too much about the MCI computers, since I’m quite confident that many students will bring and use their own laptops. I’d even suggest that we only assist students individually if they choose to work on the MCI machines.
I’m also a bit unsure about how stable everything would be if we install Python 3.14 in addition to 3.12 on those computers. Do you have any experience with running multiple Python versions in parallel on the same system?

[JakobKlotz]

Wow, thank you, I really like how the new installation chapter turned out. I think switching to the new Install Manager is a very good and forward-looking decision.
I just have two small points:
Windows – Step 3 (Verify Installation) In the written explanation, I would suggest keeping the instruction to search for cmd rather than terminal, since Windows Terminal is not necessarily installed on older Windows versions. Using cmd feels slightly more robust and universally applicable.
MCI computers / PATH variables I’m a bit unsure what we want to do about students using MCI computers. With the updated instructions, we no longer include guidance on manually setting PATH variables. It probably won’t affect more than one or two students, but we should still decide how to handle it. One option would be to provide the original written instructions separately on Sakai for those specific cases. Personally, I would prefer not to reintroduce the legacy PATH explanation into Code Campus, since it adds complexity for the majority of students. What do you think?

Good points you brought up:
Windows – Step 3 (Verify Installation): You're right, for Windows 10 we need to mention the command prompt. Though I hope students will only have to work with an older version of Windows when using our in-house computers. 🙈 Since Win 10 reached its end of life last year, I'd suggest to keep the terminal as the "default option" for the rest of the course. But I'd definitely use an info box for Win 10 users.
MCI computers / PATH variables: Honestly, I haven't thought about the MCI computers too much. But in this case, I wouldn't bother with the Python 3.11 installation and instead encourage students to also follow the instructions to set up Python 3.14 which should have a couple of advantages:

• Students are familiar with the installation process
• Everyone works with the same Python version

In the end, installing Python should just take and additional one or two minutes than setting PATH variables.
I could:

• try the installation on an MCI computer and check if everything works
• and then add another info box to clarify how students should proceed with in-house computers

Great that you reviewed it, there are a couple of things I haven't considered 😄

Haha, I feel you, and I totally agree. I don’t think we need to worry too much about the MCI computers, since I’m quite confident that many students will bring and use their own laptops. I’d even suggest that we only assist students individually if they choose to work on the MCI machines. I’m also a bit unsure about how stable everything would be if we install Python 3.14 in addition to 3.12 on those computers. Do you have any experience with running multiple Python versions in parallel on the same system?

That makes sense, what I'm hoping for is that the installer sets the latest version as default on the machine.
Else we we'd have to set Python 3.14 as default. With the new installer we could try:

$Env:PYTHON_MANAGER_DEFAULT="3.14"

But I'll check it in advance. Anyway, as you said, we can simply assist them individually. 😄

[JakobKlotz]

@verenitas @christinastampfer @manuf3006
Just tested the Python installation on an MCI computer and it should work fine.

Basically, we have to download the install manager and then use all default options. That should also set the latest Python version as the default.

[verenitas]

@verenitas @christinastampfer @manuf3006 Just tested the Python installation on an MCI computer and it should work fine.

Basically, we have to download the install manager and then use all default options. That should also set the latest Python version as the default.

Awesome, thank you ✨!!