2.2.0 #524
2.2.0 #524
Conversation
|
#523 is needed for CI to be green |
|
Hi @asottile ! Thanks for the great work. May I ask that will the latest commit "Fix pyflakes for removal of ast.Param" also be included in the 2.2.0a1 version? It seems that |
|
@C1ariS it is, however it doesn't matter as they are reverting in cpython: python/cpython#19056 |
|
Okay, thank you so much! |
|
Let's just make it 2.2.0? There's always 2.2.1, if something needs fixing. |
|
sure, I figure an alpha release is probably better so there can be some soft vetting, but it's your project so I'm happy do what you want, I'll go drop the "a1" |
|
Heh, I probably should have tweaked the release date in news.rst, too :( The most tedious part of making these releases is updating that silly file. Would too many people be upset if we just deleted it? There's always the git history. Or perhaps there's some way to automatically generate it? Or we just require PRs to update it? Open to ideas. |
|
oops, I knew I forgot something 🤦 the changelog is a bit tedious but I'm happy to fill it out when making releases 🤷 I think it's still somewhat valuable for large/popular projects such as pyflakes as traversing the git history on github is not always the easiest. having contributors edit it often ends up in merge conflict messes unless you do something like towncrier to manage changelog fragments (and then merge them all together at the end) -- but then you end up being in the business of policing those which can be quite some work -- I guess worst case we continue what we're doing and I'm fine maintaining that |
No description provided.