It is an issue that borks your install. That seems like your issue which involves notepad++. You might want to talk with them about it or more likely since they've not fixed it in a while - develop a work around or at least a message that pops up and asks if they want it fixed so the install succeeds.
Likewise if you have an option to install for all uses, then it should work without further intervention. As for unfair, is this production software or is it a toy? If it is a toy, I withdraw my comment. -----Original Message----- From: zachary.w...@gmail.com [mailto:zachary.w...@gmail.com] On Behalf Of Zachary Ware Sent: Friday, December 11, 2015 10:17 AM To: python-list@python.org Cc: Jay Hamm <ha...@vmware.com> Subject: Re: python 351x64 On Fri, Dec 11, 2015 at 10:30 AM, Jay Hamm <ha...@vmware.com> wrote: > Hi > > I was trying to use your windows version of python 3.5.1 x64. > > It has a conflict with a notepad++ plugin NppFTP giving > api-ms-win-crt-runtime-I1-1-0.dll error on start up. > > This seems pretty well documented on the web. The work around is to delete > the plugin and reinstall since it borks the install. api-ms-win-crt-runtime-I1-1-0.dll is part of the Universal CRT; I don't see what the relation between Python and Notepad++ is. This sounds like an issue with Notepad++/NppFTP, not Python. > Since about every other admin I've ever known uses notepad++, you might want > to fix this. > > Also your installer fails to set the permissions correctly: > > H:\>py -m pip install requests > Collecting requests > Downloading requests-2.8.1-py2.py3-none-any.whl (497kB) > 100% |################################| 499kB 875kB/s Installing > collected packages: requests > Exception: > Traceback (most recent call last): > File "C:\Program Files\Python35\lib\site-packages\pip\basecommand.py", line > 211, in main status = self.run(options, args) > File "C:\Program Files\Python35\lib\site-packages\pip\commands\install.py", > line 311, in run root=options.root_path, > File "C:\Program Files\Python35\lib\site-packages\pip\req\req_set.py", line > 646, in install **kwargs > File "C:\Program Files\Python35\lib\site-packages\pip\req\req_install.py", > line 803, in install self.move_wheel_files(self.source_dir, root=root) > File "C:\Program Files\Python35\lib\site-packages\pip\req\req_install.py", > line 998, in move_wheel_files isolated=self.isolated, > File "C:\Program Files\Python35\lib\site-packages\pip\wheel.py", line 339, > in move_wheel_files clobber(source, lib_dir, True) > File "C:\Program Files\Python35\lib\site-packages\pip\wheel.py", line 310, > in clobber ensure_dir(destdir) > File "C:\Program Files\Python35\lib\site-packages\pip\utils\__init__.py", > line 71, in ensure_dir os.makedirs(path) > File "C:\Program Files\Python35\lib\os.py", line 241, in makedirs > mkdir(name, mode) PermissionError: [WinError 5] Access is denied: > 'C:\\Program Files\\Python35\\Lib\\site-packages\\requests' > > Once I gave myself control it started working. The point of installing in C:\Program Files\ is that non-admin users can't write there. If you want a package installed in the global site-packages, do it as an administrator or install Python somewhere else (like C:\Python35\ as previous versions did, but be aware of the security implications). Otherwise, create a local venv (`py -3.5 -m venv path\to\venv`), install your packages there, and use it. > This is pretty shoddy for released software. That seems uncalled for. -- Zach -- https://mail.python.org/mailman/listinfo/python-list
