This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients Aaron Hall, barry, brett.cannon, eric.snow, gvanrossum, levkivskyi, methane, ned.deily, scoder, serhiy.storchaka, vstinner, yselivanov
Date 2018-02-17.19:15:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJKMERXZyS=C9Vq_g1C79uRK4TSmf-1-h4j=S8cU7yK0iA@mail.gmail.com>
In-reply-to <1518892060.87.0.467229070634.issue31333@psf.upfronthosting.co.za>
Content
> Isn't 800 lines of C code too high price for speeding up ABCs creation?

I think it's well worth it. This has long felt as a sore point to me.

On Sat, Feb 17, 2018 at 10:27 AM, Ivan Levkivskyi <report@bugs.python.org>
wrote:

>
> Ivan Levkivskyi <levkivskyi@gmail.com> added the comment:
>
> > Isn't 800 lines of C code too high price for speeding up ABCs creation?
>
> 800 lines of C code is not something hard to notice, so I suppose the
> answer is obvious for all people involved in the work on PR :-)
>
> > ...this can save just several milliseconds at start-up.
>
> The correct way to measure this is relative, not absolute. There are just
> few ABCs used by modules loaded at Python start-up, and it already allowed
> to save 10% of start-up time. My expectation is that the number will be
> similar for a typical Python app. Moreover, `isinstance` and `issubclass`
> (functions called often with ABCs) will be 1.5x faster.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue31333>
> _______________________________________
>
History
Date User Action Args
2018-02-17 19:15:01gvanrossumsetrecipients: + gvanrossum, barry, brett.cannon, scoder, vstinner, ned.deily, methane, eric.snow, serhiy.storchaka, yselivanov, levkivskyi, Aaron Hall
2018-02-17 19:15:01gvanrossumlinkissue31333 messages
2018-02-17 19:15:01gvanrossumcreate