More topics to start Python-related conversations with.#792
Conversation
wookie184
left a comment
There was a problem hiding this comment.
Just grammar and wording. There are a couple of pythons that should be Pythons I didn't comment on. Could you also fix capitalization on line 19, as PyPi, should be PyPI. Not part of this PR but probably not worth it's own one ig.
|
The syntax has changed for the yaml file, given the |
|
Oh interesting, that makes sense. (googling it, i'm not sure if a backslash is correct but i'm not 100% sure https://stackoverflow.com/questions/11301650/how-to-escape-indicator-characters-i-e-or-in-yaml, haven't use yaml personally) Also still some |
|
I wish I could help with the Python caps, but it'll be a lot of trouble to start a new fork for it |
|
Caps issue: |
brad90four
left a comment
There was a problem hiding this comment.
Is there a consistent rule for capitalized or un-capitalized "python"?
Lines 26, 31, 32, 33, 35 are un-capitalized, but the others are capitalized.
For line 36, The wording seems a bit clunky. Maybe "What Python level/skill/knowledge do you think you are at: Beginner, Intermediate or Advanced?"
(Just chiming in, wanting to get started with contributing!)
|
Wdym? They are not capitalized which is incorrect spelling, the others are capitalized because it is the correct spelling because it is a name. Unless I misunderstood you? |
I was just unsure if there was some un-written rule of when to use "python" vs "Python". For example I could say I have a python script written in Python. When it is an adjective lower case seems fine, but as a noun it seems more proper to use the capitalization. Also, saying "x is more pythonic" looks more appropriate thatn "x looks more Pythonic." |
f5ca5dc to
7b2e346
Compare
|
@NIRDERIi @Shivansh-007 @wookie184 fixed stuff up. |
|
Looks great for me! |
81ad623 to
129db3c
Compare
129db3c to
c18676e
Compare
Continuation of #763.