Re: [Python-Dev] Unicode 11.0.0 released
On Jun 6, 2018, at 00:22, Benjamin Peterson wrote: > On Tue, Jun 5, 2018, at 12:17, MRAB wrote: >> Unicode 11.0.0 has been released. Will Python 3.7 be updated to it, or >> is it too late? > > https://github.com/python/cpython/pull/7439 will update 3.8. Generally, we've > considered updating the Unicode database to be a feature and not backported > updates to bugfix branches. Thus, tradition would seem to exclude Unicode > 11.0.0 from landing so late in 3.7's release cycle. That said, the update is > highly unlikely to break anything. It's up to Ned. I'd hate for 3.7 to fall behind in the emoji race :) Seriously, there are some important additions that will, no doubt, appear in platforms over the lifetime of 3.7 and the risk is very low. Thanks for pinging about it. https://github.com/python/cpython/pull/7470 -- Ned Deily n...@python.org -- [] ___ 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/archive%40mail-archive.com
Re: [Python-Dev] Keeping an eye on Travis CI, AppVeyor and buildbots: revert on regression
On Wed, Jun 6, 2018 at 9:45 PM, Mariatta Wijaya wrote: > Are there APIs we can use to check the status of builbots? > Maybe we can have the our bots check for the buildbot status in backport > PRs. There is a REST API for buildbot; I have no idea how usable/useful it is though (but I think the new UI interacts with the master mostly via REST calls). I am planning to eventually get buildbot integration with GitHub set up, possibly in September. I think it should be possible to make only stable bots show up as status checks, or even just a select subset of the stable bots. -- Zach ___ 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/archive%40mail-archive.com
Re: [Python-Dev] Unicode 11.0.0 released
On 2018-06-07 08:40, Ned Deily wrote: On Jun 6, 2018, at 00:22, Benjamin Peterson wrote: > On Tue, Jun 5, 2018, at 12:17, MRAB wrote: >> Unicode 11.0.0 has been released. Will Python 3.7 be updated to it, or >> is it too late? > > https://github.com/python/cpython/pull/7439 will update 3.8. Generally, we've considered updating the Unicode database to be a feature and not backported updates to bugfix branches. Thus, tradition would seem to exclude Unicode 11.0.0 from landing so late in 3.7's release cycle. That said, the update is highly unlikely to break anything. It's up to Ned. I'd hate for 3.7 to fall behind in the emoji race :) The Python community _is_ meant to be inclusive, and we should support the addition of ginger emoijs. :-) Seriously, there are some important additions that will, no doubt, appear in platforms over the lifetime of 3.7 and the risk is very low. Thanks for pinging about it. https://github.com/python/cpython/pull/7470 ___ 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/archive%40mail-archive.com
Re: [Python-Dev] Microsoft to acquire GitHub for $7.5 b
> We shouldn't be uniquely or especially concerned just because > Microsoft has purchased Github. Nothing has changed. Exactly — but this change HAS made people think about an issue that we should have already been thinking about. At the end of the day, anyone, or any project, would be well served by having a plan for potential loss of valuable data. And the no brainer on that is : don’t have only one copy in one place. That’s why my family photos are on my hard drive, and a backup drive, and an online backup service. My house could burn down, so I don’t want everything there. The backup service could change its conditions, go out of business, or simply have a technical failure — so I don’t want everything there, either. Any service could change or fail. Period. So we shouldn’t want valuable information about Python development only in gitHub. I don’t know how hard it is to backup / mirror an entire repo — but it sure seems like a good idea. -CHB ___ 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/archive%40mail-archive.com
Re: [Python-Dev] Microsoft to acquire GitHub for $7.5 b
On Fri, Jun 8, 2018 at 3:33 AM, Chris Barker - NOAA Federal via Python-Dev wrote: > Any service could change or fail. Period. > > So we shouldn’t want valuable information about Python development > only in gitHub. > > I don’t know how hard it is to backup / mirror an entire repo — but it > sure seems like a good idea. There are two separate concerns here: 1) How do we get a full copy of all of CPython and its change history? 2) How do we get all the non-code content - issues, pull requests, comments? The first one is trivially easy. *Everyone* who has a clone of the repository [1] has a full copy of the code and all history, updated every time 'git pull' is run. The second one depends on GitHub's exporting facilities; but it also depends on a definition of what's important. Maybe the PSF doesn't care if people's comments at the bottoms of commits are lost (not to be confused with commit messages themselves, which are part of the repo proper), so it wouldn't matter if they're lost. Or maybe it's important to have the contents of such commits, but it's okay to credit them to an email address rather than linking to an actual username. Or whatever. Unlike with the code/history repo, an imperfect export is still of partial value. ChrisA [1] Barring shallow clones, but most people don't do those ___ 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/archive%40mail-archive.com
