I fully agree with @steve.dower that the PEPs category is not the best place for that topic, but the others also feel like a poor fit.
It is not about “Development of Python”, it is not related to Packaging and it is also not a question about Python.
One solution I could think of is to have a subcategory in PEPs for these kind of topics that people could filter out in their notification settings? But like I said in the post as well, very open to other ideas.
I think this one would’ve been okay in “Development of Python” (“oh look, people are supporting this feature we added” is an okay topic). It also could probably have been okay in Developer Tools, depending on what audience you’re trying to reach, but python-dev / Core Development is a reasonable default for general discussions - if it still feels like the wrong place, then perhaps the topic is on the wrong forum entirely
We don’t have a generic announcements category (the python-announce mailing list is still active for that), but in any case that would mainly be for maintainers announcing their own topic.
I wouldn’t make it a subcategory of PEPs. In fact, I’d prefer the description of that category to be much stricter about what to post there and to offer a few alternatives.
All of those are fine for me, but with their current descriptions I still think they don’t offer a good fit.
In an ideal scenario I guess we would have a “PEP aftertalk” category. I think it is healthy for discussions/ideas/comments/etc. to pop up after a PEP was approved or implemented. The current workflow of (mostly) closing these topics after approval makes it harder for those engaged in the “design” phase of a PEP to interact and/or get feedback from users.
Except the PEP isn’t really meant to be that big a thing - it’s a proposal to change the language (or packaging, since they chose to adopt the PEP system). Once the proposal is dealt with, the only relevant discussion is to change it. Implementation/impacts/“aftertalk” isn’t part of the PEP, it’s part of either developing the language or managing packaging.
What we’re missing isn’t specific to PEPs - it’s a generic discussion category. You’re not proposing an idea, you’re not asking for help, you’re not advertising a release, and you’re not discussing the language (though in this case I think you are), but you still think the post is on-topic for this forum. That’s the missing category, nothing PEP-related.
What we’re missing isn’t specific to PEPs - it’s a generic discussion category.
Except that, per its description, the “help” category is also for “general discussion” (and was merely renamed so as to keep help requests from flooding the other topics).
I suppose this is really more about splitting help requests and general discussion into separate topics?
