Re: [Python-Dev] devinabox has moved to GitHub

2016-05-25 Thread Nick Coghlan
On 26 May 2016 at 04:54, Franklin? Lee wrote: > It's just that I don't know whether any of them require particular > versions. If you say the latest is fine, then okay. For working on CPython trunk, the latest is fine. Things only have the potential to get trickier when building extensions for ol

Re: [Python-Dev] devinabox has moved to GitHub

2016-05-25 Thread Franklin? Lee
It's just that I don't know whether any of them require particular versions. If you say the latest is fine, then okay. On Wed, May 25, 2016 at 1:37 PM, Brett Cannon wrote: > > > On Wed, 25 May 2016 at 10:24 Franklin? Lee > wrote: >> >> Should these notes come with version requirements/minimums?

Re: [Python-Dev] devinabox has moved to GitHub

2016-05-25 Thread Brett Cannon
On Wed, 25 May 2016 at 10:24 Franklin? Lee wrote: > Should these notes come with version requirements/minimums? > > "OS X users should be told to download XCode from the Apple App Store > ahead of time." > "If new contributors think they may be doing C development, suggest > the use of LLVM + cla

Re: [Python-Dev] devinabox has moved to GitHub

2016-05-25 Thread Franklin? Lee
Should these notes come with version requirements/minimums? "OS X users should be told to download XCode from the Apple App Store ahead of time." "If new contributors think they may be doing C development, suggest the use of LLVM + clang as this provides better error reporting than gcc." "For Wind

[Python-Dev] devinabox has moved to GitHub

2016-05-08 Thread Brett Cannon
https://github.com/python/devinabox The single issue for devinabox has moved to its own issue tracker, so there's no need to worry about those issues cluttering b.p.o in the future. I have made the Python core team I created on GitHub last week have write privileges and Nick and I as admins on the