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 jaraco
Recipients jaraco, ned.deily, ronaldoussoren
Date 2019-05-25.13:58:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
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)


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?
Date User Action Args
2019-05-25 13:58:32jaracosetrecipients: + jaraco, ronaldoussoren, ned.deily
2019-05-25 13:58:32jaracosetmessageid: <>
2019-05-25 13:58:32jaracolinkissue37044 messages
2019-05-25 13:58:32jaracocreate