-
Notifications
You must be signed in to change notification settings - Fork 750
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
The Next Release (pycodestyle 2.6.x) #911
Comments
I believe #867 should be resolved before making this release so we have proper python3.8 support |
FWIW, I started running |
Running on master (Python 3.8 codebase) for the last 2 months. Everything looks good. Waiting for PyPI release :) |
I've published a changelog for 2.6.0a1 here: #922 -- I don't have permission to release to pypi so one of the project managers will have to do that if everything looks good 👍 |
Published to https://pypi.org/project/pycodestyle/2.6.0a1/ sorry for the delay, @ me next time, since I have too much email filtering right now... :) |
no problem! thanks @IanLee1521! |
Since I only use this project as a subdependency of flake8, and flake8 has a <2.6.0 requirement - can I install the alpha version to help test it before a stable release somehow? I'm getting a version conflict if I just try to add a 2.6.0a1 dependency on pycodestyle in addition to my flake8 dependency. |
@stianjensen you're too quick -- just wait a bit I'm working on it :P https://gitlab.com/pycqa/flake8/-/merge_requests/418 |
@stianjensen - If you manually upgrade pycodestyle after installing flake8, pip will complain, but will install (though I can't vouch for it working beyond that):
|
No one can, that's why there are those dependency bound 😄 |
Tested on my django+mypy codebase (also around 80kloc). The new walrus operator is working as expected, and the only new warning I get is |
things have been quiet :) -- beyond #927 I think we're ready to remove the |
Should we sneak #931 in there too? |
yes I think so 👍 |
Done on both accounts |
sweet, I'll put together a changelog and then we can get this out! |
#933 for that |
oops, hasn't been released yet -- will resolve this when that happens (just merged the changelog for it!) |
Working on it now... :) |
And we are live! https://pypi.org/project/pycodestyle/2.6.0/ Huge shout out to @asottile for all the work on getting this done! All of the credit goes to them! |
👋 I'm planning to organize the next release of pycodestyle
I'll be pinning this issue and collecting feedback on things that should end up in this release
Due to the number of contributions that have gone into
pycodestyle
since the last release, I'm planning to do this as2.6.0a1
first (an alpha pre-release) -- this should hopefully expand the number of people trying the release (though I suspect not all that many will use the alpha still)How you can help:
pip install --force-reinstall git+https://github.com/pypa/pycodestyle
The text was updated successfully, but these errors were encountered: