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 nedbat
Recipients BTaskaya, Mark.Shannon, nedbat, pablogsal, rhettinger, serhiy.storchaka
Date 2020-12-22.22:42:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
This seems like a perspective that needs a wider audience.  PEP 626 says there will be no performance slowdown:

> Performance Implications
> In general, there should be no change in performance. When tracing,
> programs should run a little faster as the new table format can be
> designed with line number calculation speed in mind. Code with long
> sequences of pass statements will probably become a bit slower.

Now you are saying that is fine to take a small performance hit in order to conform to PEP 626.  

I am usually on the side of good tracing, but I imagine other people feel differently, that it is unacceptable to slow down all execution for sake of accurate tracing.  I would love to have a clear agreement before moving forward so that we don't have to backtrack.
Date User Action Args
2020-12-22 22:42:00nedbatsetrecipients: + nedbat, rhettinger, Mark.Shannon, serhiy.storchaka, pablogsal, BTaskaya
2020-12-22 22:42:00nedbatsetmessageid: <>
2020-12-22 22:42:00nedbatlinkissue42693 messages
2020-12-22 22:42:00nedbatcreate