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 pablogsal
Recipients barry, brett.cannon, docs@python, grantjenks, gregory.p.smith, ncoghlan, p-ganssle, pablogsal, rhettinger, tim.peters, vstinner, willingc
Date 2019-06-04.18:03:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559671422.98.0.374316766581.issue37134@roundup.psfhosted.org>
In-reply-to
Content
Thank you Carol for your comment! Regarding your proposal, I find it it attractive as a compromise in order to make more gentle the introduction of the feature to users. I really appreciate the effort to balance all the different aspects and concerns.

Ccould 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:

>I think documenting the trailing "/" is especially important because now users will find very confusing the fact that functions
only document the "/" in some places. They may start to believe that a trailing "/" is illegal syntax or that the "/" at the end
is optional. This will lead to even more confusion IMHO.

Another minor concern that I have is the fear that we will have a similar discussion in the future when the PR adding the trailing / to 3.9 would be added.
History
Date User Action Args
2019-06-04 18:03:43pablogsalsetrecipients: + pablogsal, tim.peters, barry, brett.cannon, rhettinger, gregory.p.smith, ncoghlan, vstinner, docs@python, willingc, p-ganssle, grantjenks
2019-06-04 18:03:42pablogsalsetmessageid: <1559671422.98.0.374316766581.issue37134@roundup.psfhosted.org>
2019-06-04 18:03:42pablogsallinkissue37134 messages
2019-06-04 18:03:42pablogsalcreate