Error due to incompatibility with several python libraries что это

не устанавливается anaconda

После запска установки на шаге выбора места размещения выпадает окно с текстом «Due to incompatibility with several Python libraries “Destination Folder” cannot contain non-ascii characters (special characters or diacritics) Please choose another location».

Подскажите, как быть ? Заранее благодарю !

• Активные
• Старые
• Голоса

Весь путь не должен содержать русских букв. Попробуйте создать папку прям на диске:

Воспользоваться Гугл-переводчиком https://translate.google.ru/ — перевести сообщение, которое выдается — пишет, что «недопустимые символы в каталоге Установки» — задайте при установке Каталог пройтой только з английких букв и цифр (попробуйте разные символы не использовать пока не прокатит)

В моем случае уже раз 100 выбирала разные файлы, переиминовывала. но результат тот же. есть еще советы?

Перевести то проблем не было.. просто было не понятно ЧТО конкретно ребовалось. после Вашего совета разобрадся и все настроил — большое спасибо !

Anaconda3 4.3.0 (64-bit) Setup Error Message

path is set from browse in installer and has no special characters ?

1 Answer 1

Found that this is an Anaconda 4.3.0/4.3.0.1 bug caused by the NSIS installer. You can find the bug description posted begin February 2017 here. In that post mingwandroid proposed also a fix proposal that could be integrated in the 4.3.12 release.

The Overflow Blog

Related

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

Site design / logo © 2023 Stack Exchange Inc; user contributions licensed under CC BY-SA . rev 2023.9.7.43618

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

Anaconda3 4.3.0 (64-bit) Setup Error Message

path is set from browse in installer and has no special characters ?

Best Solution

Found that this is an Anaconda 4.3.0/4.3.0.1 bug caused by the NSIS installer. You can find the bug description posted begin February 2017 here. In that post mingwandroid proposed also a fix proposal that could be integrated in the 4.3.12 release.

Related Solutions

Python – Anaconda3 2.4 with python 3.5 installation error (procedure entry not found; Windows 10)

Finally I have found the reason. So, if anybody else has this problem:

Here the entry points are an issue as well and Michael Sarahan gives the solution. Install the Visual C++ Redistributable for Visual Studio 2015, which is used by the new version of python, first. After that install the Anaconda-package and it should work like a charm.

Conda environments not showing up in Jupyter Notebook

I don't think the other answers are working any more, as conda stopped automatically setting environments up as jupyter kernels. You need to manually add kernels for each environment in the following way:

Ошибка при установке анаконда

If you have a troubleshooting issue that is not listed here, obtain free support
for Anaconda through the
Anaconda community.
For Anaconda installation or technical support options, visit our
support offerings page.

You may also wish to see the Anaconda Navigator Troubleshooting guide .

On this page:

• “This package is incompatible with this version of macOS” error when running a .pkg installer on OSX
• 403 error
• HTTP 000 CONNECTION FAILED
• Anaconda installer download problems
• Cannot open Anaconda Prompt after installation
• Cannot see Anaconda menu shortcuts after installation on Windows
• Windows error: Failed to create Anaconda menus or Failed to add Anaconda to the system PATH
• I’m having trouble with the Anaconda installer on Windows. How can I debug my issue?
• Cannot get conda to run after installing
• Recovering your Anaconda installation
• Using Anaconda behind a firewall or proxy
• .zshrc not updated under macOS Catalina
• Insecure Platform Warning
• Conda: command not found on macOS or Linux
• Conda: Channel is unavailable/missing or package itself is missing
• Collecting package metadata (repodata.json): — Killed
• Anaconda interfering with other software on Windows
• Windows error: no environment named “search” exists
• Error message on Miniconda install: Already installed
• Conda update anaconda command does not install the latest version of Anaconda
• Linking problems when Python extensions are compiled with gcc
• Error message: Unable to remove files
• Files left behind after uninstalling Anaconda on Windows
• Spyder errors or failure to launch on Windows
• Problems running Anaconda on macOS 10.12.2
• “execution error: localhost doesn’t understand the “open location” message. (-1708)” when opening a Jupyter notebook on macOS 10.12.5
• Missing libgfortran on Power8
• Missing libgomp on Power8
• Anaconda on Power8 reports “can not execute binary file”
• Uninstaller requests admin privileges on Windows
• Windows permission errors when installing from Favorites folder
• Trouble with activation on PowerShell on Windows
• Cannot install Distribution 2019.07 on a webfaction server
• Segmentation fault on package import with macOS Python 3.7 intepreter
• Using 32- and 64-bit libraries and CONDA_FORCE_32BIT
• “The installation failed” message when running a .pkg installer on OSX

“This package is incompatible with this version of macOS” error when running a .pkg installer on OSX¶

Cause¶

When running the .pkg installer, you may encounter this error during the “Installation” step:

This error occurs when the installation attempts to write to a directory for which it does not have write permissions.

Solution¶

Manually select an appropriate install location. The following example shows how to select your user’s home directory.

Re-run the installer. When you get to the Installation Type page, click Change Install Location….

Click Install on a specific disk….

Select the appropriate destination drive. Then click Choose Folder….

Select your user’s home directory (e.g. /Users/johndoe/). Then click Choose.

In the message box, confirm the name of the install folder you chose in the previous step. Then click Continue.

Click Install, and then proceed with the rest of the installation.

If you continue to receive the same error message, please open an issue here, and be sure to include the installation log output from your install.log file, which can be found at /var/log/install.log .

403 error¶

Cause¶

A 403 errors is a generic Forbidden error issued by a web server in the event the client is forbidden from accessing a resource.

The 403 error you are receiving may look like the following:

• The user has misconfigured their channels in their configuration (most common)
• A firewall or other security device or system is preventing user access (second most common)
• We are blocking their access because of a potential terms of service violation (third most common)

Solution¶

First, run the following to undo your configuration of Anaconda Professional:

Next, install or upgrade the conda-token tool:

Lastly, re-apply the token and configuration settings:

If this doesn’t resolve the issue, Anaconda recommends consulting our Terms of Service error page.

HTTP 000 CONNECTION FAILED¶

If you receive this error message, run the following command:

Anaconda installer download problems¶

Cause¶

The Anaconda installer files are large (over 300 MB), and some users have
problems with errors and interrupted downloads when downloading large files.

Solution¶

One option is to download and install the smaller Miniconda (under 60MB) and then use the command
conda install anaconda to download and install all the remaining packages
in Anaconda. If the package downloads are interrupted, just run
conda install anaconda again. Conda only downloads the packages that were
not finished in any previous attempts.

A second option is to download the large Anaconda installer file, and restart
it if the download is interrupted or you need to pause it.

Windows

If you use Internet Explorer:

1. Click the Settings icon.
2. Click “View Downloads” to open the Download Manager.
3. Click on the “Resume” button next to the stopped download to restart
   downloading. The download resumes at the point where it stopped.

If you use Edge browser:

1. In Windows Explorer, open your downloads folder. There will be
   temporary files there associated with the partial downloads. Delete all of
   the temporary files except for the download you want to resume.
2. In Edge, click the file to download it again. Pause the download but do not
   cancel it.
3. In Windows Explorer, open your downloads folder. You will see two files: the
   partially downloaded file from earlier, and the paused download you just
   started. Copy the name of the file you just started, delete this file, and
   rename the other file with the copied name.
4. In Edge, resume the download.

If you use Chrome browser:

Download the plugin for Chrome called Chrono Download manager. In your Chrome
browser, go to https://chrome.google.com/webstore/category/extensions, search
on “Chrono Download” and select, “Add to Chrome.”

To resume the download using Chrono Download, from your top browser menu, click
on the Chrome menu button, then click “Downloads.” Select the filename, then
click “Resume” to restart your download.

macOS and Linux

In your terminal window, download the file with the command
curl -O FILENAME .

Replace FILENAME with the full path and name of the file, including
http:// or https:// .

To pause the download, use CTRL-c .

While a download is paused, you can shut down or restart your computer.

When ready to resume your download, use curl -O -C FILENAME .

Where “-C” is the option for “continue”. You can pause and restart a download
as many times as you wish.

Cannot open Anaconda Prompt after installation¶

I get an error message that says “activate.bat is not a recognized file or command”.

Cause¶

Anaconda 5.0.1 sometimes does not install completely on Windows.

Solution¶

Until a new version is released, you can install Miniconda, and then use conda
to install the rest of the packages in Anaconda with these instructions:

Open the command prompt (Windows key + the R key on your keyboard) which brings
up the Run… dialog box. Enter cmd.exe and then press enter)

Copy the following text:

Then paste it into the command prompt window.

This installs to a subdirectory in your User directory named anaconda3 .
If you use a different directory, replace anaconda3 with the actual name.

I’m having trouble with the Anaconda installer on Windows. How can I debug my issue?¶

Cause¶

The cause could be any number of issues.

Solution¶

Anaconda 4.4 added a feature to the Windows installer so that the “verbose” install information is printed out to a special debug stream via the Win32 API function OutputDebugStream. To see these messages, during installation you need to run the Microsoft utility https://technet.microsoft.com/en-us/sysinternals/debugview.aspx. This may provide useful clues for troubleshooting or submitting bug reports.

Cannot get conda to run after installing¶

You may get “conda not found” or “conda is not recognized as an internal or external command” or a similar message, and you cannot execute conda in a terminal window regardless of what path you are on.

Cause¶

Most likely when you were installing Anaconda or Miniconda, you answered “NO” to the question whether or not to prepend the conda prompt to your path.

Solution¶

Uninstall and then reinstall Anaconda or Miniconda, answering “YES” to the question about prepending the conda prompt.

Or, you can manually edit your .bashrc file to prepend the Anaconda or Miniconda install location. Open a text editor and in your home directory, locate the hidden file .bashrc. Add this line to it and save:

Close your terminal window and re-open before running a conda command.

Recovering your Anaconda installation¶

If your Anaconda installation is in a state where normal conda commands
are not functioning, use the following steps to repair Anaconda and
preserve your installed packages and environments.

Step 1¶

Download a new installer, then follow
the instructions for your system Windows, macOS, or Linux.

Use the actual path, filename, and directory name for your installation.

Windows¶

Change your original installer’s name so you do not overwrite it:

move Anaconda Professional_old

Run the Anaconda.exe installer as usual and use robocopy to sync the
directories:

macOS¶

Change your original installer’s name so you do not overwrite it:

mv Anaconda Professional_orig

Install to same directory as your original installer:

Linux¶

Change your original installer’s name so you do not overwrite it:

mv Anaconda Professional_orig

Install to same directory as your original installer:

Step 2¶

Run conda list to view the packages from the previous installation.

Run conda info -e to list the environments created in the previous installation which are now available in the new installation.

Using Anaconda behind a firewall or proxy¶

Corporate security policies may prevent a new Anaconda installation from
downloading packages and other functionality that requires connecting
to an external server. To make external connections you may need to connect to a
firewall/proxy. Additionally, your IT team may need to allow connections
to https://anaconda.org and https://repo.anaconda.com as these are the
main package repositories.

Solution¶

To add the proxy information you will need to add two entries to your
.condarc file located in the user’s home directory. This information
should be made available by your IT team and may contain a username and
password that is included in the URL. Read more about the
.condarc configuration.

In some situations it may be necessary to export the HTTP_PROXY and
HTTPS_PROXY environment variables.

MacOS/Linux

Windows

If these steps have not allowed connections you should speak to your IT
team to verify that security policies are not blocking connections to
https://anaconda.com and https://repo.continuum.io.

.zshrc not updated under macOS Catalina¶

Cause¶

MacOS Catalina changed the default shell from Bash to zsh.

Solution¶

Run bash -c «conda init zsh» and then restart your shell to initialize conda for zsh.

Insecure Platform Warning¶

Cause¶

“InsecurePlatformWarning” appears only when the installed version of Python is
older than version 2.7.9. This message warns only that the validity of the SSL
connection is not being verified. It should not affect your package downloads.

Solution¶

To resolve this on Windows, install the updated package ndg-httpsclient :

When initially installing this package, you receive the SSL warning again. Once it is installed, the package will prevent the warnings.

Conda: command not found on macOS or Linux¶

Cause¶

The conda shell function is not available, or is not working
properly. Some causes:

• You have set conda_auto_activate_base to false. You need to run conda activate [env] . Env is optional, the default if not provided is base.
• You haven’t started a new shell after installing Anaconda/Miniconda (assuming you allow it to modify your startup script)
• You didn’t allow the installer to modify your startup script
• Conda has been corrupted, usually by a change in the Python package (e.g. 3.6->3.7)

Solution¶

Run /full/path/to/bin/conda init to modify

Either start a new shell or source the modified

/.bash_profile
(Windows/MSYS2, Windows/Cygwin and macOS) or

/.bashrc (Linux and Windows Subsystem for Linux).
Source them via .

You may prefer that conda not automatically activate your base
environment when a new shell is started. This behavior shadows
your system Python, and some users prefer to have their conda
environment be inactive until they need it. To achieve this,
you can set a .condarc setting:

If you have this set, the conda command will still be available
as a shell function, but your base environment will not be
active when a new shell is started. To activate your base
environment, run conda activate .

Conda: Channel is unavailable/missing or package itself is missing¶

Cause¶

After a user has configured their .condarc for either Professional or Business, in some cases they are unable to install packages. They may receive an error message that the channel or package is unavailable or missing.

Solution¶

One potential fix for all of these is to run the following command:

This will clear the “index cache” and force conda to sync metadata from the repo server.

Anaconda interfering with other software on Windows¶

Cause¶

If a user chooses to add Anaconda to the Windows PATH, this can cause programs
to use the new Anaconda versions of software such as Python and not the
versions that were already in place. In some cases this can cause
incompatibility and errors.

Solution¶

Anaconda recommends against adding Anaconda to the Windows PATH manually. Instead, use Anaconda
software by opening Anaconda Navigator or the Anaconda Prompt from the
Start Menu.

Windows error: no environment named “search” exists¶

If anaconda-client is not installed and you search for a package on
anaconda.org using the Anaconda search command:
anaconda search -t conda packagename

You will receive the following error message:

Anaconda on Windows contains an anaconda.bat file, which is used for setting
environment paths and switching environments. If anaconda-client is not
installed, this batch file is called instead and produces the error.

To resolve the error, install anaconda-client:

conda install anaconda-client

And then search for a package:

anaconda search -t conda packagename

Error message on Miniconda install: Already installed¶

Cause¶

This situation can occur if you are getting a conda error and you want to reinstall Miniconda to fix it.

Solution¶

For macOS and Linux, download and install the appropriate Miniconda for your operating system from the Miniconda download page using the force or -f option:

For Miniconda3-latest-MacOSX-x86_64, substitute the appropriate filename and version for your operating system.

Be sure that you install to the same location as your existing install so it overwrites the core conda files and does not install a duplicate in a new folder.

Conda update anaconda command does not install the latest version of Anaconda¶

Cause¶

For users who have installed packages that are not compatible with the latest version of the Anaconda metapackage, running conda update anaconda updates the Anaconda metapackage to the latest compatible version, but this may not be the latest version.

Solution¶

Obtain a list of the conflicting packages by running conda update anaconda or conda install anaconda=5.2 .

Replace 5.2 with the latest version number.

Once you know which packages are conflicting, you can update all current packages without upgrading to the latest version of Anaconda, or you can remove the conflicting packages and then upgrade to the latest version of Anaconda.

To update all current packages without upgrading to the latest version of Anaconda:

1. Use conda remove anaconda to remove the Anaconda metapackage itself. (This will not remove any of the packages included with Anaconda.)
2. Use conda update —all to update all currently installed packages.

To remove the conflicting packages and upgrade to the latest version of Anaconda:

Remove the conflicting packages by running conda remove package-name for each one.

Replace package-name with the name of the package.

Run conda update anaconda .

Linking problems when Python extensions are compiled with gcc¶

Cause¶

When compiling Python extensions with gcc on Windows, linking problems may result.

Solution¶

To resolve these linking problems, use the mingw import library–the conda package libpython–which Anaconda builds and includes with the Anaconda Distribution.

Error message: Unable to remove files¶

When trying to update or install packages with conda, you may see an error message such as:

Cause¶

This may be caused by a file lock issue.

Solution¶

Before updating or installing any packages with conda, be sure to terminate any running Anaconda processes such as Spyder or IPython.

You can also force the installation of the package: conda install -f package-name .

Replace package-name with the name of the package that you want to install.

Files left behind after uninstalling Anaconda on Windows¶

Cause¶

Some users may need to keep settings files and other users may need to delete them, so Anaconda leaves some settings files in place when it is uninstalled. Specifically, the directories .spyder2 , .ipython , .matplotlib , and .astropy remain. Depending on your version of Windows these may be in C:Documents and SettingsYour_User_Name or in C:UsersYour_User_Name .

Replace Your_User_Name with your Windows user name as it appears in the Documents and Settings or Users folder.

Solution¶

Manually delete any unneeded settings files.

Spyder errors or failure to launch on Windows¶

Cause¶

This may be caused by errors in the Spyder setting and configuration files.

Solution¶

Close and relaunch Spyder and see if the problem remains.

On the menu, select Start, then select Reset Spyder Settings and see if the problem remains.

Close Spyder and relaunch it from the Anaconda Prompt:

1. From the Start menu, open the Anaconda Prompt.
2. At the Anaconda Prompt, enter Spyder .
3. See if the problem remains.

Delete the directory .spyder2 and then repeat the previous steps from Step 1. Depending on your version of Windows, .spyder2 may be in C:Documents and SettingsYour_User_Name or in C:UsersYour_User_Name .

Replace Your_User_Name , with your Windows user name as it appears in the Documents and Settings folder.

Problems running Anaconda on macOS 10.12.2¶

Cause¶

Some installations of Anaconda on macOS 10.12.2 experienced incorrect file and
directory permissions, which caused a range of errors with Navigator and other
parts of Anaconda.

Solution¶

Anaconda recommends that any users with Anaconda on macOS 10.12.2 follow these steps:

Uninstall Anaconda. Open the Terminal.app or iTerm2 terminal application and
remove your Anaconda directory, which will have a name such as “anaconda2”
or “anaconda3”, by entering a command such as this: rm -rf

“execution error: localhost doesn’t understand the “open location” message. (-1708)” when opening a Jupyter notebook on macOS 10.12.5¶

Cause¶

This version of macOS seems to have a bug affecting some of the ways for a program to open a web page in a browser.

Solution¶

Several possible workarounds have been found for this bug.

You can explicitly set the browser in

/.jupyter/jupyter_notebook_config.py with a line such as this:

Or you can copy the Jupyter notebook URL from the log messages on the command line and paste it into your browser.

Or you can set the BROWSER environment variable: export BROWSER=/Applications/Google Chrome.app/Contents/MacOS/Google Chrome

Further information is available at the Jupyter bug tracker, the Python bug tracker, and this blog post.

Missing libgfortran on Power8¶

Cause¶

Anaconda 4.4.0.0 for Power8 did not include libgfortran.

Solution¶

Anaconda 4.4.0.1 and later for Power8 do include libgfortran.

Upgrade to the latest version of Anaconda:

Anaconda 4.4.0.0 users who do not wish to upgrade may instead install libgfortran with this command:

Missing libgomp on Power8¶

If the Python command “import numpy” fails, the system is likely missing the
libgomp system library.

Cause¶

Most Power8 Linux distributions include libgomp, but some may not.

Solution¶

Check whether the system is missing libgomp with this command:

If libgomp.so.1 is listed in the “not found:” section, it must be installed.

Install libgomp on Ubuntu with this command:

Install libgomp on Red Hat Enterprise Linux (RHEL) or CentOS with this command:

Anaconda on Power8 reports “can not execute binary file”¶

Cause¶

Anaconda on Power8 only supports little endian mode. The little endian Python binary will not execute on a big endian operating system.

Solution¶

Install Anaconda on Power8 on a little endian Linux installation or VM.

Uninstaller requests admin privileges on Windows¶

Cause¶

After installing Anaconda or Miniconda as a non-administrative user on Windows,
uninstalling may prompt for administrative privileges.

This occurs when running the uninstaller by choosing Control Panel, System,
Apps & features, Python x.x.x (Miniconda3 4.3.xx 64-bit), Uninstall.

Solution¶

Open the Anaconda or Miniconda installation folder and run the .exe file
uninstaller from that location. Uninstallation will complete without prompting
for administrative privileges.

EXAMPLE: If you installed Miniconda3, the uninstall file will be
Uninstall-Miniconda3.exe . Users who installed Miniconda2 or Anaconda will
find a similar file with the appropriate name.

Windows permission errors when installing from Favorites folder¶

Cause¶

The Windows Favorites folder has unusual permissions and may cause permission
errors with installers of any software. If you try launching the installer from
the Favorites folder you may see errors such as “Setup was unable to create the
directory”, “Access is denied”, or “Error opening file for writing”.

Solution¶

Move the installer to a different folder and run the installer from the new
folder.

Trouble with activation on PowerShell on Windows¶

Solution¶

If you run into the following backtrace on Windows:

Open a cmd.exe prompt. cd to where you installed conda and run:

Close the cmd.exe prompt and the Anaconda Prompt or the Anaconda
PowerShell Prompt as usual.

If this doesn’t work, try running:

Cannot install Distribution 2019.07 on a webfaction server¶

You may receive an error when trying to install
Distribution 2019.07 for Linux on a webfaction server:

Cause¶

This is caused by having TMP as a noexec.

Solution¶

To enable installation, you can temporarily
set TMP to somewhere else from which you can execute software.

After installing, set the TMP folder back to its initial location.

Segmentation fault on package import with macOS Python 3.7 intepreter¶

In CPython < 3.8, using python3-config to determine a linking command line to
compile an extension module will cause that extension module to segfault upon import.
python3-config does provide command-line flags but for the different purpose of
embedding a Python interpreter.

Cause¶

This is because of the command-line flags returned by python3-config . Before Python 3.8,
those are needed to embed the core Python interpreter into a different project altogether
and not those that should be used when linking a Python extension module.

Python modules should never link to the core Python interpreter library directly,
either statically at build time or dynamically at runtime. This is because the Python
executable itself provides all the necessary functions and symbols.

Solution¶

You should only use python*-config —ldflags when linking to an interpreter library (either static or shared).

Action	Python < 3.8	Python >= 3.8
Get command line to link to extension module	python -c «import sysconfig; print(sysconfig.get_config_var(‘LDSHARED’))»	python3-config —ldflags
Get command line to embed Python interpreter	python3-config —ldflags	python3-config —ldflags —embed

python3-config doesn’t include the command/compiler name whereas the sysconfig way
does. This works provided none of your arguments have spaces:

Using 32- and 64-bit libraries and CONDA_FORCE_32BIT¶

To work with both 32- and 64-bit libraries, Anaconda recommends that you have
two separate installs: Anaconda32 and Anaconda64 or Miniconda32 and Miniconda64.

When working with both versions, add the path to your installer files to the PATH.

Always specify which version you want to work with because mixing 32- and 64-bit
packages can cause problems in your environment.

To get the information about conda including your PATH, run:
conda info -a

Using CONDA_FORCE_32BIT is not recommended because it forces 32-bit packages to
be installed in the environment, but does not force 32-bit libraries to load at
runtime.

CONDA_FORCE_32BIT should be used only when running conda-build to build 32-bit
packages on a 64-bit system.

“The installation failed” message when running a .pkg installer on OSX¶

Cause¶

When running the .pkg installer, you may see this message at the end of the installation:

If so, check for the following:

Open your /var/log/install.log file and check whether the most recent lines show errors following a call to conda init —all .

In your $HOME directory, check whether the owner of your shell config files is root :

Solution¶

If both of the above are true, do the following:

Change the owner of your shell config files to your current user:

Uninstall the previous installation. Then re-run the installer, making sure to select the “Install for me only” option.

Update: Two months after posting this question, I switched to a fresh install of Windows 10 and was able to install the correct version of Anaconda Python. Unfortunately the answers came too late for me to test them.

I want to switch from the 32-bit version of Anaconda Python 3.5 to the 64-bit version. First I uninstalled Anaconda through the ‘Programs and Features’ window, then I downloaded the Anaconda3-4.2.0-Windows-x86_64.exe installer and attempted to run it. For reference, I am using the 64-bit version of Windows 7. After some initial processing the installer is stuck on Execute: «C:Usersuser.nameAppDataLocalContinuumAnaconda3pythonw.exe» -E -s «C:Usersuser.nameAppDataLocalContinuumAnaconda3pkgs.install.py» —root-prefix «C:Usersuser.nameAppDataLocalContinuumAnaconda3» —post root

It does not throw any errors, it just hangs. I let it run throughout the night to see if it would progress any further, but unfortunately it was still stuck in the same place in the morning. Afterwards I tried looking for hidden Continuum files from the previous installation and removed those — also removed Anaconda from my PATH variable. I even tried installing miniconda instead of anaconda, but both installers get stuck in the exact same place. Am I missing a hidden file somewhere which is causing the Anaconda installer to hang?

Below is part of the installation log up until the execution command where it gets stuck.

Весь путь не должен содержать русских букв. Попробуйте создать папку прям на диске:

Воспользоваться Гугл-переводчиком https://translate.google.ru/ — перевести сообщение, которое выдается — пишет, что «недопустимые символы в каталоге Установки» — задайте при установке Каталог пройтой только з английких букв и цифр (попробуйте разные символы не использовать пока не прокатит)

В моем случае уже раз 100 выбирала разные файлы, переиминовывала…но результат тот же. есть еще советы?

Перевести то проблем не было.. просто было не понятно ЧТО конкретно ребовалось… после Вашего совета разобрадся и все настроил — большое спасибо !

Вчера я подвел Python и Pycharm. Я думал, что у меня будет сводная информация о Анаконде. Кто знает, эта установка, я провел мне ночь, (грусть большая). Я столкнулся с различными проблемами, перезагружая 20 раз, каждая проблема отличается. Это возможно до прямо сейчас. Перед лицом проблемы первая идея — Baidu, и результат все еще не может решить проблему. Все еще слишком глупо. Короче говоря, он все еще представляет собой краткое изложение проблем, которые вы столкнулись, так что я не вижу мою решить проблему блога, это также не белый, чтобы использовать Baidu.

оглавление:

1. Удаленная версия и загрузка ANACONDA

1.1 версия

1.2 Загрузка (два пути, официальный сайт / зеркальная сеть)

2. Установка Annaconda3 и резюме различных проблем! (Climax !!)

Позвольте мне подумать, где вы начинаете. Просто начните с самого начала.

1. Удаленная версия и загрузка ANACONDA

1.1 версия

AnaConda имеет две версии ANACONDA2 для PY2.7, AnaConda3 для PY3. При нормальных обстоятельствах каждый устанавливается сначала, с AnaConda с AnaConda в случае Python или библиотека или использует версию PY Conda, решить проблему сосуществования Multi-версий PY. На базе Python2 много онлайн на базе Python2 на базе Python2.

Здесь я впервые устанавливаю Python3.6 (подробную установку, можно увидеть.), Поэтому решающее резюме всех проблем основано на установленном Python3.6 Anaconda3 устанавливается на основе + Pycharm.

1.2 скачать

Есть два способа скачать: a. Официальный сайт (не рекомендуется)https://www.anaconda.com/download/

Не рекомендуется, потому что особенно медленно, и обычно устанавливающие обычно ошибки, если ваша сеть будет быстро с вами ( ), установить соответствующую версию хорошо, такая, как вы установка PY3.

B. Зеркальная установка сайта.https://mirrors.tuna.tsinghua.edu.cn/anaconda/archive/

Это зеркальная сеть университета Цингуа, напрямую найдите нужные вам загрузку, а быстро и усилие, рекомендуется.

Здесь вы должны поговорить об этом, я скачал последнюю версию 3-5.1.0. Почему вы чувствуете неудачу, отказаться от использования моего друга? 3-4.3 версия Отказ Конечно, это не должно иметь значения, если это необходимо, Wechat (18131375521, я отметку, я отметку, спрашивая меня).

Вы не должны знать, сколько версий я изменился для установки, и тот факт, что это не версия версии.

Короче говоря, именно этот дьявол (один из них).

2. Установка Annaconda3 и резюме различных проблем! (Climax !!)

2.1 Запуск установки

После того, как вы согласитесь, вы столкнетесь с этой проблемой:

Здесь вы напоминаете вам, это лучше всего следовать Python 3. Как выбор, короче говоря, я попробовал, если вы просто пользователь, конечно, выбирая Just Me Хорошо, но как только вы выберете это, когда вы устанавливаете Python, вы должны выбрать все все пользователю:

Поскольку я был в последний раз выбрал это для всех пользователей, когда я был установлен на Python3, я также выбрал всех пользователей при установке ANA.

Тогда путь — это путь, напоминающий малую белую, установку к дискору C может действительно избежать много небольших проблем, но даже если я не пытался перевести его в дисковер, выберите D диск, обратите внимание на Путь к простому D: Anaconda3, вроде этого, нет места, не имейте китайских иероглифов, особенно китайский путь! ! :

———> Тогда это важно выбор:

Это место, первое добавление AnaConda … Это предназначено для заполнения пути установки в системную переменную среды, выберите

Второй элемент состоит в том, чтобы использовать версию Python3.6, которая будет использоваться по умолчанию. Это, вероятно, будет иметь такую ​​проблему при выборе этого:

Я постановил Baidu перевел проблему, короче не управлять им, определите, смело выберите второй элемент. Если у вас есть какие-либо вопросы, мы решаем это позже.

————> После выбора это не очень длинная установка

Тихое ожидание этого, если нет проблем, поздравляю, вы только небольшое количество успешно установленного шага.

Но я здесь, потому что эта проблема вылетает в день! !

Не удалось создать меню ANACODA. ! ! Создание меню не удалось.

Я нашел различные методы в Baidu почти все пробовал:

A. Удалить переустановить один раз

B. Удалить оригинальную систему системной среды Java: в основном частью PATH и Java Home, первая копия со стороны Java, связанная с Java, сохранить его в Notepad, затем удалить, затем установить, после загрузки, то переменные среды изначально неполные добавления Отказ Не забудьте перезапустить.

C. Создание метода ярлыка, см. Вполне:http://www.mamicode.com/info-detail-1974384.html

D. Другие методы:http://blog.csdn.net/qq_33282758/article/details/77841404

E. Мой последний метод использования (эффективный): игнорировать игнорировать игнорировать игнорировать игнорировать, пока установка не будет успешной. В это время вы открываете свое начало меню, вы обнаружите, что не можете найти ничего о AnaConda

Win + R —> CMD —> D: —-> CD ANACONDA (эта часть красного цвета — войти в папку установки AnaConda)

Затем введите python. Lib _nsis.py mkmenus имеет много успешно

Вернуться к меню «Пуск» Вы можете увидеть различные ярлыки.

2.2 Проверьте, установлен ли успешная анаконда

Вы можете войти в Python в CMD, проверьте, есть ли:

Или вы можете войти в CONDA —version: (проверить знак успешной установки)

Если нет, или Prompt Conda не является внутренней или внешней командой, что означает, что ваша ANACONDA не настроила переменные среды.

Решение: Найдите вашу конфигурацию переменной окружающей среды, см. Если связано, связано с AnaConda в пути: (если не добавлено:

Добавьте эти два элемента

какие не добавляют. Определите Сохранить … Перезагрузите компьютер, откройте CMD как проверено выше.

2.3 Проверьте, будет ли успешная установка. Особенно Anaconda Navifator

Я не могу открыть Navifator Anaconda, я нашел не может быть открыт и предлагает следующую ошибку:

Решение:

• Будет Anaconda3Libraryplugins Каталог platforms Папка копирования в Anaconda3 После повторного открытия Anaconda Navigator
• Примечание. Не устанавливайте AnaConda в каталог

2.4 end

Это все вопросы, с которыми я столкнулся, подвел итоги в течение длительного времени, у меня не было много проблем, я установил так долго, я также пробовал много способов, что важно найти метод. Еще сами.

При установке программы Anaconda возникает следующее предупреждение:

Warning: ‘Destination Folder’ contains 1 space. This can cause problems with several Conda packages. Please consider removing the space.

Жмем Ок и вылетает ошибка

Error: Due to incompatibility with several Python libraries, I Destination Folder’ cannot contain non-ascii characters (special characters or diacritics). Please choose another location.

Жмем опять Ок и остаемся в том же окне.

Для устранения ошибки следует поменять путь.

Создать на диске C папку с именем программы и указать путь в окне Choose Install Location к данной папке. Ошибка должна исчезнуть.

5991

Похожие публикации:

1. 10 это сколько в числах
2. Додж караван гранд на сколько рассчитана коробка
3. Как включить синхронизацию контактов на андроиде
4. Как узнать пароль от роутера билайн