On 23/09/2014 18:05, Steve Dower wrote: > I'm also considering/experimenting with installing into "Program > Files" by default, but I suspect that isn't going to work out yet. I'd like to see that go forward: I think it's increasingly difficult to justify Python's position at c:\pythonxx. But it does run the risk of breaking All The Things. When it was discussed, people spoke about symlinks (or hardlinks / junctions / whatever) in the appropriate places to support hardcoded paths, but I don't know how feasible that will turn out to be. > > I'd like to move the Windows versions onto the next release of VC > (currently "VC 14" until the branding team figures out what to call > it). There isn't a promised RTM date for VC 14 yet, so it looks like > the best available compiler by Beta 1 will be a "Go Live" RC. (The > "Go Live" marking basically means "we think this is ready for use, > but expect a round of minor updates/fixes soon - the compiler is > least likely to be updated, my guess is that it'll be Visual Studio > UI mostly). My only real misgiving here is that, for a few years, we'll need *three* versions installed to build the active branches: 2008 for 2.7; 2010 for 3.4; and 2014 for 3.5. Am I wrong? TJG
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4