On 8/2/2018 8:01 PM, Yury Selivanov wrote:
On Thu, Aug 2, 2018 at 4:43 PM Brett Cannon wrote:
On Wed, 1 Aug 2018 at 17:58 Yury Selivanov wrote:
On Wed, Aug 1, 2018 at 8:29 PM Mariatta Wijaya
wrote:
[..]
I'm open to extend the dates, and even wait another year if we need to.
Or do folks wa
> as long we are okay with long-dormant folk who predate this list not
voting (which I'm personally fine with)
That sounds reasonable. Maintaining contact info is everyone's own
responsibility and not a too hard requirement.
And I see that for the vote it's necessary to sort out emails more
carefu
On Thu, Aug 2, 2018 at 3:55 PM Jack Jansen wrote:
>
> Nathaniel, you strike the nail on the head here.
>
> The reason Guido as BDFL and therefore ultimate authority on what “python” is
> worked because it is organic: it is not set down in strict rules and
> regulations and timelines and percenta
On Thu, Aug 2, 2018 at 4:43 PM Brett Cannon wrote:
>
> On Wed, 1 Aug 2018 at 17:58 Yury Selivanov wrote:
>>
>> On Wed, Aug 1, 2018 at 8:29 PM Mariatta Wijaya
>> wrote:
>> [..]
>> > I'm open to extend the dates, and even wait another year if we need to.
>> > Or do folks want to come up with a com
On Thu, 2 Aug 2018 at 04:54 Stefan Richthofer
wrote:
> Again, this was in the (poorly conveyed) context of getting email
>> addresses for them, or at least being able to contact them.
>>
>
> I always thought there were already at least three places containing the
> necessary email addresses.
>
>
On Wed, 1 Aug 2018 at 14:29 Mariatta Wijaya
wrote:
> See also an open issue to revamp the Developer log:
> https://github.com/python/devguide/issues/390
>
> Someone has also said that they're working on tracking down the dormant
> core devs, but now I can't find that email.
>
Ethan said he would
On Thu, 2 Aug 2018 at 00:32 M.-A. Lemburg wrote:
> On 02.08.2018 03:24, Eric V. Smith wrote:
> > On 8/1/2018 8:32 PM, Mariatta Wijaya wrote:
> >> I think it would also be a good idea to include core developers
> >> of other Python implementations in such a document, in
> >> separate s
On Wed, 1 Aug 2018 at 14:44 M.-A. Lemburg wrote:
> On 01.08.2018 23:28, Mariatta Wijaya wrote:
> > See also an open issue to revamp the Developer log:
> > https://github.com/python/devguide/issues/390
> >
> > Someone has also said that they're working on tracking down the dormant
> > core devs, b
On Thu, 2 Aug 2018 at 13:02 Jack Jansen wrote:
>
> > On Aug 1, 2018, at 23:37, Antoine Pitrou wrote:
> >
> >
> >
> >> Le 01/08/2018 à 23:31, Jack Diederich a écrit :
> >> https://hg.python.org/committers.txt
> >
> > Probably outdated, for example Pablo Salingo Salgado doesn't seem there.
>
> And
On Thu, 2 Aug 2018 at 00:24 Ronald Oussoren via python-committers <
python-committers@python.org> wrote:
>
>
> > On 2 Aug 2018, at 01:06, Yury Selivanov wrote:
> >
> > On Wed, Aug 1, 2018 at 6:44 PM Mariatta Wijaya
> > wrote:
> >>
> >
> >> Currently any undecided PEP is stalled, and no one can p
On Wed, 1 Aug 2018 at 17:58 Yury Selivanov wrote:
> On Wed, Aug 1, 2018 at 8:29 PM Mariatta Wijaya
> wrote:
> [..]
> > Please don't misunderstand my wanting to set up a deadlines and process
> as wanting to rush things.
>
> Absolutely, I understand, I didn't want to imply that "[name] is
> rushi
> On Aug 1, 2018, at 23:37, Antoine Pitrou wrote:
>
>
>
>> Le 01/08/2018 à 23:31, Jack Diederich a écrit :
>> https://hg.python.org/committers.txt
>
> Probably outdated, for example Pablo Salingo Salgado doesn't seem there.
And historically incomplete: I seem to be missing from that list, ev
Nathaniel, you strike the nail on the head here.
The reason Guido as BDFL and therefore ultimate authority on what “python” is
worked because it is organic: it is not set down in strict rules and
regulations and timelines and percentages of votes and what not. It works
because a very large frac
On behalf of the Python development community, I'm happy to announce the
availability of Python 3.4.9 and Python 3.5.6.
Both Python 3.4 and 3.5 are in "security fixes only" mode. Both
versions only accept security fixes, not conventional bug fixes, and
both releases are source-only.
You
On 8/2/2018 7:53 AM, Stefan Richthofer wrote:
Again, this was in the (poorly conveyed) context of getting email
addresses for them, or at least being able to contact them.
I always thought there were already at least three places containing the
necessary email addresses.
* python-com
>
> Again, this was in the (poorly conveyed) context of getting email
> addresses for them, or at least being able to contact them.
>
I always thought there were already at least three places containing the
necessary email addresses.
* python-committers should be exactly this mailing list.
* acco
2018-08-01 23:10 GMT+02:00 M.-A. Lemburg :
> So let's ponder some more about ideas we could use to
> get there and perhaps watch some Monty Python movies for
> inspiration ;-)
Monty Python's Life of Brian is an obvious tutorial how to select a
BDFL where FL means for life ;-)
Victor
_
Hi,
The error may be related to https://bugs.python.org/issue33782
I understood that VSTS has troubles when a PR gets a new commit while
VSTS is running tests on the previous commit.
Victor
2018-08-02 0:00 GMT+02:00 Antoine Pitrou :
>
> Hello,
>
> I may be missing something, but I fail to view
On 8/2/2018 3:32 AM, M.-A. Lemburg wrote:
On 02.08.2018 03:24, Eric V. Smith wrote:
On 8/1/2018 8:32 PM, Mariatta Wijaya wrote:
I think it would also be a good idea to include core developers
of other Python implementations in such a document, in
separate sections, e.g. for Jytho
On Thu, 2 Aug 2018 at 08:50, Steven D'Aprano wrote:
> Indeed. A hard deadline concentrates the mind. It doesn't need to be
> tomorrow, I think your choosen dates are a great balance, neither too
> quick nor too drawn out.
But it also encourages people (particularly people with limited free
time)
On Thu, 2 Aug 2018 at 01:58, Yury Selivanov wrote:
>
> On Wed, Aug 1, 2018 at 8:29 PM Mariatta Wijaya
> wrote:
> [..]
> > Please don't misunderstand my wanting to set up a deadlines and process as
> > wanting to rush things.
>
> Absolutely, I understand, I didn't want to imply that "[name] is
>
On Wed, Aug 01, 2018 at 05:29:00PM -0700, Mariatta Wijaya wrote:
> Please don't misunderstand my wanting to set up a deadlines and process as
> wanting to rush things.
> I'm open to extend the dates, and even wait another year if we need to.
Please no. Leaving things in limbo for a handful of mon
On 02.08.2018 03:24, Eric V. Smith wrote:
> On 8/1/2018 8:32 PM, Mariatta Wijaya wrote:
>> I think it would also be a good idea to include core developers
>> of other Python implementations in such a document, in
>> separate sections, e.g. for Jython, IronPython, PyPy,
>> Stackless,
> On 2 Aug 2018, at 01:06, Yury Selivanov wrote:
>
> On Wed, Aug 1, 2018 at 6:44 PM Mariatta Wijaya
> wrote:
>>
>
>> Currently any undecided PEP is stalled, and no one can pronounce on them.
>
> And maybe that's OK for a few months? I don't recall Guido ever
> accepting PEPs promptly. :) S
24 matches
Mail list logo
