K Richard Pixley <r...@noir.com> added the comment: I think a better solution that declaring it to be apple's bug would be to release one binary for pre-10.7, (or maybe 10.6 with the current xcode), and a different binary for post-10.7.
This isn't an apple "bug" in the sense that there's anything wrong nor in the sense that they would ever "fix" it. It's simply a difference between xcode versions. So the choices would seem to be a) code around it or b) release different binaries. I'm ok with either solution. I'm not sure what would be best as I'm not sure I know all of the concerns involved. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13590> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
