On Fri, Jul 15, 2022 at 12:15 PM Barry Warsaw wrote:
> I agree that the experiment has proven successful enough that there’s more
> value at this point in consolidating discussions.
We've only been running this experiment since 2017(?) so maybe it's
too soon to say it's a success?
-eric
_
On Fri, Jul 15, 2022 at 5:21 AM Petr Viktorin wrote:
> The Steering Council would like to switch from python-dev to
> discuss.python.org.
This seems like a net win for the community so +1 from me. (For me
personally it amounts to disruption with little advantage, so I'd
probably be -0). However
On Mon, Jul 18, 2022 at 11:48 AM wrote:
> LLVM did the same recently (though they imported all previous messages from
> the mailinglist, thus making them searchable in discourse) [2 - announcement;
> 3 - retro], and by and large, I think it was a success.
>
> One of the comments in the retro was
On Tue, Jul 19, 2022 at 2:17 PM Kevin T via Python-Dev <
python-dev@python.org> wrote:
> I have built this on systems at work, that are populated by CAD guys who
> have developed a good set of libraries to maintain in a linux
> distribution. Went without a hitch.
>
> I am trying to build this at
The SC has been notified of at least one instance of someone subscribed to
this list harassing another subscriber privately. We wanted to remind folks
that we expect people to behave reasonably towards each other, else people
risk losing access to this mailing list and other places where Python is
Thank you Brett and totally agree.
Learning should not be clouded by any other agenda, we are very smart people
and should conduct ourselves as such, with respect.
From: Brett Cannon
Sent: Wednesday, July 20, 2022 5:55 PM
To: python-dev
Subject: [Python-Dev] Do not harass other mailing list su
On 18Jul2022 16:53, Joannah Nanjekye wrote:
>I see I might have misunderstood, thinking a python-dev channel on discuss
>was not as active as the mailing list. Understood.
>
>My original stand on preferring email stands though due to stable
>standards.
Several of us use the email mode in Discour
On 7/20/22 17:35, Cameron Simpson wrote:
> On 18Jul2022 16:53, Joannah Nanjekye wrote:
>> My original stand on preferring email stands though due to stable
>> standards.
>
> Several of us use the email mode in Discourse. It works quite well. For
> me, both python-dev and the PDO posts land in my
Eric Snow writes:
> I consider the ability to search message archives to be essential to
> effective contribution[.]
+1
> There are relevant three aspects to archival and search that are worth
> asking about here:
>
> 1. search functionality on the [archive] web site
> 2. ability to sear
On 21Jul2022 10:29, Stephen J. Turnbull wrote:
>As long as Discourse provides the In-Reply-To header field, the current
>threading algorithm would work reasonably well.
Discourse does not do `In-Reply-To:` very well at all. Here's some
headers from the _second_ post in the "Core dev sprint this
I'm -1 on moving to the walled garden, but I don't expect this to change
anyone's mind. I don't know if I'll move over to Discourse or not.
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
ht
Cameron Simpson writes:
> Discourse does not do `In-Reply-To:` very well at all. Here's some
> headers from the _second_ post in the "Core dev sprint this year"
> thread:
>
> Message-ID:
>
> In-Reply-To:
> References:
I'm tempted to write something uncivil, but instead
h.vetin...@gmx.com schrieb am 18.07.22 um 18:04:
One of the comments in the retro was:
Searching the archives is much easier and have found me many old threads that I
probably would have problem finding before since I haven’t been subscribed for
that long.
I'm actually reading python-dev, c.
13 matches
Mail list logo
