-
-
Notifications
You must be signed in to change notification settings - Fork 387
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
Quotes consistency #2326
Quotes consistency #2326
Conversation
Not finished, but the idea is to go through all files. I clarified quoting of URIs: basically a quote can theoretically appear in those (single quote is a reserved character for sub delimitation, a bit like |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These look good. The convention also makes sense. Easy to understand, and it makes the code easier to read.
2116dd7
to
6cdd8f9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This all looks good to me. Now I just need to try to remember to follow it when submitting changes. ;-)
- Add a note about URI & quoting - Add note about XML - Clarify scope and usage if in doubt Clarification
In fact, Python codec is `utf_8` but it has aliases, `utf8' (declared as alias) or `utf-8` (because `_` or `-` do not make difference) are working, but we mainly use `utf-8` among the code. See https://docs.python.org/3/library/codecs.html#standard-encodings
0a630c5
to
511f3be
Compare
Merged, but I squashed all the commits that updated the quotes only |
In general, I wouldn't squash such big set of changes, it disables the possibility to bisect. I intentionally split changes in small sets. |
In this case it was really a huge amount of separate commits with essentially all the same commit message and with many but trivial changes that causes parser error if done wrong. There was not much point in keeping those. I totally agree in doing changes in multiple commits and I'm not much a friend of squashing all PR as some projects practice it, as any PR that is a bit more complex easily consists of multiple separate steps of implementation. But if each commit is just an extension or fix of the previous one we can keep them combined. |
Summary
Problem
Solution
Action