I could not find Build Applet mentioned on distributing-python-applications-on-the-mac. It seems that is has been removed.

The document of Build Applet on Using Python on a Macintosh should be another issue. I will create a new issue for it if i could find something about it.

@MakDon, thanks for the PRs and for noticing the spurious reference to Build Applet, a tool that was removed in Python 3. The whole "Using Python on a Macintosh" chapter has not been updated in a long time and is woefully out-of-date. Despite good intentions, I have not yet gotten around to doing it but I will do so shortly - really. I'm going to push the PRs you have already made but I would ask you to hold off on making further changes as major rewrites are necessary. Thanks!

A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

I have made the requested changes; please review again.
Thanks bot :D

Thanks for making the requested changes!

@ned-deily: please review the changes made to this pull request.

It looks like your newer PR, #13966, effectively replaces this PR so I"m just going to close this one and merge the other. Thanks!

@ned-deily hummm, the problem is, the folder name in 2.7, 3.5, 3.6 is wrong so i create this pr for the folder name.

But it seems that it would be conflict if backport directly. Is it the best way is create PR for each version?

For

I would ask you to hold off on making further changes as major rewrites are necessary.

i would not create new PR the the floder name issue. Thanks for your review! :D

But it seems that it would be conflict if backport directly. Is it the best way is create PR for each version?

The change in this case is a bit unusual in that the changed lines include the version number in them so an automated backport is not possible and someone, either the PR submitter or the core developer merging the original PR, would need to manually create the backports. In general, it's best to just produce the PR for the master branch and then once it has been reviewed and accepted then produce any needed backport PRs if the core developer hasn't already done so.

But it seems that it would be conflict if backport directly. Is it the best way is create PR for each version?

The change in this case is a bit unusual in that the changed lines include the version number in them so an automated backport is not possible and someone, either the PR submitter or the core developer merging the original PR, would need to manually create the backports. In general, it's best to just produce the PR for the master branch and then once it has been reviewed and accepted then produce any needed backport PRs if the core developer hasn't already done so.

Thanks for your description. :D