> On Jan 5, 2015, at 3:13 AM, Paul Moore <p.f.mo...@gmail.com> wrote: > >> py.exe is more important than ever. It's still installed into the Windows >> directory for all-user installs, and into the Python directory for >> just-for-me. It's installed in a way that will make upgrades more reliable >> (so if you install 3.6 and then 3.5, you'll keep the newer launcher) and all >> the file associations go straight to the launcher. > > The biggest problem here is that py.exe doesn't help in the slightest > with script wrappers like pip.exe, virtualenv.exe, py.test.exe, > ipython.exe ... I've actually drifted away from using py.exe because > of this. Having just the interpreter special cased isn't really good > enough. (I know there's py -m pip, but it's not easy to get people to > use this...)
Won’t script wrappers use whatever version they were installs against? Or do you mean the “installed” version might be 3.5 for ``pip.exe`` even though there’s a 3.5.1 for ``pip.exe`` on the PATH? --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA _______________________________________________ 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
