On Sun, Jul 22, 2018 at 11:18 PM Chris Angelico wrote:
>
> * Lately, all Guido's actions have been to benefit his employer, not
> the Common Pythonista. We have proof of this from reliable reporting
> sources such as Twitter and social media.
>
This accusation is ridiculous and not appreciated.
On Mon, 23 Jul 2018 11:47:25 +0300
Yury Selivanov wrote:
> On Sun, Jul 22, 2018 at 11:18 PM Chris Angelico wrote:
>
> >
> > * Lately, all Guido's actions have been to benefit his employer, not
> > the Common Pythonista. We have proof of this from reliable reporting
> > sources such as Twitter an
On Mon, Jul 23, 2018 at 12:03 PM Antoine Pitrou wrote:
>
> I suspect Chris A. was merely joking, though I'm not sure what the joke
> ultimately is supposed to be about.
>
Ah, right, I stopped reading his email after the quoted line. Well executed.
Yury
>
> --
Yury
__
Hi!
On Mon, Jul 23, 2018 at 11:47:25AM +0300, Yury Selivanov
wrote:
> On Sun, Jul 22, 2018 at 11:18 PM Chris Angelico wrote:
>
> >
> > * Lately, all Guido's actions have been to benefit his employer, not
> > the Common Pythonista. We have proof of this from reliable reporting
> > sources such
I did exactly the same benchmark again with Python 3.7 and the results
are similar. I'm copying and editing the original post for completeness:
I finally managed to get some real-life benchmarks for why we need a
faster C calling protocol (see PEPs 576, 579, 580).
I focused on the Cython compil
On Mon, 23 Jul 2018 11:51:41 +0200
Jeroen Demeyer wrote:
> I did exactly the same benchmark again with Python 3.7 and the results
> are similar. I'm copying and editing the original post for completeness:
>
> [...]
>
> I hope that this finally shows that the problems mentioned in PEP 579
> are
On Mon, Jul 23, 2018 at 7:07 PM, Oleg Broytman wrote:
> Hi!
>
> On Mon, Jul 23, 2018 at 11:47:25AM +0300, Yury Selivanov
> wrote:
>> On Sun, Jul 22, 2018 at 11:18 PM Chris Angelico wrote:
>>
>> >
>> > * Lately, all Guido's actions have been to benefit his employer, not
>> > the Common Pythonist
On Mon, Jul 23, 2018 at 08:37:05PM +1000, Chris Angelico
wrote:
> On Mon, Jul 23, 2018 at 7:07 PM, Oleg Broytman wrote:
> > I also didn't get initially that it was a joke, it took me
> > a few minutes to understand.
>
> If the reference to PEP 401 didn't tip you off and you don't recognize
> th
Please, take this thread off-list. Nobody is interested in you
explaining a joke.
On Mon, 23 Jul 2018 20:37:05 +1000
Chris Angelico wrote:
> On Mon, Jul 23, 2018 at 7:07 PM, Oleg Broytman wrote:
> > Hi!
> >
> > On Mon, Jul 23, 2018 at 11:47:25AM +0300, Yury Selivanov
> > wrote:
> >> On
On 2018-07-23 01:54, Ivan Pozdeev via Python-Dev wrote:
All the material to discuss that we have in this thread is a single test
result that's impossible to reproduce and impossible to run in Py3.
I just posted that it can be reproduced on Python 3.7:
https://mail.python.org/pipermail/python-de
On Mon, Jul 23, 2018 at 7:20 PM Antoine Pitrou wrote:
>
> Just for the record, personally I have no doubt that the problems are
> real. IMHO the main point of discussion should be judging the solution
> you are proposing (and thank you, really, for being persistent, since
> this isn't an easy dis
On 2018-07-23 00:28, Guido van Rossum wrote:
So does your implementation of the PEP result in a net increase or
decrease of the total lines of code?
12 files changed, 918 insertions(+), 704 deletions(-)
That's a net increase, so there is no obvious win here. Still, I have
various excuses for
On Sun, Jul 22, 2018 at 7:42 PM Jeroen Demeyer wrote:
>
> On 2018-07-22 08:27, INADA Naoki wrote:
> > It's interesting... But I failed to build sage.
>
> What went wrong?
>
I can't install Sage into my virtual environment, so I can't run
> python -m timeit -s "from sage.all import MatrixSpace, G
On 2018-07-23 12:13, Antoine Pitrou wrote:
IMHO the main point of discussion should be judging the solution
you are proposing
Yes please. I would very much welcome a discussion about the actual
content of the PEP instead of meta-discussions like how complicated it is.
___
Hello list,
I encountered a problem with the Windows packaging of gPodder[1]
using msys2:
basic libraries (zlib, openssl) depended upon by python
platform-specific modules are loaded preferably :
1. from lib-dynload (where they are not)
2. from the Windows directory (can be any version)
3. fro
In general, if the dependent DLL is in the same directory as the module
loading it (the .pyd or .exe), then it should be loaded first. If it's
alongside the .exe, it should be loaded before any of the other search
paths. If it's being loaded directly from Python, your best option is to
resolve
On Mon, Jul 23, 2018, 08:22 Eric Le Lay wrote:
> Hello list,
>
> I encountered a problem with the Windows packaging of gPodder[1]
> using msys2:
>
> basic libraries (zlib, openssl) depended upon by python
> platform-specific modules are loaded preferably :
> 1. from lib-dynload (where they are n
> fun fact: weirdly enough after BDFL1 took a vac (for life?), google made
> it's appearance on the mailing list
>
As the Googler who appeared on the mailing list, I can say this was just a
coincidence. I was a bit nervous no one would respond though, given Guido's
vacation :)
18 matches
Mail list logo
