Pull Windows dependencies from GitHub rather than svn.python.org

[zware]

BPO	30450
Nosy	@pfmoore, @pitrou, @vstinner, @tjguk, @benjaminp, @jkloth, @zware, @zooba, @ammaraskar
PRs	bpo-30450: Pull Windows dependencies from GitHub rather than svn #1783 bpo-30450: Add NEWS and whatsnew #2236 [3.6] bpo-30450: Pull Windows dependencies from GitHub rather than svn (GH-1783) #2237 bpo-30450: Adds alternate download approach for nuget.exe #2737 bpo-30450: Fall back to git.exe if no Python is found. #2739 bpo-30450: Fix logic for retrying nuget.exe download #2744 [3.6] bpo-30450: Improved logic for obtaining dependencies #2751 [2.7] bpo-30450: Pull Windows dependencies from GitHub rather than SVN (GH-1783) #3306 [2.7] bpo-30450: Don't use where, it doesn't exist on XP #3330 bpo-30450: Don't use where, XP doesn't have it #3348 [2.7] bpo-30450: Fall back on the old env.bat #3443

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/zooba'
closed_at = <Date 2017-12-06.21:14:23.747>
created_at = <Date 2017-05-24.01:33:46.861>
labels = ['extension-modules', 'build', '3.7', 'OS-windows', 'performance']
title = 'Pull Windows dependencies from GitHub rather than svn.python.org'
updated_at = <Date 2017-12-06.22:28:17.743>
user = 'https://github.com/zware'

bugs.python.org fields:

activity = <Date 2017-12-06.22:28:17.743>
actor = 'vstinner'
assignee = 'steve.dower'
closed = True
closed_date = <Date 2017-12-06.21:14:23.747>
closer = 'zach.ware'
components = ['Build', 'Extension Modules', 'Windows']
creation = <Date 2017-05-24.01:33:46.861>
creator = 'zach.ware'
dependencies = []
files = []
hgrepos = []
issue_num = 30450
keywords = ['patch']
message_count = 52.0
messages = ['294307', '294359', '294441', '294494', '294533', '294534', '295240', '296150', '296157', '296160', '296351', '296365', '296805', '298469', '298471', '298476', '298497', '298498', '298501', '298504', '298505', '298506', '298507', '298508', '298509', '298512', '298513', '298516', '298517', '298518', '298519', '298520', '298522', '298523', '298526', '298552', '298557', '298559', '298560', '298608', '298609', '298640', '299803', '299809', '301279', '301327', '301328', '301365', '301712', '301966', '307769', '307772']
nosy_count = 11.0
nosy_names = ['paul.moore', 'pitrou', 'vstinner', 'tim.golden', 'benjamin.peterson', 'jkloth', 'jeremy.kloth', 'zach.ware', 'steve.dower', 'ammar2', 'schen']
pr_nums = ['1783', '2236', '2237', '2737', '2739', '2744', '2751', '3306', '3330', '3348', '3443']
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'resource usage'
url = 'https://bugs.python.org/issue30450'
versions = ['Python 2.7', 'Python 3.5', 'Python 3.6', 'Python 3.7']

[zware]

Once we've migrated away from svn.python.org for Windows build dependencies, there should be no reason to continue running svn.python.org.

[zooba]

The reason to keep it running is for all the existing people who are building from source. Unless you're porting all the old versions over and providing instructions for updating old sources? I wouldn't bother - just leave the server up for a few more years.

Ben probably knows - can we add a custom message to svn requests? Then we could start publicising an end of life date for it.

[benjaminp]

The box svn is running on is at risk of falling over any day. Plus with whatever ancient software it's running, it's surely a security risk to keep running an unmaintained svn instance. I certainly don't want to keep it running for years. I don't think we've ever advertised the svn windows deps as a service we provide the community.

Off the top of my head, I'm not sure how to announce that deprecation to svn client users. If you find something on the internets, I can put it on the server.

[zooba]

I don't think we've ever advertised the svn windows deps as a service we provide the community.

Except in the dev guide :) ([after looking] well, linked from the dev guide https://github.com/python/cpython/blob/master/PCbuild/readme.txt#L230 )

Maybe we just need to pick a date and publicise it separately. Is this process PEP-worthy? Considering the amount of decisions we had to make regarding putting code in git, it might be worth writing up how it works in a brief PEP and including an EOL for svn.p.o

[benjaminp]

How far along are you with removing the svn.python.org dependency. Does Jan 1 2018 sound okay for the end of svn.python.org?

I think a PEP is up to you. Doesn't seem like something that needs to be approved.

[pitrou]

I could imagine people wanting to build old releases. But we have Windows binaries up here:
https://www.python.org/ftp/python/

Therefore I don't think it's a problem to discontinue svn.python.org once new releases are migrated to github (but only once those new releases are out).

[benjaminp]

I just disabled viewvc on svn.python.org because of a security problem.

[zware]

New changeset 51599e2 by Zachary Ware in branch 'master':
bpo-30450: Pull Windows dependencies from GitHub rather than svn (GH-1783)
51599e2

[zware]

New changeset cb8c048 by Zachary Ware in branch 'master':
bpo-30450: Add NEWS and whatsnew (GH-2236)
cb8c048