I installed Jupyter Notebook on Windows 10. But I got an error when launching it in Visual Studio Code as:
jupyter : The term 'jupyter' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
After searching online, I decided to install Anaconda first and run Jupyter from it. But launching it from Anaconda was directed to a web address. It looks like Jupyter is only a web application.
I wonder if it is possible to run the Jupyter Notebook as a desktop application on Windows.
There is a JupyterLab Desktop App, see here and here. I don't know how old of a version of Windows works for it.
Rest was built from discussion in comments:
On Jupyter with VS Code:
Jupyter itself works with VScode to run Jupyter notebooks in VScode. You wouldn't need the JupyterLab Desktop App in that case. You do need Jupyter though. See here if you are interested in using Jupyter notebooks in VSCode.
On installing packages that worked before installed Anaconda:
The easiest solution would be to reinstall them. It is possible you could add the already installed ones to your path, but if you have room it is easiest to keep your Anaconda installed stuff where it is and separate from what you had. The easiest way to sort where to install them is to let Jupyter handle it. For example, if you want to work with Pandas in a notebook, in that notebook run %conda install -c anaconda pandas, based on here and the magic install command. For the packages that conda cannot install, and only for those, use %pip install <package_name>.
You can delete the install commands out of the notebook after if you want. You may just want to comment them out so you remember. For the short term you are fine re-running the commands because if the package is already installed by conda or pip it won't get reinstalled; however, if the package gets a new release and you aren't specifying versions, you'll get the latest when that install command next runs and if there is an error or incompatibility, then you'll have caused yourself an issue you could have avoided.
Related
Mac OS 12.2.1
Anaconda Navigator 2.1.2
Spyder 5.1.5
I’ve been to the Spyder Web site, performed what was described as “Basic First-Aid” as well as “Emergency CPR” without satisfactory resolution. The first symptom was that the debugger just hung. After performing the suggested fixes (updating Anaconda, Spyder, and Spyder dependencies, system re-boot, etc.), the debugger now reports: “OperationalError: attempt to write a readonly database.”
I’m at my wits’ end. I’m wondering if I need to completely re-install all of Anaconda. Is there a “best way” to do this? Is there a web site that I can consult that will demonstrate how to get a fresh installation?
ADDENDUM
So, I cleaned Anaconda from my machine (what a horrific experience!) and re-installed it, using conda for both tasks. I started Anaconda and then launched Spyder. Then I loaded one of my modules, set a brake-point in the editor, and boom! The Spyder debugger worked. However, the new installation of Anaconda was lacking a particular library: pyreadstat. I used conda to get this library. I then launched Anaconda again, saw that pyreadstat was now in the base(root) environment. I ran one of my packages (8 modules mainly consisting of numpy and itertools manipulations of N-D arrays) and everything worked, including calls to pyreadstat to read SAS datasets. Okay, everything seemed copacetic. So, I tried to debug one of my modules and the debugger failed again, returning the message: “OperationalError: attempt to write a readonly database.” WTF! Is conda trashing Spyder’s debugger in some mysterious way? I don’t get it. Why would pyreadstat affect Spyder. It must be conda.
To answer my own question, in the Mac Terminal app, I typed:
--> conda install -c conda-forge spyder=5.2.2
Boom! All is well.
I had the same problem on Windows10 with spyder version 5.1.5.
For me, updating Spyder to the newest version as suggested here worked as well. This can be done in two ways:
Console
Open the console or, if you're working on Windows, the Anaconda Prompt and type the following commands in order to first uninstall spyder, and then re-install the newest version (just updating didn't work for me).
conda remove -n myenv spyder
conda install -n myenv -c conda-forge spyder
The first command, remove, uninstalls spyder in the virtualenv called 'myenv'. If you don't use virtualenvs, just leave the -n myenv aside.
The second command, install installs spyder from the third-party channel conda-forge instead of the official channel defaults. This option is necessary in order to install a spyder version newer than 5.1.5
Anaconda Navigator
Uninstall Spyder: In the "Home" tab, select the correct virtual environment in the "Applications on" dropdown menu. Then click on the gear symbol in the upper right corner of the spyder tile and select "remove application".
Add conda-forge to your environment's channels: This is nicely described at the bottom of this page.
Install spyder again, in the way you did it the first time.
Click again on the gear on the spyder tile, choose "install specific version" in order to update to the newest version. Now, versions newer than 5.1.5 should be available.
I have installed the Anaconda 3 in my windows 10 and it has not installed the Scripts folder and the Anaconda Prompt or Navigator applications.
I have come here and in other sources for an answer and tried to reinstall, use the cmd as adm to install with the conda commands, but the system does not recognize the conda command. I have seen answers with the Scripts folder, but it was not installed.
I have also seen answers advising me to install miniconda and then update to anaconda, but again, miniconda has the same problem as anaconda: no scripts folder, no recognition of the conda command.
I don't know what to do.
Dear all who may have had the same problem, what worked for me was to install the 32-bit version, I had heard it was more stable.
I did not have to restart Windows after installing this version, It was already there, Anaconda Prompt and Navigator.
I work on a hp Probook with windows 10 and the problem was that the application hp Sure Sense Installer block the installation of anaconda. After uninstalling the hp Sure Sense Installer application and reinstalling anaconda, everything works fine !
I install Anaconda vs 2019.10 on my Windows 10 but I couldn't find the shortcuts to it.
I've tried searching for it using CMD but it's returns the message that Anaconda can't be found
And I can't also find jupyter notebook or spider
Reinstall Anaconda and don't change the default settings. Everything will work as expected. C:\Users\user_name\AppData\Anaconda3\condabin will be added to your PATH and you'll only need to conda activate (or run the Anaconda-Prompt shortcut) to start using Python.
I have windows-7 64 bit machine and Python3.6.1(32-bit) installed on it. I wanted to try spyder as IDE for python. I don't have Anaconda or anything like that. So, I installed spyder from command line (cmd.exe) and it did install successfully and prompt returned.
I think it is installed because
I can see spyder3.exe under C:\Users\UserName\AppData\Local\Programs\Python\Python36-32\Scripts
From cmd.exe when I enter spyder3 it doesn't throw any error and a rotating circle appears which indicates something is processing. But nothing is launched.
After running spyder3 from cmd.exe though nothing gets launched except the rotating circle for couple of seconds, I see spyder.lock folder under C:\Users\UserName\.spyder-py3
When I delete spyder.lock folder under C:\Users\UserName\.spyder-py3 and run spyder3 again in cmd.exe the folder is created again.
Question: How can I make spyder launch? Did I do something wrong while installing spyder or am I trying to launch it with an incorrect method?
I had to install PyQt5. It is a requirement for spyder on windows and I was missing it. After I installed it I can launch spyder3 from cmd.exe
I am running into an issue where default site packages are no longer working in a jupyter notebook. However, when I send a script to the computer via windows cmd to install pip "package name", the package works again. Site Packages were working properly prior to yesterday. This is what changed:
Yesterday, I ran a script via windows cmd to install a few packages and to activate a few widget extension in the jupyter notebook. Because I ran the script within windows cmd, could windows shell be taking precedence over the anaconda shell?
Troubleshooting: For the default packages that were note working, I reran the install pip "package name" in a windows shell and the package started working again, along with the new packages I installed yesterday with windows cmd.
When I look in c:\Anaconda3\Lib\site-packages the modified date for the "reinstalled" packages shows the original date that I installed the software.
This software is very new to me and I am still trying to learn the logic of it along with the process. Any help or recommendations would be greatly appreciated!
OS: Windows 7 64-bit
Software: Python 3.5.2 (Anaconda3 4.1.1 64-Bit)