Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assignment & Concatenation - potential clarifications #605

Open
Cook4986 opened this issue Jul 28, 2022 · 1 comment
Open

Assignment & Concatenation - potential clarifications #605

Cook4986 opened this issue Jul 28, 2022 · 1 comment

Comments

@Cook4986
Copy link

Regarding the lesson Plotting and Programming in Python:

Assignment Ordering

As a novice coder, it’s tempting to see the = character in a variable assignment statement (e.g. num = 6) as representing arithmetical identity. So, interchangeability characterizes the = notation that many novice programmers will have encountered before. This can lead to problems associated with erroneously switching the left/right position of the declared variable and the assigned value. The addition of a brief note reinforcing assignment ordering rigidity could be valuable.

Printing vs. Concatenating

Within the same lesson, there are multi-argument print calls (“Use print to display values” sub-section) that combine variables via , notation. In the subsequent lesson Data Types and Type Conversion, print function concatenation is demonstrated using the + notation. The addition of a note differentiating simple printing vs. concatenation might be useful for novice coders (like me).

Happy to pull and update, if these additional notes/clarifications make sense. Thanks!

@martinosorb
Copy link
Contributor

Hi @Cook4986 , thank you for the comment and sorry for the much delayed reply, I'm going through some old issues. I don't disagree with either of your comments, do you have ideas on how to fix those?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants