Thanks, it's really useful to document this! This looks pretty good.

Could you maybe start the section with a brief description of why you might or might not want to use this option? I worry that at the moment, people new to Python might think that this is the best option that they should use all the time (since "optimized" is a very positive adjective!)

Maybe the section could start with something like this?

If you are trying to improve the performance of Python, you will probably want to use an optimized build of CPython. It can take a lot longer to build CPython with optimizations enabled, and it's usually not necessary to do so. However, it's essential if you want accurate benchmark results for a proposed performance optimization.

Could you also please wrap each line to 80 characters, like the other paragraphs in this document?

@KilJaeeun

Would you like to update the PR with comments from other reviewers?

• #1153 (review)
• https://github.com/python/devguide/pull/1153/files#r1291623444

Thanks, nearly there! A few more small suggestions below. If you like my suggestions, you can apply them by clicking the "commit suggestion" button below each suggestion :)

Depending on how much detail you want to go into, you could link the specific options themselves with :option`python:--enable-optimizations` or :option`python:--with-lto`.

Related, I was a little surprised to see configure options in d.p.o -- thinking about it, should we consider moving it to the devguide? I'm not sure many end-users build their own Python from sources...

A

Thanks, looks great!

Looks good overall! Thanks @KilJaeeun and again congratulations on your first PR!

A