When developing on macOS, after some build/test operations (I'm not sure exactly which, but seemingly relating to a framework build), artifacts are generated which aren't ignored. As a result, it's easy for them to leak into a merge request as they did with GH-12547 (issue34632).

For example:

```
cpython master $ ./configure --enable-framework=/Users/jaraco/Library/Frameworks && make
...
cpython master $ git status                                                                                                                                                    
On branch master
Your branch is up to date with 'origin/master'.

Untracked files:
  (use "git add <file>..." to include in what will be committed)

        Mac/Resources/app/Info.plist
        Mac/Resources/framework/Info.plist
        Python.framework/Python
        Python.framework/Versions/

nothing added to commit but untracked files present (use "git add" to track)
```

(also Python.framework/Resources/, except that's in the repo at the moment, the reason for reporting this issue)

Is there not a reason to ignore these artifacts so they don't risk being added to the commit?

That seems like a reasonable request.  We should also check that the Makfile clean* rules do the right thing.  One potential complication: the framework name is specified by the ./configure --with-framework-name= parameter, so it may not always be "Python.framework", the default value.