Hello!
This PR needs to add:

1. A NEWS entry
2. A whatsnew entry
3. A new paragraph in the Doc/cmdline for the -X option.
4. New test case in the Lib/test/test_cmd_line

Hello! This PR needs to add:

1. A NEWS entry
2. A whatsnew entry
3. A new paragraph in the Doc/cmdline for the -X option.
4. New test case in the Lib/test/test_cmd_line

Thanks for the quick feedback. I've committed a first pass of 1-3. As for tests: there appear to be no importtime tests (likely due to the fact that any simple implementation would be super noisy as other parts of the interpreter change). Would it be sufficient to do some rudimentary check i.e. import foo then ensure a corresponding foo row appears in the output?

Thanks again!

Hello! This PR needs to add:

1. A NEWS entry
2. A whatsnew entry
3. A new paragraph in the Doc/cmdline for the -X option.
4. New test case in the Lib/test/test_cmd_line

Thanks for the quick feedback. I've committed a first pass of 1-3. As for tests: there appear to be no importtime tests (likely due to the fact that any simple implementation would be super noisy as other parts of the interpreter change). Would it be sufficient to do some rudimentary check i.e. import foo then ensure a corresponding foo row appears in the output?

Thanks again!

Yes, it would be sufficient :)

Also, there's a merge conflict. Can you resolve it? (I can do it myself, but it seems like you have turned off this option)

Also, there's a merge conflict. Can you resolve it? (I can do it myself, but it seems like you have turned off this option)

Done, just added tests as well

@Eclips4 who should I ping to get final review? Is it alright if I @ the blamed reviewers?

@Eclips4 who should I ping to get final review? Is it alright if I @ the blamed reviewers?

I guess @vstinner is the right person to review this 😄
However, you should move your changes from whatsnew/3.13.rst to whatsnew/3.14.rst since 3.13 branch is in feature-freeze mode, and this feature will appear only in the 3.14 version.

However, you should move your changes from whatsnew/3.13.rst to whatsnew/3.14.rst since 3.13 branch is in feature-freeze mode, and this feature will appear only in the 3.14 version.

The same applies for the versionchanged directives.

All commit authors signed the Contributor License Agreement.

Apologies for the noise, I had to amend some of the commits with the correct email to pick up the right CLA.

Pinging @serhiy-storchaka for re-review; I intend to leave the mypy errors as-is because this import try/except mechanism is already used elsewhere in the stdlib.

LGTM! Before merging, we need to know @pablogsal and @ambv opinion on change in Lib/_pyrepl/unix_console.py

Re-pinging for quick review!

@noahbkim Can you make the CI pass on Windows and macOS? the logs are no more available so I can't see what happened.

All checks except for mypy should pass. The issue reported by mypy is the following idiom

try:
    import posix
except ImportError:
    posix = None

Since this is used pretty widely throughout the standard library, I figured it should be left as is and the warning ignored. I could suppress the warning instead.

Update: woah, I lied, something has changed since my last push. I'll fix these failures today.

Since this is used pretty widely throughout the standard library, I figured it should be left as is and the warning ignored. I could suppress the warning instead.

You can mypy-ignore it I think. Otherwise, future modifications in that file would also be flagged, right?

All commit authors signed the Contributor License Agreement.

@AA-Turner merged your changes, happy to do anything else necessary, apologies for the inconvenience of the organization branch. Not sure where your comment went (I saw it in my email), but thanks for helping push this through.

Thanks @noahbkim, no worries! Are you able to make the changes to config_set_import_time etc to reserve values >=2?

We also recently changed our CLA bot, please can you click on the red 'not signed' and ensure everything is up to date?

A

I think I've messed up my branch, I'm going to attempt to squash everything so I can overwrite my commit email correctly.

Ok, please ping for a review when you've sorted the branch out! If it's easier, feel free to just open a new PR, but a force push here should also work.

A

@AA-Turner I've squashed my changes and given everything a second pass.

It looks like I caused some kind of regression in test_embed.py, but none of the expected invariants make sense to me (I'm not sure why we expect import_time to be set to 1 in any of the listed circumstances). Looking through the blame was not particularly illuminating. My suspicion is that these tests have been migrated/updated several times without regard for what they're actually testing (or perhaps implicit behavior surrounding -Ximporttime has changed since the test suite's addition?).

Zeroing import_time in said cases returns everything to passing, but a second pair of eyes on that particular bit would be greatly appreciated.

I have about 6 tests failing locally, one of which prevents me from compiling with --enable-optimizations (test_json) but I can't imagine those are related. I'll check if my merge base is behind + fix the CI lint issue.