[issue37044] Build/test artifacts not ignored for framework build

Ned Deily added the comment: 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

[issue37044] Build/test artifacts not ignored for framework build

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37044] Build/test artifacts not ignored for framework build

New submission from Jason R. Coombs : 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