t;
> Date: Friday, October 7, 2022 at 1:30 PM
> To: MRAB mailto:pyt...@mrabarnett.plus.com>>
> Cc: python-list@python.org <mailto:python-list@python.org>
> mailto:python-list@python.org>>
> Subject: Re: Ref-strings in logging messages (was: Performance issue with
hello"
logging.basicConfig()
logging.debug(Defer(some_expensive_function))
From: Python-list on
behalf of Barry
Date: Friday, October 7, 2022 at 1:30 PM
To: MRAB
Cc: python-list@python.org
Subject: Re: Ref-strings in logging messages (was: Performance issue with
CPython 3.10 + Cython)
*** Attentio
On Fri, 7 Oct 2022 18:28:06 +0100
Barry wrote:
> > On 7 Oct 2022, at 18:16, MRAB wrote:
> >
> > On 2022-10-07 16:45, Skip Montanaro wrote:
> >>> On Fri, Oct 7, 2022 at 9:42 AM Andreas Ames
> >>>
> >>> wrote:
> >>> 1. The culprit was me. As lazy as I am, I have used f-strings all over the
>
ebug = logger_from(DEBUG)
log_debug and log_debug(‘expensive %s’ % (complex(),))
Barry
>
> From: Python-list on
> behalf of Barry
> Date: Friday, October 7, 2022 at 1:30 PM
> To: MRAB
> Cc: python-list@python.org
> Subject: Re: Ref-strings in logging messages (was: Pe
To: MRAB
Cc: python-list@python.org
Subject: Re: Ref-strings in logging messages (was: Performance issue with
CPython 3.10 + Cython)
*** Attention: This is an external email. Use caution responding, opening
attachments or clicking on links. ***
> On 7 Oct 2022, at 18:16, MRAB wrote:
>
> On 7 Oct 2022, at 18:16, MRAB wrote:
>
> On 2022-10-07 16:45, Skip Montanaro wrote:
>>> On Fri, Oct 7, 2022 at 9:42 AM Andreas Ames
>>> wrote:
>>> 1. The culprit was me. As lazy as I am, I have used f-strings all over the
>>> place in calls to `logging.logger.debug()` and friends, evaluatin
On 2022-10-07 16:45, Skip Montanaro wrote:
On Fri, Oct 7, 2022 at 9:42 AM Andreas Ames
wrote:
1. The culprit was me. As lazy as I am, I have used f-strings all over the
place in calls to `logging.logger.debug()` and friends, evaluating all
arguments regardless of whether the logger was enabled
> On 7 Oct 2022, at 16:48, Skip Montanaro wrote:
>
> On Fri, Oct 7, 2022 at 9:42 AM Andreas Ames
> wrote:
>
>> 1. The culprit was me. As lazy as I am, I have used f-strings all over the
>> place in calls to `logging.logger.debug()` and friends, evaluating all
>> arguments regardless of wheth
Dang autocorrect. Subject first word was supposed to be "f-strings" not
"ref-strings." Sorry about that.
S
On Fri, Oct 7, 2022, 10:45 AM Skip Montanaro
wrote:
>
>
> On Fri, Oct 7, 2022 at 9:42 AM Andreas Ames
> wrote:
>
>> 1. The culprit was me. As lazy as I am, I have used f-strings all over
On Fri, Oct 7, 2022 at 9:42 AM Andreas Ames
wrote:
> 1. The culprit was me. As lazy as I am, I have used f-strings all over the
> place in calls to `logging.logger.debug()` and friends, evaluating all
> arguments regardless of whether the logger was enabled or not.
>
I thought there was some dis
Answering to myself, just for the records:
1. The culprit was me. As lazy as I am, I have used f-strings all over the
place in calls to `logging.logger.debug()` and friends, evaluating all
arguments regardless of whether the logger was enabled or not. Replacing
these f-strings by regular printf-l
Hi all,
I am wrapping an embedded application (, which does not use any dynamic
memory management,) using Cython to call it from CPython. The wrapped
application uses a cyclic executive, i.e. everything is done in the
input-logic-output design, typical for some real-time related domains.
Conseque
12 matches
Mail list logo
