Message201198
| Author | abarnert |
|---|---|
| Recipients | abarnert, ned.deily, python-dev, r.david.murray, rhettinger, ronaldoussoren, skip.montanaro |
| Date | 2013-10-25.00:05:40 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1382659540.53.0.465723841197.issue19019@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Now that Xcode 5 is out, and does not have anything named "gcc-4.2" (it _does_ still have something called "gcc", which is now a wrapper around clang instead of a wrapper around llvm-gcc-4.2), this seems a lot more critical, because (as far as I can tell) nobody with Xcode 5 can build C extensions for python.org Python installations. And that also implies that any changes need to be backported to 2.7 and 3.3, unless the plan is that only Python 3.4+ should work with Xcode 5. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013-10-25 00:05:40 | abarnert | set | recipients: + abarnert, skip.montanaro, rhettinger, ronaldoussoren, ned.deily, r.david.murray, python-dev |
| 2013-10-25 00:05:40 | abarnert | set | messageid: <1382659540.53.0.465723841197.issue19019@psf.upfronthosting.co.za> |
| 2013-10-25 00:05:40 | abarnert | link | issue19019 messages |
| 2013-10-25 00:05:40 | abarnert | create | |