[Python-Dev] Migrate python-dev to Mailman 3?

Hi, We are using Mailman 3 for the new buildbot-status mailing list and it works well: https://mail.python.org/mm3/archives/list/buildbot-sta...@python.org/ I prefer to read archives with this UI, it's simpler to follow threads, and it's possible to reply on the web UI! To be honest, we got som

Re: [Python-Dev] Migrate python-dev to Mailman 3?

On Thu, 26 Oct 2017 11:24:54 +0200 Victor Stinner wrote: > > We are using Mailman 3 for the new buildbot-status mailing list and it > works well: > > https://mail.python.org/mm3/archives/list/buildbot-sta...@python.org/ > > I prefer to read archives with this UI, it's simpler to follow > thread

Re: [Python-Dev] Migrate python-dev to Mailman 3?

2017-10-26 12:01 GMT+02:00 Antoine Pitrou : > Is it possible to have a > pipermail-style UI as an alternative? I don't know pipermail. Do you have an example? I don't think that Mailman 3 gives the choice of the UI for archives. I didn't ask anyone to write a new software. I only proposed to use

Re: [Python-Dev] Migrate python-dev to Mailman 3?

Le 26/10/2017 à 12:15, Victor Stinner a écrit : > 2017-10-26 12:01 GMT+02:00 Antoine Pitrou : >> Is it possible to have a >> pipermail-style UI as an alternative? > > I don't know pipermail. Do you have an example? https://mail.python.org/pipermail/python-dev/ :-) > The main drawback of Mailman

Re: [Python-Dev] Migrate python-dev to Mailman 3?

On 26 October 2017 at 20:19, Antoine Pitrou wrote: > > Le 26/10/2017 à 12:15, Victor Stinner a écrit : > > 2017-10-26 12:01 GMT+02:00 Antoine Pitrou : > >> Is it possible to have a > >> pipermail-style UI as an alternative? > > > > I don't know pipermail. Do you have an example? > > https://mail.

Re: [Python-Dev] Migrate python-dev to Mailman 3?

Le 26/10/2017 à 14:40, Nick Coghlan a écrit : > > If folks want to see MM3 in action with some more active lists, I'd > suggest looking at the Fedora MM3 instance, especially the main dev > list: > https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org> > There's a 100 messag

Re: [Python-Dev] Migrate python-dev to Mailman 3?

On 26 October 2017 at 10:24, Victor Stinner wrote: > We are using Mailman 3 for the new buildbot-status mailing list and it > works well: > > https://mail.python.org/mm3/archives/list/buildbot-sta...@python.org/ > > I prefer to read archives with this UI, it's simpler to follow > threads, and it's

Re: [Python-Dev] Migrate python-dev to Mailman 3?

> On Oct 26, 2017, at 6:19 AM, Antoine Pitrou wrote: > > The pipermail UI isn't perfect (the monthly segregation can be annoying > as you point out), but at least it has a synthetic and easy-to-navigate > tree view. Pipermail is *horrible* and it’s tree view makes things actively harder to read

Re: [Python-Dev] Migrate python-dev to Mailman 3?

Le 26/10/2017 à 16:01, Donald Stufft a écrit : > >> On Oct 26, 2017, at 6:19 AM, Antoine Pitrou > > wrote: >> >> The pipermail UI isn't perfect (the monthly segregation can be annoying >> as you point out), but at least it has a synthetic and easy-to-navigate >> tree vi

Re: [Python-Dev] Migrate python-dev to Mailman 3?

On Thursday, October 26, 2017, Paul Moore wrote: > On 26 October 2017 at 10:24, Victor Stinner > wrote: > > We are using Mailman 3 for the new buildbot-status mailing list and it > > works well: > > > > https://mail.python.org/mm3/archives/list/buildbot-sta...@python.org/ > > > > I prefer to rea

Re: [Python-Dev] iso8601 parsing

On Wed, Oct 25, 2017 at 7:37 PM, Wes Turner wrote: > ISO 8601 support offsets, but not time zones -- presumably the __str__ >> supports the full datetime tzinfo somehow. Which may be why .isoformat() >> exists. >> > > ISO8601 does support timezones. > https://en.wikipedia.org/wiki/ISO_8601#Time_z

Re: [Python-Dev] iso8601 parsing

From: Python-Dev [mailto:python-dev-bounces+tritium-list=sdamon@python.org] On Behalf Of Chris Barker Sent: Thursday, October 26, 2017 12:46 PM To: Wes Turner Cc: Python-Dev Subject: Re: [Python-Dev] iso8601 parsing > No, it doesn't -- it may call them "timezones", but it only supp

Re: [Python-Dev] Migrate python-dev to Mailman 3?

On 10/26/2017 07:28 AM, Wes Turner wrote: > > > On Thursday, October 26, 2017, Paul Moore wrote: > > On 26 October 2017 at 10:24, Victor Stinner > wrote: > > We are using Mailman 3 for the new buildbot-status mailing list and it > > works well: > > > > > https://mai

Re: [Python-Dev] iso8601 parsing

On Thursday, October 26, 2017, Chris Barker wrote: > On Wed, Oct 25, 2017 at 7:37 PM, Wes Turner > wrote: > >> ISO 8601 support offsets, but not time zones -- presumably the __str__ >>> supports the full datetime tzinfo somehow. Which may be why .isoformat() >>> exists. >>> >> >> ISO8601 does su

Re: [Python-Dev] Migrate python-dev to Mailman 3?

On Thursday, October 26, 2017, Mark Sapiro wrote: > On 10/26/2017 07:28 AM, Wes Turner wrote: > > > > > > On Thursday, October 26, 2017, Paul Moore > wrote: > > > > On 26 October 2017 at 10:24, Victor Stinner > > > wrote: > > > We are using Mailman 3 for the new buildbot-status maili

[Python-Dev] PEP 561: Distributing and Packaging Type Information

Hello all, I have completed an implementation for PEP 561, and believe it is time to share the PEP and implementation with python-dev Python-ideas threads: * PEP 561: Distributing and Packaging Type Information * PEP 561 v2 - Packaging Static Type Information * PEP 561: Distributing Type Infor

Re: [Python-Dev] PEP 561: Distributing and Packaging Type Information

Hi! On Thu, Oct 26, 2017 at 03:42:19PM -0700, Ethan Smith wrote: > Post-History: Not sure if postings to python-ideas count, but Post-History: 10-Sep-2017, 12-Sep-2017, 26-Oct-2017 Refs: https://mail.python.org/pipermail/python-ideas/2017-September/047015.html https://mail.python.org/pip

Re: [Python-Dev] PEP 561: Distributing and Packaging Type Information

> > Not sure if postings to python-ideas count, PEP 1 says: Post-History is used to record the dates of when new versions of the PEP are posted to python-list and/or python-dev. So, no ? Mariatta Wijaya ___ Python-Dev mailing list Python-Dev@python.o

Re: [Python-Dev] PEP 561: Distributing and Packaging Type Information

On Thu, Oct 26, 2017 at 04:48:23PM -0700, Mariatta Wijaya wrote: > > > > Not sure if postings to python-ideas count, > > PEP 1 says: > > Post-History is used to record the dates of when new versions of the PEP > are posted to python-list and/or python-dev. That's was added in 2003: https://

Re: [Python-Dev] PEP 561: Distributing and Packaging Type Information

On Thu, Oct 26, 2017 at 4:48 PM, Mariatta Wijaya wrote: > Not sure if postings to python-ideas count, > > > PEP 1 says: > > Post-History is used to record the dates of when new versions of the PEP > are posted to python-list and/or python-dev. > > So, no ? > Reading PEP 12, https://www.python.o

Re: [Python-Dev] PEP 561: Distributing and Packaging Type Information

I think python-ideas does count here. Many PEPs evolve mostly there. On Oct 26, 2017 4:59 PM, "Oleg Broytman" wrote: > On Thu, Oct 26, 2017 at 04:48:23PM -0700, Mariatta Wijaya < > mariatta.wij...@gmail.com> wrote: > > > > > > Not sure if postings to python-ideas count, > > > > PEP 1 says: > > >

Re: [Python-Dev] PEP 561: Distributing and Packaging Type Information

Ok I created an issue https://github.com/python/peps/issues/440, maybe someone can work on updating the wordings in PEP 1 and PEP 12. Thanks :) Mariatta Wijaya On Thu, Oct 26, 2017 at 5:03 PM, Guido van Rossum wrote: > I think python-ideas does count here. Many PEPs evolve mostly there. > > > _

Re: [Python-Dev] PEP 561: Distributing and Packaging Type Information

Proposed pull request: https://github.com/python/peps/pull/441 On Thu, Oct 26, 2017 at 05:21:57PM -0700, Mariatta Wijaya wrote: > Ok I created an issue https://github.com/python/peps/issues/440, maybe > someone can work on updating the wordings in PEP 1 and PEP 12. > Thanks :) > > Mariatta Wija

Re: [Python-Dev] PEP 561: Distributing and Packaging Type Information

On Oct 26, 2017, at 20:03, Guido van Rossum wrote: > > I think python-ideas does count here. Many PEPs evolve mostly there. True, but there was some discussion of this way back when. The way I remember it was that, while there are many outlets to discuss PEPs (including those pointed to by the

Re: [Python-Dev] Migrate python-dev to Mailman 3?

On Oct 26, 2017, at 06:15, Victor Stinner wrote: > I don't think that Mailman 3 gives the choice of the UI for archives. Technically, it does. Mailman 3 has a pluggable architecture and supports multiple archives enabled site-wide and opt-in by individual lists. HyperKitty is the default arch

Re: [Python-Dev] Migrate python-dev to Mailman 3?

On Oct 26, 2017, at 10:01, Donald Stufft wrote: > Pipermail is *horrible* Pipermail also has a fatal flaw, and we have been hit by it several times in our past. It’s fundamental to Pipermail’s design and can’t be fixed. Fortunately, HyperKitty was designed and implemented correctly so it doe

Re: [Python-Dev] PEP 561: Distributing and Packaging Type Information

Heh, you're right that was the reasoning. But I think python-list is much less valuable than python-ideas for PEP authors. So let's change it. On Thu, Oct 26, 2017 at 6:38 PM, Barry Warsaw wrote: > On Oct 26, 2017, at 20:03, Guido van Rossum wrote: > > > > I think python-ideas does count here.

Re: [Python-Dev] Migrate python-dev to Mailman 3?

On 27 October 2017 at 00:28, Wes Turner wrote: > > On Thursday, October 26, 2017, Paul Moore wrote: > >> So basically, what I'm asking is what would be the support for the use >> case "Find a permanent link to an archived article as fast as possible >> based on subject/author or a Google search"