Sorry because i know that this topic has already been explored many times, but i couldn't find any solution to my problem.
I'm on windows 10 (if my company was working with linux i wouldn't have this type of problem --')
To sum up i tried to unsinstall Anaconda (the usual windows way by unstalling the application), to reinstall and make a fresh new installation (i'm naïve i was hopping this would be simple)...
Then when i launched spyder and the anaconda navigator, it told me that the shortcuts was invalid and that i needed to delete it.
Why not after all i just uninstall reinstall, i just needed to create new shortcuts using directly the application of spyder or anaconda that i would find in my computer...
But nothing worked. When i found the application (spyder or anaconda navigator) it didn't work, i wasn't able to launch anything. My anaconda prompt just seems to be a classic windows terminal (commands as conda, pip or jupyter just doesn't exist anymore).
This is the beginning....
Currently i have tried many thing (uninstall reinstall 4 times, delete folders myself etc..) but nothing worked and i'm affraid i totaly broke Anaconda..
Do you have any ideas on how i can get out of this mess ?
PS: of course to make the problem harder, i used a proxy to install package so i used pip for all my libraries and i'm not sure i can install with conda (whatever the conda commands doesn't work now :'( )
Seems that i finally achieve to delete all the concerning file and redo the installation ^^
Related
As the title says I'm trying to install anaconda onto my MacBook running macOS Monterey. I feel like I have tried everything. Have booted in safe mode, have downloaded older versions, have even set my profile picture to default (it was somehow a fix for another piece of software with the same install error). It simply won't get past the last little bit of 'running package scripts'. Any help is appreciated.
In the first link below, csoja gave a clue to solve this issue following the instructions in the second link.
https://github.com/ContinuumIO/anaconda-issues/issues/12940
https://docs.anaconda.com/anaconda/user-guide/troubleshooting/#the-installation-failed-message-when-running-a-pkg-installer-on-osx
In my case, I successfully installed the Anaconda distribution for M1 Anaconda3-2022.05-MacOSX-arm64.pkg after changing the owner of my shell config files from root to my current user name cgironda.
I hope this would be helpful!.
I also ran into this issue and the way I fixed it was by going into Finder and searching for a folder named 'Anaconda3'. Not entirely sure why but I when I completely deleted this folder from my machine and tried to install again everything seemed to work just fine. Hope this works for you!
PS: On the successful install it did still get stuck on again for like 10 mins
when i open anaconda prompt or use "conda" in cmd its says access is denied and window prompt
"
this app can't run on your pc to find a version for your pc check with the software publisher"
and right now i also cant open anaconda navigator as well
Noted: I have been using the anaconda for a while with no problem before, however i miss-clicked sign out option instead of shutdown from window10 and it seem that the privacy is changed somehow, so far i have try changing environment variable and manage app execution alias but both of them did not solve the issue. Please share your solution if you experience this before thank you
The solution I found for it is the worst possible: I simply reinstalled Anaconda.
You can also try just getting conda.exe from the compiled source and replace it on Scripts folder instead of reinstalling it.
I recently broke my installation of Anaconda Navigator by using:
conda update --all -y
Apparently this is not uncommon, and it was a good excuse to reinstall Anaconda and start a new environment from scratch.
However, my new installation gives the following error, when trying to install any libraries:
I have tried:
Windows uninstall of Anaconda, followed by reboot, then reinstall
uninstall/reboot/install as admin
uninstall/reboot/manually delete various remaining folders in the User directory/reboot/reinstall
etc etc
All these methods produce this error, when trying to install libraries.
install libraries using Anaconda console works fine
there aren't any problems in Windows' PATH
conda is up to date
What's going on!?
If you install Anaconda as admin, then you need to launch it as admin every time you run updates.
You can enable this behaviour by default by navigating to the Anaconda launch shortcut, right-click > Properties, go to Shortcut tab, click Advanced, and tick 'Always launch as administrator'.
Have you tried to create a new environment? I had the same message in another situation and that's what worked for me.
maybe you can try to download package and install it by yourself .
here is a python package url https://www.lfd.uci.edu/~gohlke/pythonlibs/#lxml
I have installed Anaconda recently in a new Windows computer. I have no experience with managing installed packages in Windows, but in Linux. I created a new project with PyCharm and chose to use as interpreter Python 3.7 that I installed separate from the Python 3.6 version that Anaconda comes with. Now I want to be able to use Anaconda modules such as numpy or pandas in my PyCharm Project, that is using a virtual environment set up in a PyCharmProjects folder.
I fail to understand how exactly should I do it. What is that I have to copy or run to migrate the Python packages installed in Conda to my Virtual environment created from a clean independent install of Python 3.7? When I try to import them they don't work. Do I have to create a new project and migrate the files or can I do it without that?
Edit
Also, I am very unclear about how I can run Python36 that Anaconda installed. There is no conda command in Windows and python runs python27. How do I do this?
So it seems that using Python in Windows goes a bit differently than in Linux/MacOS. In order to change the default version that runs when python command is executed, one has to run the command regedit and Find (Ctrl+F) Python.exe, and change the path to default Python interpreter that one wants to use. Python installed by Anaconda can be found in Anaconda's folder in C:\ProgramData (if installation was for all users, if not its probably in some other folder in C:\Users\[User].
As for the other part of the question, I'm not sure but I think packages have to be re-installed in the virtual environment, unless you know how to copy the files one by one. Also, it's important to be careful with the version compatibility. In my case, the two Python installations are different versions, so it might not work the trick to copy the files. Other option is to change where the interpreter runs; if in that folder the packages are installed, the installation will succeed. You can also change Python's path to find packages; but that is something that must be done programatically and is not very handy to have to be running those lines of code each time.
When creating a project (or even when the project is already created) you can choose to change the interpreter to Anaconda's Python, even if you are not using conda as a package manager, but virtualenv by Python. That'd be the trick for me. Aditionally, PyCharm also natively integrates package installation into the virtual environment in a GUI menu.
If anyone has a better answer/explanation, I'm looking forward to getting to know it, but in the meanwhile that is the conclusion I have arrived to.
Installed MacVim on my Yosemite 10.10.2 Macbook Pro today from http://www.macupdate.com/app/mac/25988/macvim
The problem is that no editor window(s) are visible. If I open a file using the menu, there's simply no effect: no editor window appears. It's not hidden behind other windows, it's not listed in the Windows menu, it's just entirely undisplayed.
Strangely, the file will appear in the MRU list, though. So this renders the entire editor completely useless. Should I just build gvim myself? Is this app actually being maintained by anyone?
I'd read some answers which suggest running:
brew install macvim
... does the trick.
You might want to try that first.
What worked for me...
However, this didn't work for me because although it updated my macvim, the one being linked to in the /Applications folder was not the version being updated by brew.
So, here are the steps I had to take.
Quit MacVim if open.
Delete the MacVim file in /Applications.
In the terminal, run:
brew install macvim --override-system-vim
Run (this will add the link to your Applications file):
brew linkapps macvim
I can't be sure every step above is required, or that the --override-system-vim flag is required, but I can tell you that doing the above steps worked for me.
Hope this helps.
It looks like MacVim development has been moved to a new repository (and maybe a different group of developers?):
https://github.com/macvim-dev/macvim
This repo has had changes applied to fix MacVim's graphical problems under Yosemite. (This is the same location that brew's macvim formula currently pulls its source from, which is why MacVim works on Yosemite when installed via brew.)
They also have a set of precompiled binary releases:
https://github.com/macvim-dev/macvim/releases
The latest ("snapshot 76") has worked fine for me in Yosemite so far. You just need to download the .tbz archive, double-click it to unpack to a folder, then drag the MacVim.app icon to Applications -- much easier and less invasive than installing a whole package management system and build environment! :)
Note: I had to execute a command given in another StackOverflow answer to correct a rendering glitch seen in full screen mode for snapshot 76:
$ defaults write org.vim.MacVim MMNativeFullScreen 0
I got the same problem today.
The solution:
mv ~/.vimrc ~/.vimrc_bak
It looks like there is something wrong with my .vimrc file.
I was having the same issue, and one of the answers in here helped me, but not for the reason explained so I thought this might be useful for others.
Some plugins might depend on the version of vim, and may work in version 7 but not in version 8, when you install MacVim this could be version 8, and the terminal vim version might be 7, both will use the same .vim folder and .vimrc to load the plugins and configuration, when you open the vim from terminal it might still work because the plugins were depending on vim version 7, but when you try to execute MacVim it will try to load the plugins using version 8 and then it will crash, the reason some of the answers worked it's because they are replacing the system vim, therefore MacVim and vim will be in the same major version, if you have upgraded from the previous version the best you can do it's to clear up the plugins folder and then load MacVim or vim and check that everything is working, then start applying the plugins one by one checking that they are not breaking vim. At least with this method I found that one of the plugins was not working as expected and removing it solved the "MacVim" issue.
In summary:
- move your .vim as .vim_bak
- move your .vimrc as .vimrc_bak (suggested by #hai feng kao)
And test if this solves the issue, if that's the case then a plugin is breaking your installation and you will need to activate some and figure out which is the one that causes the issue.
Hope this helps to others, I've followed a lot of these recommendations without success until I decided to upgrade vim (terminal) and this started to break as well, that pointed me in the right direction.
Again hope this saves some hours for some.
I had the same symptom with MacVim launching with no window and command-N doesn't start any a new one. brew re-install didn't help.
It turned out there was another instance of macvim installed on my system somehow, in the Downloads folder. I found out by clicking "MacVim" --> "About MacVim" and it was a version from 2014. I found the instance and deleted it.
I created an alias for the newly installed version and copied that into Applications folder so spotlight search can find the new one. That solved my problem.
I had this problem upon updating from MacOS 10.12.5 to 10.12.6.
I uninstalled MacVim by moving it to the trashcan and downloading it again.
I would guess that the new version fixed whatever issue it had with the new operating system.