devinabox has moved to GitHub
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 repository. I have also turned on the CLA bot for the repository (FYI https://github.com/python/the-knights-who-say-ni has that bot's code). I've asked Georg, Antoine, and Benjamin to tell me what I need to do to shut off -- either by making it read-only or just deleting -- hg.python.org/devinabox. Now that the migration has seriously begun, the next repos will be the peps and devguide (slightly more complicated thanks to needing to update commands for building their online versions). There's also the benchmarks repo, but that might not get migrated if we start from scratch (see the speed@ ML about that). As for cpython, I've been asked to talk about it at the language summit where I will start a conversation about what the minimal feature set will need to be to migrate. Once we have settled on what has to be in place to migrate the cpython repo then we can start working on that TODO list.
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 Windows users, ask them to download and install Visual Studio Community edition ahead of time." On Sun, May 8, 2016 at 4:41 PM, Brett Cannon <brett@python.org> wrote:
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 repository. I have also turned on the CLA bot for the repository (FYI https://github.com/python/the-knights-who-say-ni has that bot's code).
I've asked Georg, Antoine, and Benjamin to tell me what I need to do to shut off -- either by making it read-only or just deleting -- hg.python.org/devinabox.
Now that the migration has seriously begun, the next repos will be the peps and devguide (slightly more complicated thanks to needing to update commands for building their online versions). There's also the benchmarks repo, but that might not get migrated if we start from scratch (see the speed@ ML about that).
As for cpython, I've been asked to talk about it at the language summit where I will start a conversation about what the minimal feature set will need to be to migrate. Once we have settled on what has to be in place to migrate the cpython repo then we can start working on that TODO list.
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/leewangzhong%2Bpython%40g...
On Wed, 25 May 2016 at 10:24 Franklin? Lee <leewangzhong+python@gmail.com> 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 + clang as this provides better error reporting than gcc." "For Windows users, ask them to download and install Visual Studio Community edition ahead of time."
If you want to submit a PR to say "the latest" that's fine, but I don't know if any of those tools really promote downloading older versions such that one has to worry about it.
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 repository. I have also turned on the CLA bot for the repository (FYI https://github.com/python/the-knights-who-say-ni has that bot's code).
I've asked Georg, Antoine, and Benjamin to tell me what I need to do to shut off -- either by making it read-only or just deleting -- hg.python.org/devinabox.
Now that the migration has seriously begun, the next repos will be the
On Sun, May 8, 2016 at 4:41 PM, Brett Cannon <brett@python.org> wrote: peps
and devguide (slightly more complicated thanks to needing to update commands for building their online versions). There's also the benchmarks repo, but that might not get migrated if we start from scratch (see the speed@ ML about that).
As for cpython, I've been asked to talk about it at the language summit where I will start a conversation about what the minimal feature set will need to be to migrate. Once we have settled on what has to be in place to migrate the cpython repo then we can start working on that TODO list.
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe:
https://mail.python.org/mailman/options/python-dev/leewangzhong%2Bpython%40g...
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 <brett@python.org> wrote:
On Wed, 25 May 2016 at 10:24 Franklin? Lee <leewangzhong+python@gmail.com> 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 + clang as this provides better error reporting than gcc." "For Windows users, ask them to download and install Visual Studio Community edition ahead of time."
If you want to submit a PR to say "the latest" that's fine, but I don't know if any of those tools really promote downloading older versions such that one has to worry about it.
On Sun, May 8, 2016 at 4:41 PM, Brett Cannon <brett@python.org> wrote:
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 repository. I have also turned on the CLA bot for the repository (FYI https://github.com/python/the-knights-who-say-ni has that bot's code).
I've asked Georg, Antoine, and Benjamin to tell me what I need to do to shut off -- either by making it read-only or just deleting -- hg.python.org/devinabox.
Now that the migration has seriously begun, the next repos will be the peps and devguide (slightly more complicated thanks to needing to update commands for building their online versions). There's also the benchmarks repo, but that might not get migrated if we start from scratch (see the speed@ ML about that).
As for cpython, I've been asked to talk about it at the language summit where I will start a conversation about what the minimal feature set will need to be to migrate. Once we have settled on what has to be in place to migrate the cpython repo then we can start working on that TODO list.
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe:
https://mail.python.org/mailman/options/python-dev/leewangzhong%2Bpython%40g...
On 26 May 2016 at 04:54, Franklin? Lee <leewangzhong+python@gmail.com> 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 older Python versions (since you need to make sure the binaries are compatible), but that's not a topic devinabox concerns itself with. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
participants (3)
-
Brett Cannon -
Franklin? Lee -
Nick Coghlan