Pycodestyle: Version on pypi is a year old.

[euresti]

Happy birthday to pycodestyle 2.3.1!
Can a new version be released? There are lots of bug-fixes that I'm sure the world would appreciate!

[FichteFoll]

And new features like W504.

[IanLee1521]

Yeesh... Yes, I should get on that...

[JakobGM]

Gentle reminder, @IanLee1521 :)

Waiting #710 to be implemented :tada:

[hoylemd]

@JakobGM #710 looks like it's done to me. Did you mean to link to a different issue or am I missing something?

[sigmavirus24]

I've had various people volunteer to write changelogs to make it easier to cut a release. If anyone wants to through together something for the release I could potentially do this tonight or tomorrow night.

[hugovk]

Here's a list of what's been merged since the last release: https://github.com/PyCQA/pycodestyle/compare/2.3.1...master

[sigmavirus24]

@hugovk that is neither accurate nor what I asked for

[hugovk]

I updated the link, it's to help someone write a changelog.

[IanLee1521]

Yes, a pull request with a change log would greatly speed my ability to handle this one.

[JakobGM]

@hoylemd Yes, #710 is indeed fixed! But am I incorrect in that the fix is not part of the published PyPI version?

Regarding writing the changelog, I might be able to help out, if it consists of nothing else than reading through a range of commits and summarizing them in a single file. I'm not familiar with the code base though. Perhaps as a WIP pull-request?

EDIT:
@sigmavirus24 If the commit range is incorrect, can you provide the correct range?

Thanks!

[IanLee1521]

Thanks @JakobGM that would be great. You are correct, it is not yet been released to PyPI.

For the changelog, you can use what @hugovk left as a list of the diff (https://github.com/PyCQA/pycodestyle/compare/2.3.1...master) as a reference, but you'll probably need to compare that against the actual merged pull requests to combine the two.

The changelog is at https://github.com/PyCQA/pycodestyle/blob/master/CHANGES.txt, and you can see there is already a bit of work to fill in the changes, but we need to complete it.

Thank you!

[JakobGM]

That seems managable, @IanLee1521!

[...] but you'll probably need to compare that against the actual merged pull requests to combine the two.

Seems to me that all the merged pull requests are merged into master, so shouldn't all the merged pull requests already be part of the provided commit range? Is there something I misunderstand here?

[IanLee1521]

Just that you might need to look at the PRs / Issues to find the references for the changelog, e.g. "this change was made because of #XYZ"

[JakobGM]

Ok, then I understand :stuck_out_tongue:

[JakobGM]

Okay, I have now read the git log and included any relevant items in CHANGES.txt as a part of #740.

I will update the pull request if you think something is missing, or if I have included anything irrelevant :smile:

[sigmavirus24]

2.4.0 i son PyPI! :tada: Thank you @JakobGM for helping get this out the door. :+1:

[JakobGM]

Great, thank you, I'm glad I could help!