Could not install packages due to an environmenterror


SUBMITTED BY: Guest

DATE: Jan. 27, 2019, 11:23 p.m.

FORMAT: Text only

SIZE: 4.1 kB

HITS: 257

  1. Could not install packages due to an environmenterror
  2. => http://poupamchandthe.nnmcloud.ru/d?s=YToyOntzOjc6InJlZmVyZXIiO3M6MjE6Imh0dHA6Ly9iaXRiaW4uaXQyX2RsLyI7czozOiJrZXkiO3M6NTM6IkNvdWxkIG5vdCBpbnN0YWxsIHBhY2thZ2VzIGR1ZSB0byBhbiBlbnZpcm9ubWVudGVycm9yIjt9
  3. This doesn't occur for Python 3. If this exists you will not be able to modify any files via Kudu.
  4. I've tried googling parts of the error but I cannot find anything related to fixing this. Have a question about this project?
  5. I'm -1 on the various workarounds you suggest. In regards to the permission issue, I was told that it wasn't wise to change the permissions in the System folder. This puts your application files into a read only mode. Similarly, for other Python versions, installing with pip install --no-binary :all: numpy into a path with spaces in it, e. There seem to be a plethora of virtual environment related packages and commands, and I get stuck a couple of commands into it. Just thought if anyone runs into this, that would be a quicker way to get to it. In fact, the last 6 lines of this error, something about incompatibility issues, repeat for every pip3 install command. When viewing verbose logs with pip, the full traceback is: Could not install packages due to an EnvironmentError. Just to clarify, are you an admin on the subscription? Does fix the issue at least in cases where the user hasn't overridden the default style? And if you will install tensorflow according to my answer, it will help you have better boundaries for different versions of tensorflow on a single machine.
  6. Could not install packages due to an EnvironmentError: [Errno 13] Permission denied · Issue #1849 · Microsoft/vscode - That's why I started using Node. When viewing verbose logs with pip, the full traceback is: Could not install packages due to an EnvironmentError.
  7. Have a question about this project. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Description pip throws an exception when trying to display a progress bar for the download of any package on Windows. Expected behavior pip should work and install the package correctly. How to Reproduce Note that this is environment dependent. Analysis The following seems to succeed, while later attempts to actually write the characters to the console fail. There is which could be used to get similar support for Python 2. But the check should probably be fixed anyhow. The second exception is an entirely different bug. This happens when you use --no-cache-dir. Not sure if reported, if not, then a separate issue needs to be opened for that. Anyhow, this doesn't happen when you just print the Unicode character, in fact it works in the Python interpreter. It seems to be triggered by calling locale. Later I found this describing this:. This makes the check for the characters use the correct encoding. Actually writing anything will still use the wrong encoding of course We can also just skip the check and use ascii always if this condition holds if sys. If so, I don't see that there's any point in pip trying to work around it. Does fix the issue at least could not install packages due to an environmenterror cases where the user hasn't overridden the default style. If so, that seems to be a sufficient workaround. I'm -1 on the various workarounds you suggest. In my opinion, It's a core issue in the way Python 2. I kinda opened the issue for documentation purposes So that people can find it and get linked to workaroundsI doubted anyone would want to make any changes to encodings in Python 2. Let alone a potentially non-backwards compatible fix. It will still be a required to use it manually, and placing it in a config file will have it take effect for Python 3 too, which the user likely doesn't want. Without implementing a workaround, pip will be broken by default for many new users on Python 2. Things should really work out of the box. Users shouldn't need to apply workarounds themselves to get things to work with supported Python versions.

comments powered by Disqus