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 willingc
Recipients barry, brett.cannon, bskinn, docs@python, grantjenks, gregory.p.smith, ncoghlan, p-ganssle, pablogsal, rhettinger, tim.peters, vstinner, willingc
Date 2019-06-04.21:01:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559682081.77.0.399531463004.issue37134@roundup.psfhosted.org>
In-reply-to
Content
> Could you extend your thoughts regarding this concern that I have with respect of not including the trailing / in 3.8 but doing it in 3.9:

Pablo, Sure thing. I believe that a Sphinx extension (possibly existing sphinx-tabs as suggested by @bskinn in the Steering Council issue or one we develop/find) could give us both a "technically accurate" view and "simplified" view. I wasn't sure if this could/would be ready by 3.8. But I think that it is feasible for 3.9. If we can do it for 3.8, fantastic.

If we do the 3.8/3.9 phased approach, I definitely think the 3.8 docs need to be explicit in stating the what/why/when of the / (still searching for a cute name - right now the best I have is "twig" from another name, virgule, for slash and its Latin derivation). Ultimately, 3.9 should either by Sphinx extension or edit contain the "technically accurate" version.
History
Date User Action Args
2019-06-04 21:01:21willingcsetrecipients: + willingc, tim.peters, barry, brett.cannon, rhettinger, gregory.p.smith, ncoghlan, vstinner, docs@python, bskinn, p-ganssle, pablogsal, grantjenks
2019-06-04 21:01:21willingcsetmessageid: <1559682081.77.0.399531463004.issue37134@roundup.psfhosted.org>
2019-06-04 21:01:21willingclinkissue37134 messages
2019-06-04 21:01:21willingccreate