Vladimir Feinberg added the comment:
Mark, I will say I'm pretty sympathetic to the feature-bloat avoidance
perspective here, and if the outcome here is to improve docs, that's still
a win, I think.
That said, since this thread will become precedent, and I think
`math.ceildiv` is the exactly
New submission from Vladimir Feinberg :
I have a request related to the rejected proposal
(https://bugs.python.org/issue43255) to introduce a ceildiv operator.
I frequently find myself wishing for a ceildiv function which computes
`ceil(x/y)` for integers `x,y`. This comes up all the time
Change by Vladimir Feinberg :
--
keywords: +patch
pull_requests: +23256
stage: resolved -> patch review
pull_request: https://github.com/python/cpython/pull/24460
___
Python tracker
<https://bugs.python.org/issu
Vladimir Feinberg added the comment:
Yep, you're right. I'd be happy to (but I've never done it before, so
please give me some time).
On Tue, Feb 2, 2021 at 12:35 AM Irit Katriel wrote:
>
> Irit Katriel added the comment:
>
> It should truncate at the call that raised the rec
Vladimir Feinberg added the comment:
Oh, yes, I suppose, that'll truncate to just the first TracebackException.
On Mon, Feb 1, 2021 at 4:38 PM Irit Katriel wrote:
>
> Irit Katriel added the comment:
>
> I meant to catch the exception in the constructor’s recursive call, and if
Vladimir Feinberg added the comment:
A simple catch may not work (the very first TracebackException is the one
that gets the RecursionError during initialization of its __context__), but
one thing I was thinking about was walking the __context__ pointers and
nulling out anything past
Vladimir Feinberg added the comment:
I agree with both the duplicate classification and am glad the fix works in
3.10. Thanks all for the responses.
Given the issue can be triggered with a fairly benign setup (pandas triggers
such an error, and logger.exception is idiomatic), I do think
New submission from Vladimir Feinberg :
Python's standard logger provides an exception() method, which is to be called
from except blocks to log out exception traces by pulling from sys.exc_info().
Per https://github.com/python/cpython/blob/3.9/Lib/logging/__init__.py#L617 ,
logger.exception
Vladimir Feinberg added the comment:
I'm still hitting this issue in Python 3.6.0 :: Anaconda 4.3.0 (64-bit). Is
there a reason this patch has been ignored?
This is on CentOS release 6.5
--
nosy: +Vladimir Feinberg
versions: +Python 3.6 -Python 2.7, Python 3.3
Added file: http
