Use if __name__ == '__main__': in server examples docs#3788
Use if __name__ == '__main__': in server examples docs#3788asvetlov merged 1 commit intoaio-libs:masterfrom samuelcolvin:update-examples
if __name__ == '__main__': in server examples docs#3788Conversation
Codecov Report
@@ Coverage Diff @@
## master #3788 +/- ##
=======================================
Coverage 97.94% 97.94%
=======================================
Files 43 43
Lines 8576 8576
Branches 1374 1374
=======================================
Hits 8400 8400
Misses 74 74
Partials 102 102Continue to review full report at Codecov.
|
if __name__ == '__main__': in server examples docs
|
Side note: The version is brand new: |
(cherry picked from commit 506c244) Co-authored-by: Samuel Colvin <[email protected]>
|
what's wrong with squash merge in github? |
|
I mean backporting to 3.5 branch |
|
Currently I do backporting by running |
|
Sorry about the issue with cherry-picker. It is also a problem in miss-islington, so we reverted back to using earlier cherry-picker 1.2.x.
Yes, I will be writing this bot sometime this week or next. |
|
About cherry-picker issue, I had described it to @webknjaz. He said he will think about it after returning from PyCon 🙂 |
|
@asvetlov, clean the state in Git and use the latest version of cherry-picker, if the one you use creates that state this means that you use an outdated version which has this bug. |
|
Yes, I'll take a look at addressing this issue. |
|
I use cherry_picker 1.3.1 but it keeps a record in git config after cherry-picking finishing |
|
@asvetlov did you clean up the local git config before using 1.3.1? Can you confirm that it appears in |
|
I understand your astonishment but yes. Try yourself |
|
Wow. I have to check what's actually published on PyPI then. |
What do these changes do?
Make it slightly easier to use the default examples with aiohttp-devtools etc.
Are there changes in behavior for the user?
no
Related issue number
fix #3775
Checklist
CONTRIBUTORS.txtCHANGESfolder<issue_id>.<type>for example (588.bugfix)issue_idchange it to the pr id after creating the pr.feature: Signifying a new feature..bugfix: Signifying a bug fix..doc: Signifying a documentation improvement..removal: Signifying a deprecation or removal of public API..misc: A ticket has been closed, but it is not of interest to users.