[Python-Dev] Re: Switching to Discourse

On 15Jul2022 11:59, Ethan Furman wrote: >On 7/15/22 08:37, Petr Viktorin wrote: >> And that's exactly why I consume Discourse in mailing list mode, with >> client-side >> filtering in Thunderbird. > >How do you handle threading? I follow each (sub)thread through to >it's end, as it keeps a

[Python-Dev] Re: Switching to Discourse

To me, that’s the biggest negative of Discourse, and I definitely prefer threaded discussions. Unfortunately though, much like top posting , I think that horse is out of the barn, what with other forums like GitHub being linear. -Barry On Jul 15, 2022, at 11:59, Ethan Furman wrote: > > How

[Python-Dev] Re: Switching to Discourse

I am -1 for leaving email due to the long history of standardization, for a platform whose future I don't know about. When you say core development is busier, does that mean the experiment with python-dev failed? aka wasn't a success, if so why are we moving python-dev too if it's not working

[Python-Dev] Re: Switching to Discourse

On 7/15/22 08:37, Petr Viktorin wrote: > And that's exactly why I consume Discourse in mailing list mode, with client-side > filtering in Thunderbird. How do you handle threading? I follow each (sub)thread through to it's end, as it keeps a logical flow, but Discourse has everything linear

[Python-Dev] Re: Switching to Discourse

I support the move to Discourse. For me, the combination of GitHub, Discourse, and Discord work very well. Looking forward to one less mailing list subscription in my life ;) Erlend On Fri, 15 Jul 2022 at 13:27, Petr Viktorin wrote: > Hello, > Currently development discussions are split

[Python-Dev] Re: New `python` Organization Repository Policy

On Fri, Jul 15, 2022 at 4:54 AM Joannah Nanjekye wrote: > I understand that the steering council decides new repositories that can > be added to the Python organization but as a committer, it is good courtesy > that public decisions are discussed first on committer channels because > this

[Python-Dev] Re: Switching to Discourse

I think this is a great change, one I've been looking forward to myself. For authors of PEPs and discussion topics, Discourse provides better authoring experience, allowing for typo fixes and small edits. For moderators, Discourse also provides the toolings to make their jobs easier, which is

[Python-Dev] Re: Switching to Discourse

This might seem odd coming from me, but I’ve come around to supporting this move. Discourse is not without its issues, but then again, the same can be said about email. Without going into too much of my own personal preferences, I agree that the experiment has proven successful enough that

[Python-Dev] Re: [RELEASE] The cursed fourth Python 3.11 beta (3.11.0b4) is available

Since a few people have reacted to my PS comment: I suffered (committed) a very confusing typo; the github bot refers to "07/13/2022" (e.g. MM/DD/) which drew my ire, I then confusingly referenced a different format in my comment. Overall, I agree we should be using ISO8601 for exactly this

[Python-Dev] Re: Presenting PEP 695: Type Parameter Syntax

On 13/07/2022 14:14, o.jacob.nils...@gmail.com wrote: Hi, I like this PEP but I couldn't find the motivation for using angle brackets over square braces (brackets?). The survey in Appendix A is great but lacks any conclusions. From that survey alone I would assume that angle brackets would

[Python-Dev] Re: [RELEASE] The cursed fourth Python 3.11 beta (3.11.0b4) is available

Agreed on all 4 counts! :) ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at

[Python-Dev] Re: [SPAM] Re: Switching to Discourse

On 15. 07. 22 17:34, Phil Thompson via Python-Dev wrote: On 15/07/2022 16:09, Rob Boehne via Python-Dev wrote: 100% agree – dealing with 5 or more platforms for discussion groups is a nightmare, and I tend not to follow any of them as closely for that reason. I agree. I don't mind having to

[Python-Dev] Re: Switching to Discourse

On 15. 07. 22 16:24, Skip Montanaro wrote: The discuss.python.org experiment has been going on for quite a while, and while the platform is not without its issues, we consider it a success. The Core Development category is busier than python-dev.

[Python-Dev] Re: [SPAM] Re: Switching to Discourse

On 15/07/2022 16:09, Rob Boehne via Python-Dev wrote: 100% agree – dealing with 5 or more platforms for discussion groups is a nightmare, and I tend not to follow any of them as closely for that reason. I agree. I don't mind having to use Discourse if I want to take part in a discussion but

[Python-Dev] Re: Switching to Discourse

On Fri, Jul 15, 2022 at 9:33 AM Skip Montanaro wrote: > Email protocols were long ago standardized. As a result, people can use > any of a large number of applications to read and organize their email. To > my knowledge, there is no standardization amongst the various forum tools > out there. >

[Python-Dev] Re: [SPAM] Re: Switching to Discourse

100% agree – dealing with 5 or more platforms for discussion groups is a nightmare, and I tend not to follow any of them as closely for that reason. From: Skip Montanaro Date: Friday, July 15, 2022 at 9:26 AM To: Petr Viktorin Cc: python-dev@python.org Subject: [SPAM] [Python-Dev] Re:

[Python-Dev] Re: Switching to Discourse

> > The discuss.python.org experiment has been going on for quite a while, > and while the platform is not without its issues, we consider it a > success. The Core Development category is busier than python-dev. > According to staff, discuss.python.org is much easier to moderate.. If > you're

[Python-Dev] Re: Presenting PEP 695: Type Parameter Syntax

I actually really like some variation on `@with type S`, or some other variation that has a keyword, because that makes it much easier for someone newly encountering one of these syntax constructs to search to figure out what it does. If you didn't already know what the square brackets did,

[Python-Dev] Re: New `python` Organization Repository Policy

I understand that the steering council decides new repositories that can be added to the Python organization but as a committer, it is good courtesy that public decisions are discussed first on committer channels because this impacts allow us to a degree I.e you are some how responsible for that

[Python-Dev] New `python` Organization Repository Policy

(Cross-posted from https://discuss.python.org/t/new-python-organization-repository-policy/17376 – please perfer commenting there.) Hello, When asked about adding the typing_extensions repository to the Python organization (https://github.com/python/steering-council/issues/126), the Steering

[Python-Dev] Switching to Discourse

Hello, Currently development discussions are split between multiple communication channels, for example: - python-dev and discuss.python.org for design discussions, - GitHub Issues and Pull Requests for specific changes, - IRC, Discord and private chats for real-time discussions, -