New submission from Jason R. Coombs <[email protected]>:
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?
----------
components: macOS
messages: 343479
nosy: jaraco, ned.deily, ronaldoussoren
priority: normal
severity: normal
status: open
title: Build/test artifacts not ignored for framework build
type: behavior
_______________________________________
Python tracker <[email protected]>
<https://bugs.python.org/issue37044>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
