You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What I want the code to look like after pressing enter:
# Add 4 spaces (an extra level of indentation) to distinguish arguments from the rest.deflong_function_name(
var_one, var_two, var_three,
var_four):
print(var_one)
What the code actually looks like after pressing enter:
@parkershamblin where are your cursors in the above? Please be very explicit in how you created such a situation -- my issue template includes a "What the code looks like before pressing enter" section which you seem to have deleted, but is crucial for reproducibility. When I try to replicate this, I end up with the following steps:
@kbrose I apologize for not including a "What the code looks like before pressing enter" section in my post. I believe that I accidentally deleted it while writing the post, but yes, the steps you listed are exact the steps I took.
Personally, I think the format of the code being generated is fine and easily readable. As you mentioned, it's clear which code belongs to the function definition vs. the function code.
If it is going a hassle to try and change it to match PEP8, I would not worry about it. I created this issue with the intent of it acting as a friendly notification to the contributors that this small difference existed, and not as an actual "issue" that must be fixed.
See PEP8 Indentation for example.
Minimal code example:
What I want the code to look like after pressing
enter
:What the code actually looks like after pressing
enter
:The text was updated successfully, but these errors were encountered: