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.
I have the most recent Anaconda navigator on both my Windows and Linux machines, but when i open Spyder on either machine it tells me that Spyder 4.1.5 is available and i should install it. I can't do this through navigator.
The Anaconda page says to run 'conda install -c anaconda spyder' to install Spyder 4.1.5. link: Anaconda.org page On my linux machine this just tries to install Spyder 4.1.4 (Ubuntu screeenshot), I get the same result with windows (windows screenshot)
It seems this is a regular issue, what is the point of relesaing a piece of software and then not allowing it to be downlaoded and installed in the very manner that both Anaconda and Spyder tell you to do it?
Since you seem to have a previous version installed, did you try a simple update from the conda prompt?
conda update spyder --dry-run
Just remove the --dry-run part if everything looks fine.
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 installed Trac on Windows 7 using Trac-1.0.1.win32.exe.
How do I cleanly uninstall this? My reason for uninstalling is that I installed it with Python 3.4, and then discovered that it actually requires Python 2.7. So I would like to remove the existing install, and re-install it for Python 2.7 .
Nothing appears for Trac in the Windows 7 "Add/Remove Programs" area. There is a program RemoveTrac.exe that was created under the Python34 directory, however when I run that it pops up a MessageBox with title Runtime Error and text This program is normally started by windows, and it does not uninstall.
I'm not sure but to me it seems that installer just checks your environment, detects some pathes and sets them in the installed Trac environment. Trac should be on top of Python and SVN. So likely, you can just remove the installed Trac directory.
I have recently tried to install Python 3.4 as an alternative installation on my system in an attempt to familiarise myself before migrating code. My main Python installation is 2.7.6.
I tried the 64 bit installer for Windows, but it came up with an error message
There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.
After this the install is rolled back (from the point shown below):
I have eventually found a solution to this posted below and decided to share in case anyone else was having the same issue.
After some looking online I found (here) that the issue was related to conflicting pip installs (I have a version already installed for Python 2.7 and apparently this is not compatible with the version that ships with Python 3.4.
To get around this issue I simply de-selected pip from the install options shown below and the install went ahead smoothly:
Run installer again and select PIP installation.
If the PIP fails to install with the same error, you may want to check environmental variables using a tool like http://eveditor.com/ which enables to check whether they are valid. If you had another version installed before, you most likely have wrong PYTHONHOME and PYTHONPATH variables. Fix them by setting them to relevant paths. e.g. PYTHONHOME=C:\python27 and PYTHONPATH=c:\python27\Lib
You will then be able to run and install PIP.
My issue was that I had a PYTHON_HOME or PYTHON_SOMETHING environment variable set. After removing the environment variable, the installation worked perfectly.
What worked for me, strangely enough, was the "Microsoft Program Install and Uninstall troubleshooter"
The "deselect pip" solution did not work for me.
My Python 3.4.1 install was failing with the same "A program run as part of the setup did not finish as expected" error. I tried both installing it on top of Python 3.4.0 and installing it in a new folder, but got the same error. I tried uninstalling Python 3.4.0 first, but got the error during the uninstall, as well.
I ran that Microsoft utility, which helped me uninstall 3.4.0, and was then able to install 3.4.1 cleanly. The utility has options for both problematic installs and uninstalls, so it may help even if you're doing a new install, not an upgrade.
I'm running 64-bit Windows 7, but was working with 32-bit Python versions.
I had similar issues with Python 3.4x on Windows 8.1. Even after a successful install, the uninstaller would fail in the same way. Ultimately, "Method 1" at the MS forum solved this for me when I ran Microsoft's (Un)installer Fix It.
I also had the problem that pip couldn't be installed like #ChrisPosser.
So I deselected pip and the installation went fine. afterwards I restarted the setup, chose "change python" and installed pip. now everything worked like expected.
If you have any problems with windows installers I recommend activating the verbose log like this:
msiexec /i python-2.7.10-1.609.2.msi /lv install-python.log
From the logs I could see that it was the pip install, which was not working.
Yes, I faced the same issue, and was working on this for the past one hour. Was trying to uninstall the Python 3.4.1 from the control panel -> uinstall program -> add/remove program, but was facing issues.
This trick worked for me:
Manually deleted the 3.4.1 folder, which was present in my C folders after I installed the 3.4.1
Then I followed these steps:
-> Went to Regedit.exe, checked in both HKEY_CURRENT_USER, HKEY_LOCAL SOFTWARE Folder, and deleted the Python folders there.
-> windows 8 -> Downloads -> 3.4.1 msi setup (Glad I never deleted it)
-> Right clicked on the msi setup and choose the repair option
-> The repair would re install the Python 3.4.1
-> After this, I un-installed the Python 3.4.1
-> Then I deleted the 3.4.1 msi setup.
Rebooted the system, and now, there is no instance of Python 3.4.1 in my system.
According to me when environment variables containing name 'Python' are created they somehow becomes related with python. I was unable to open idle (GUI PUTHON) and to uninstall it . Deleting a variable named 'PYTHON PATH' solved my all python related problems.
I had 3.7.4 and wanted to move to 2.7.13.
I uninstalled 3.7.4
Tried to install 2.7.13 but got the same error.
There was a 2.7.10 installer(not msi) also present, uninstalling which gave the same error.
So I downloaded 2.7.10 msi, installed it, and then just installed 2.7.13 from the downloaded msi and it worked fine. This overwriting worked because the major version i.e. 2.7 was same for both.
I don't know if this is helpful but after the hours I spent on this, I wanted to write out what worked for me.
Yup, I have already installed another version of python. I have uninstalled them using Program features. But still the same issue persisted because of the folder which was present in my C: drive. After deleting them manually, the installation got completed without errors
I faced this issue because of 2 conflicting versions of 7zip. Removing them both and installing just one fixed this issue.
I had python3.4 installed, then added 3.5, and deleted 3.4. That was a mistake. In trying to get a library to work, I had to go back to 3.4. I uninstalled 3.5, but couldn't uninstall 3.4 (folder deleted).
I ended up searching the registry in rededt32 for "python". There was a Guid folder with a number of entries that had c:\python34 and one more related to the same folder that I deleted. After this, the install worked correctly.
Windows 10.
Mine was linked to having installed an older version in the past, only for my own user account. I got around it by telling the installer to install Python for all users.
For me none of the suggested fixes worked for me. However checking the option "Install just for me" instead of "Install for all users" (Windows 10) worked for me. So this might be another option to try.