V2 #12
Draft
V2 #12
Conversation
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
My first full pass is done.
(Then I run out of time at the end of HANDSON1.md. Will resume from HANDSON2.md)
…talled to under the `~/.local/bin` But RY doesn't think it's commond to add it to PATH
Update README.md
Had a markdown preview artifact removed so it is readable.
Update README.md
Follow up v2
1. observation option should be set the record session command 2. set target option to subset
Followup v2 part2
This is just not true. Participants will not interact with different test categories.
Fixed the link
Wrong option name
Correction
Here's what Gemini had to say on this: Q: Please discuss the portability/availability of `python` command vs `python3` command. On Mac, the former doesn't exist. Is the latter more portable? The short answer is that, yes, the python3 command is more portable and reliable today than the python command. Using python3 explicitly ensures that you are invoking the Python 3 interpreter, which has been the standard for years, while the python command can be ambiguous and lead to unexpected behavior. The Ambiguity of python The main issue with the python command stems from the long transition from Python 2 to Python 3. For a long time, many operating systems, including older versions of macOS and various Linux distributions, used Python 2 for their internal system scripts. To avoid breaking these scripts when Python 3 was installed, a new command, python3, was created. This meant that on many systems, python would point to Python 2, and python3 would point to Python 3. With Python 2 reaching its official end-of-life in 2020, most modern operating systems have fully transitioned to Python 3. However, the legacy of this transition still exists. On some systems, the python command might still not be defined by default or might be configured to point to a specific version of Python 3. This inconsistency makes relying on the python command a portability risk. On macOS, for example, the python command doesn't exist by default in recent versions, precisely to avoid this ambiguity and encourage developers to use the explicit python3 command. The Portability of python3 The python3 command is now the de facto standard for invoking Python 3. By using it, you are explicitly telling the operating system to run a Python 3 interpreter, regardless of what the python command is (or isn't) configured to do. This makes your scripts and commands more predictable and portable across different environments, from macOS and Windows to various Linux distributions. For this reason, best practice is to always use python3 in your scripts and command-line interactions. This ensures that your code will run on the correct interpreter and won't suddenly break if you move to a different machine with a different default configuration.
Unless your fluency is at a certain level, these options come across mysterious.
Confusing three extra lines that do not match with what's actually in `pre-merge.yml`
SSH URL needed to push code
Added screenshots to guide students to the right button.
[AIENG-218] Fix v2handson3
[chore] add `launchable compare subsets` command section
... in order to upload images.
Let the SE create a PR for the participant.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.