-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
1795 rename async module #1796
1795 rename async module #1796
Conversation
renaming it |
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.
see comment above
changes requested done ;) |
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.
Thanks! looks good for me, just wondering if the change should be major. Thoughts ? cc @berkerpeksag @tilgovi
@tilgovi @berkerpeksag thoughts? I am thinking we should create a pre-20 branch that include that change and the removal of python 2. Thoughts? |
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.
Thanks! looks good for me, just wondering if the change should be major.
I don't think this is a major change since the chance of having worker subclasses is low and we are not the only project to make this change.
I'd vote +1 for adding this to the next 19.x release.
requirements_test.txt
Outdated
@@ -1,3 +1,3 @@ | |||
coverage>=4.0,<4.4 # TODO: https://github.com/benoitc/gunicorn/issues/1548 | |||
pytest==3.0.5 | |||
pytest-cov==2.4.0 | |||
pytest |
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.
Please leave unrelated changes to another PR.
docs/source/news.rst
Outdated
19.9.0 / 2018/05/26 | ||
=================== | ||
|
||
- the internal module `gunicorn.workers.async` was renamed to `gunicorn.workers.base_async` |
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.
the -> The
docs/source/news.rst
Outdated
19.9.0 / 2018/05/26 | ||
=================== | ||
|
||
- the internal module `gunicorn.workers.async` was renamed to `gunicorn.workers.base_async` |
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.
Style nit: Please use double backtics.
docs/source/news.rst
Outdated
@@ -2,6 +2,14 @@ | |||
Changelog | |||
========= | |||
|
|||
19.9.0 / 2018/05/26 |
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.
I would change 2018/05/26 with "not released".
.gitignore
Outdated
@@ -15,3 +15,5 @@ examples/frameworks/pylonstest/pylonstest.egg-info/ | |||
MANIFEST | |||
nohup.out | |||
setuptools-* | |||
.cache |
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.
.cache was renamed to .pytest_cache and we already added it to .gitignore.
.gitignore
Outdated
@@ -15,3 +15,5 @@ examples/frameworks/pylonstest/pylonstest.egg-info/ | |||
MANIFEST | |||
nohup.out | |||
setuptools-* | |||
.cache | |||
.eggs |
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 looks like a good candidate for having a global .gitignore file.
@berkerpeksag done |
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.
Looks great, thank you!
gunicorn/workers/__init__.py
Outdated
@@ -17,6 +17,6 @@ | |||
} | |||
|
|||
|
|||
if sys.version_info >= (3, 3): | |||
if sys.version_info >= (3, 4): | |||
# gaiohttp worker can be used with Python 3.3+ only. |
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.
3.3+
-> 3.4+
?
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.
I did this change to match this: https://github.com/benoitc/gunicorn/blob/master/gunicorn/workers/gaiohttp.py#L10
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.
I mean the comment # gaiohttp worker can be used with Python 3.3+ only.
should be updated to # gaiohttp worker can be used with Python 3.4+ only.
to match your change.
Merged! Thank you all for the PR and for the reviews. I'll try to make a release by next weekend so that hopefully Gunicorn is ready when 3.7 is released. |
Can we please use the "squash and merge" option when there are intermediate commits in a PR? Commits like 07dc716 and 66ec021 shouldn't be merged into the master branch. We don't have feature branches and develop features the way the Linux kernel team does (long lived branches, no intermediate commits etc.), so I think we can even disable the "create a merge commit" option. |
I agree that we should avoid having fixup commits like that. They're not useful. I don't "squash and merge" because sometimes the commits matter. I'll try to be more careful, though, and review the commits. Maybe we can agree on a review process. When you give a ✔️ a usually trust it, but maybe we should ask for rebase / squash by the authors before we approve. Small risk of making people frustrated, but lower risk of accidentally squashing useful history or merging useless history. |
@berkerpeksag well we should probably have long lived branch. So we can break from now the code and work on next major release and start new iterations from it :) For example, I wouldn't have merged it before bumping our own version. That change will break anyone using a custom worker based on the async base. So that's a good call for such branches :) |
Closes #1795