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 lemburg
Recipients brett.cannon, corona10, eric.snow, lemburg
Date 2021-10-20.14:38:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <6986df3a-f5cf-786c-6483-20440d7311b2@egenix.com>
In-reply-to <CALFfu7COWtRcKv-_rKDbb8MOpA0__0MWti5dLXF3macrN1Vb8w@mail.gmail.com>
Content
On 20.10.2021 16:25, Eric Snow wrote:
> 
> Eric Snow <ericsnowcurrently@gmail.com> added the comment:
> 
> On Wed, Oct 20, 2021 at 6:01 AM Marc-Andre Lemburg
> <report@bugs.python.org> wrote:
>> I have PyRun mostly working with Python 3.9.
>> ...
>> No changes were necessary to Tools/freeze/.
> 
> Great!  Thanks for getting to that so quickly.  Are you going to take
> a look at 3.10 after you're happy with 3.9?

Yes, 3.10 is next, once I have 3.9 ironed out. And then I'll give
3.11 a try.

>> BTW: Why is test_embed even used for the PGO target ?
> 
> Perhaps I've missed something, but I'm not clear on why PGO would be a
> problem for test_embed.  Are you talking about a specific test in
> test_embed?

Sorry, I wasn't clear. PGO is not a problem for test_embed. I just
wonder why the test_embed tests are run for creating the PGO profile
files. test_embed is far from being a regular work load for Python
applications.

Well, I guess using the test suite for PGO is questionable anyway.
It's just that we don't have anything else handy to create those
profiles at Python build time :-)
History
Date User Action Args
2021-10-20 14:38:02lemburgsetrecipients: + lemburg, brett.cannon, eric.snow, corona10
2021-10-20 14:38:02lemburglinkissue45395 messages
2021-10-20 14:38:02lemburgcreate