On 5/10/2021 6:07 AM, Steven D'Aprano wrote:
On Mon, May 10, 2021 at 05:34:12AM -0400, Terry Reedy wrote:
On 5/10/2021 3:28 AM, M.-A. Lemburg wrote:
I'm mostly thinking of tracebacks which go >10 levels deep, which is
rather common in larger applications. For those tracebacks, the top
entries
Hi everyone,
Now that we are in the beta period for 3.10 is very important that we make
sure that all
improvements, new APIs and deprecations are reflected in the 3.10 what's
New document.
IMPORTANT!!
If you have worked on:
* Make a PEP that affects Python 3.10.
* A new
Hello Kyle,
I don't personally know you but I am glad you are on the recovery side.
Regards
Karim
Le lun. 10 mai 2021 à 09:20, Kyle Stanley a écrit :
> Hey all,
>
> In these last few months, I have been in the process of healing from some
> pretty heavy past trauma. And now that I am on the
I opened a new thread here:
https://mail.python.org/archives/list/python-id...@python.org/thread/WQOMBT4Z22EIFB53WN54E52AYS3QBKAV/
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
Hey all,
In these last few months, I have been in the process of healing from some
pretty heavy past trauma. And now that I am on the road to recovery, I want
to share my journey with the Python community in hopes that it may reach
those that are struggling with their own mental health battles,
On Tue, 23 Mar 2021 at 21:39, Python Steering Council
wrote:
>
> This isn’t happening because GitHub/Microsoft made a political decision. It’s
> happening because it is incredibly easy to make this move, many projects have
> already done this, and it reflects badly on any project not making
That is going to be very hard to read, unfortunately. Especially when the
line is
not simple. Highlighting the range is quite a fundamental part of the
proposal and
is driven by the great welcoming of highlighting ranges for syntax errors,
which many
users have reached to say that they find it
Another alternative is instead of
File blah.py line 3:
return x/0
^^^
to have
File blah.py line 3 cols 12-14:
x/0
On Mon, May 10, 2021 at 11:12 AM Steven D'Aprano
wrote:
> On Mon, May 10, 2021 at 05:34:12AM -0400, Terry Reedy wrote:
> > On 5/10/2021 3:28 AM,
On Mon, May 10, 2021 at 05:34:12AM -0400, Terry Reedy wrote:
> On 5/10/2021 3:28 AM, M.-A. Lemburg wrote:
>
> >I'm mostly thinking of tracebacks which go >10 levels deep, which is
> >rather common in larger applications. For those tracebacks, the top
> >entries are mostly noise you never look at
On 5/10/2021 3:28 AM, M.-A. Lemburg wrote:
I'm mostly thinking of tracebacks which go >10 levels deep, which is
rather common in larger applications. For those tracebacks, the top
entries are mostly noise you never look at when debugging. The proposal
now adds another 10 extra lines to jump
Hi, folks.
Now Python 3.11 development is open and I am removing some deprecated
stuffs carefully.
I am considering `configparser.ParseError.filename` property that is
deprecated since Python 3.2.
On Mon, 10 May 2021 at 08:34, M.-A. Lemburg wrote:
> [...]
PS: It looks like the discussion has wondered off to Discourse
> now. Should we continue there ?
>
> --
> Marc-Andre Lemburg
> eGenix.com
>
Pablo seems to want to redirect the discussion there yes, in particular to:
On 09.05.2021 14:22, Larry Hastings wrote:
> On 5/9/21 3:00 AM, M.-A. Lemburg wrote:
>> BTW: For better readability, I'd also not output the lines
>> for every stack level in the traceback, but just the last one,
>> since it's usually clear where the call to the next stack
>> level happens in
13 matches
Mail list logo
