[issue44537] Document PGO in devguide

[Guido van Rossum]

Guido van Rossum  added the comment:

Hm, there is now also info on how to build in the end user documentation in 
Doc/using/configure.rst. I am actually confused by the intention of documenting 
information about *building* CPython in the same place where we document 
*using* Python (and sometimes CPython), esp. given that we have a devguide. 
Maybe one of the docs owners can clarify where they thing PGO should be 
documented, and why?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue44537] Document PGO in devguide

[Guido van Rossum]

New submission from Guido van Rossum :

The only docs for PGO seem to be in the toplevel README.rst. Sinec that is 
what's shown to all visitors to the GitHub repo, perhaps this information is 
not so useful there, and instead a section could be added to the devguide? 
(Ditto for LTO.)

Note that for Windows this info is in PCbuild/readme.txt. It's perhaps okay to 
keep it there, and just mention in the devguide that the Windows info in there.

FWIW, maybe we should get rid of the tradition that the toplevel README.rst 
file's heading gives the version? That tradition dates from the times when 
source distributions were done as tarballs... It would save one more place to 
update (there's another mention of the version later in README.rst which still 
points to 3.10).

--
assignee: docs@python
components: Documentation
messages: 396764
nosy: docs@python, gvanrossum
priority: normal
severity: normal
status: open
title: Document PGO in devguide
versions: Python 3.11

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com