On 2018-07-22 08:27, INADA Naoki wrote:
It's interesting... But I failed to build sage.
What went wrong?
It's build step is
too different from
normal Python package.
That's true because Sage considers itself a distribution rather than a
package. But it's possible to pick the distribution a
On 2018-07-22 01:14, Guido van Rossum wrote:
Jeroen was asked to provide benchmarks
but only provided them for Python 2. The reasoning that not much has
changed that could affect the benchmarks feels a bit optimistic, that’s all.
The micro-benchmarks showed a clear difference on Python 3.8 (git
Guido van Rossum schrieb am 22.07.2018 um 01:14:
> The cost would be if we were to end up maintaining all that code and it
> wouldn’t make much difference.
Well, this is exactly my point. Someone has to maintain the *existing* code
base and help newcomers to get into it and understand it. This is
OK, I believe you, I was just referring to the relative irreproducibility
of Jeroen's results (see INADA Naoki's problems).
My main point is actually that until the Python core devs have elected a
new BDFL or come up with some other process for accepting PEPs, no action
will be taken on this PEP -
On 2018-07-22 18:14, Guido van Rossum wrote:
Sorry I don't have better news.
I don't consider that particularly bad news (but not good news either).
I feel like the status on PEP 580 isn't anywhere near accepted anyway.
I just hope that Python development won't stall completely. Even if no
On 2018-07-22 14:52, Stefan Behnel wrote:
Someone has to maintain the *existing* code
base and help newcomers to get into it and understand it.
This is an important point that people seem to be overlooking. The
complexity and maintenance burden of PEP 580 should be compared to the
status-quo.
Guido's term as Benevolent Dictator For Life has been a long one, but
in the wake of his resignation, we have an opportunity to correct some
fundamental flaws in the system. Among them:
* Guido lacks patience, as evidenced by the brevity of his acceptance
posts. See
https://mail.python.org/piperm
On Sun, 22 Jul 2018 22:11:25 +0200
Jeroen Demeyer wrote:
> On 2018-07-22 14:52, Stefan Behnel wrote:
> > Someone has to maintain the *existing* code
> > base and help newcomers to get into it and understand it.
>
> This is an important point that people seem to be overlooking. The
> complexity
On 2018-07-22 22:32, Antoine Pitrou wrote:
Two things:
- the issue26110 changes are not very large, it's just two additional
opcodes and a bit of support code
I didn't mean to compare PEP 580 to that specific issue, it was just an
example. Even if issue26110 is small, the total complexity a
Jeroen Demeyer schrieb am 22.07.2018 um 22:54:
> On 2018-07-22 22:32, Antoine Pitrou wrote:
>> - more importantly, issue26110 is entirely internal changes, while you
>> are proposing to add a new protocol (which is like a new API)
>
> Just to make sure I understand you: your point is that it's
On Sun, 22 Jul 2018 22:54:24 +0200
Jeroen Demeyer wrote:
>
> > - more importantly, issue26110 is entirely internal changes, while you
> >are proposing to add a new protocol (which is like a new API)
>
> Just to make sure I understand you: your point is that it's
> automatically more compl
On Sun, Jul 22, 2018 at 1:11 PM, Jeroen Demeyer wrote:
> On 2018-07-22 14:52, Stefan Behnel wrote:
>
>> Someone has to maintain the *existing* code
>> base and help newcomers to get into it and understand it.
>>
>
> This is an important point that people seem to be overlooking. The
> complexity a
On Sun, Jul 22, 2018 at 1:19 PM Chris Angelico wrote:
> * Finally, "For Life" is far too long. We need to change our rulers
> periodically.
>
With the proposed bi-weekly death matches, "for life" may actually be too
short.
___
Python-Dev mailing list
I think it'll benefit all to keep the discussion objective, or at least
"good subjective"
(https://stackoverflow.blog/2010/09/29/good-subjective-bad-subjective/).
Laments or mutual accusations are only wasting everyone's time,
including the writers.
It's strange that even Guido jumped on the ba
Whatever you decide, please research existing practices and their
results so as not to repeat the same mistakes as others made before you.
In particular, http://meatballwiki.org/wiki/BenevolentDictator and
https://en.wikipedia.org/wiki/Anti-pattern .
It would be a waste if Python falls victim to
sometimes back after the event the BDFL1 said that "the new BDFL might be
less demanding"
hint to an imminent new one? i won't tell much the core devs (not all) have
already shown their preferences
fun fact: weirdly enough after BDFL1 took a vac (for life?), google made
it's appearance on the mai
16 matches
Mail list logo
