Replaced VSCode with Positron (and conda with pixi) - #10
Open
pdallago97 wants to merge 7 commits into
Open
Conversation
awurno
reviewed
Aug 18, 2026
| **Warning for students taking the course**: VSCode comes with advanced integration of generative AI. It is recommended to not make use of GenAI while learning to code. Struggling through how to get a script working is how you learn, and that is what this course is about. Generating the correct result will not teach you anything. | ||
| **Warning for students taking the course**: Positron comes with advanced integration of generative AI. It is recommended to not make use of GenAI while learning to code. Struggling through how to get a script working is how you learn, and that is what this course is about. Generating the correct result will not teach you anything. | ||
|
|
||
| It is recommended to turn off automatic features that copilot offers. You can do this by |
Contributor
There was a problem hiding this comment.
Also include how to turn off posit assistent
| If you press `ctrl` and click on the function in `main.py` you will open the function definition. This is very useful when navigating through a large project. | ||
|
|
||
| ### Environments in VSCode | ||
| ### Environments in Positron |
Contributor
There was a problem hiding this comment.
Instead of introducing setting the interpreter earlier, we can also just get them to run a script there in the most easy way and introduce that here.
| @@ -304,7 +318,7 @@ If `(geotest)` is visible before the active line in the terminal the environment | |||
|
|
|||
| Now, you might wonder how you will write code without being able to inspect what is going on. And don't be afraid there are ways to help you. The *debugger* and the interactive *REPL* _(Read-Evaluate-Print Loop)_ are tools developers use to make developing easier. Firstly the debugger. The debugger is a way of running code where you can set breakpoints and inspect the state of the code and all the variables and objects in memory. While at a checkpoint you can manipulate variables, print them and test small pieces of code on them to figure out how to proceed. From the checkpoint it is possible to proceed line by line, stepping into your function or imported packages to get a good understanding of what is happening and often identifying issues. Sounds good right? | |||
Contributor
There was a problem hiding this comment.
This might be rewritten a bit more, since line by line is an option in positron. the REPL is nto that relevant anymore, but maybe introducing the debugger a bit more detailed is useful.
Author
There was a problem hiding this comment.
I really dont use the debugger or REPL, so maybe its best if you take a look over this Arno and decide what is best to keep and what to explain in more detail
Author
There was a problem hiding this comment.
Note: REPL is also used the day after in the tutorial Python Programming
Co-authored-by: Arno Timmer <199092967+awurno@users.noreply.github.com>
Co-authored-by: Arno Timmer <199092967+awurno@users.noreply.github.com>
Removed Spyder. Removed link to Python 3 Cheatsheet (link not working anymore)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I have replaced the VSCode parts with Positron. The conda installations have been replaced with the pixi intsallations.
I think only two screenshots actually need replacement, the rest (all the Git part) is really the same as the previous one (even if in VSCode).
I also felt like reordering bits of code/text, as it was clearer to me.
I have added minor things such as the command ls -a in 'using pixi' to see all files (as ls only does not show all the hidden files).
Things to note:
the cow.py example gives a warning (only the first time you run it).
Disable GitHub Copilot: disabling the settings for GitHub Copilot: Enable should be enough? When looking for GitHub Copilot Chat a loooot of settings are found.
The Extensions are already installed in the VM. I changed the text to make the students note that these are installed, but no installments are done.
Positron raises an error when calling a package MyPackage, it suggests calling it my_package and solves the problem.
I removed the extensions.png image as it was the same as main.py ? no need to repeat twice?