Strange repeating sequence printed on console when installing packages through condos

My system specifications:

C: \ Users \ Lenovo> conda information Current installation:

platform : win-64 conda version : 4.3.8 conda is private : False conda-env version : 4.3.8 conda-build version : 1.21.3 python version : 3.5.2.final.0 requests version : 2.12.4 root environment : C:\Anaconda3 (writable) default environment : C:\Anaconda3 envs directories : C:\Anaconda3\envs package cache : C:\Anaconda3\pkgs channel URLs : https://repo.continuum.io/pkgs/free/win-64 https://repo.continuum.io/pkgs/free/noarch https://repo.continuum.io/pkgs/r/win-64 https://repo.continuum.io/pkgs/r/noarch https://repo.continuum.io/pkgs/pro/win-64 https://repo.continuum.io/pkgs/pro/noarch https://repo.continuum.io/pkgs/msys2/win-64 https://repo.continuum.io/pkgs/msys2/noarch config file : None offline mode : False user-agent : conda/4.3.8 requests/2.12.4 CPython/3.5.2 Windows/7 Windows/6.1.7601 

Recently, when after installing or updating packages through the conda, and sometimes even with a peak, the following sequence is displayed on the console :

 extern "Python": function Cryptography_locking_cb() called, but @ffi.def_extern( ) was not called in the current subinterpreter. Returning 0. extern "Python": function Cryptography_locking_cb() called, but @ffi.def_extern( ) was not called in the current subinterpreter. Returning 0. extern "Python": function Cryptography_locking_cb() called, but @ffi.def_extern( ) was not called in the current subinterpreter. Returning 0. extern "Python": function Cryptography_locking_cb() called, but @ffi.def_extern( ) was not called in the current subinterpreter. Returning 0. extern "Python": function Cryptography_locking_cb() called, but @ffi.def_extern( ) was not called in the current subinterpreter. Returning 0. extern "Python": function Cryptography_locking_cb() called, but @ffi.def_extern( ) was not called in the current subinterpreter. Returning 0. extern "Python": function Cryptography_locking_cb() called, but @ffi.def_extern( ) was not called in the current subinterpreter. Returning 0. extern "Python": function Cryptography_locking_cb() called, but @ffi.def_extern( ) was not called in the current subinterpreter. Returning 0. extern "Python": function Cryptography_locking_cb() called, but @ffi.def_extern( ) was not called in the current subinterpreter. Returning 0. extern "Python": function Cryptography_locking_cb() called, but @ffi.def_extern( ) was not called in the current subinterpreter. Returning 0. extern "Python": function Cryptography_locking_cb() called, but @ffi.def_extern( ) was not called in the current subinterpreter. Returning 0. extern "Python": function Cryptography_locking_cb() called, but @ffi.def_extern( ) was not called in the current subinterpreter. Returning 0. extern "Python": function Cryptography_locking_cb() called, but @ffi.def_extern( ) was not called in the current subinterpreter. Returning 0. extern "Python": function Cryptography_locking_cb() called, but @ffi.def_extern( ) was not called in the current subinterpreter. Returning 0. extern "Python": function Cryptography_locking_cb() called, but @ffi.def_extern( ) was not called in the current subinterpreter. Returning 0. extern "Python": function Cryptography_locking_cb() called, but @ffi.def_extern( ) was not called in the current subinterpreter. Returning 0. extern "Python": function Cryptography_locking_cb() called, but @ffi.def_extern( ) was not called in the current subinterpreter. Returning 0. 

That I could not tell you how many times this is repeated. I start console2, and the command history goes off after my 300 lines. I could print it all in a text file if necessary, but I thought I'd ask first. Does anyone know what it is or how to fix it?

+6
source share
1 answer

According to this post , you can upgrade to Cryptography 1.7 with pip:

 pip install --upgrade pip pip install cryptography>=1.7 --upgrade 
+8
source

Source: https://habr.com/ru/post/1014497/


All Articles