I want to use the mlbox package (see here) which works with a 64-bit version of Python only. But I have a 32 bit version of Ubuntu, can I install a 64-bit python without any problem ?
PS : I've already installed 32-bit anaconda.
No, 64-bit software requires a 64-bit operating system, or at least a 64-bit kernel.
You may be able to run 64-bit Anaconda in a virtualization environment, or you may be able to upgrade just your kernel to 64-bit (seems unlikely to me though). Here are a couple of links with more info:
https://unix.stackexchange.com/questions/118343/run-64-bit-app-on-32-bit-system-ubuntu
https://superuser.com/questions/111975/can-i-run-64-bit-executables-on-a-32-bit-linux
I am pretty sure it won't work, or if it will (which is less likely) it will have bunch of bugs and have some issues. I would not recommend doing it, because it is just a waste of time.
what I recommend you doing is download the Oracle the Virtualbox (click here)
and try running the 64-bit version of your Linux Ubuntu and try running the Python. Basically try doing this whole process through the virtual machine.
Good Luck with your project !!! I hope I helped you.
Related
I am trying to install Miniconda on my new iMac. I have installed Miniconda on an older macOS system before with no problems, but I am having difficulty with this new computer/system.
The computer is an iMac with the Apple M1 chip running macOS Big Sur (version 11.3).
I downloaded the latest miniconda installer and ran the following code: bash Miniconda3-latest-MacOSX-x86_64.sh
This results in the following warning:
WARNING:
Your operating system appears not to be 64-bit, but you are trying to
install a 64-bit version of Miniconda3.
Are sure you want to continue the installation? [yes|no]
I am not sure why it is saying that I don't have a 64-bit system - my understanding is that starting with macOS Catalina, everything should be 64-bit (but may be I am wrong?).
I searched around on the internet, but didn't find a solution, so thought I would try installing it anyway just to see what happens. It does not complete the install. I followed the prompts, but at some point, you get this:
[/Users/jenniferweinert/miniconda3] >>>
PREFIX=/Users/jenniferweinert/miniconda3
Unpacking payload ...
Miniconda3-latest-MacOSX-x86_64.sh: line 411: /Users/jenniferweinert/miniconda3/conda.exe: Bad CPU type in executable
Miniconda3-latest-MacOSX-x86_64.sh: line 413: /Users/jenniferweinert/miniconda3/conda.exe: Bad CPU type in executable
Most of what I have found about issues with miniconda (or anaconda) and macOS (Catalina or Big Sur) relates to the differences between bash and zsh and the two extra lines of code that you need to activate miniconda/anaconda. But I can't even get to that point because I cannot get Miniconda installed!
I was able to install home-brew and then tried the silent installation. But that ended up at the same point, unable to install due to the bad cpu type in executable.
Someone mentioned to me that this might be due to the M1 chip in this computer, but did not have a work-around or solution to suggest.
If anyone can offer any help with this, I would really appreciate it! Also, if there is any additional information that I should provide in order for you to help, just let me know.
Thank you!
I encountered the same problem with the downloaded ".bash" script. But the ".pkg" installer worked fine.
https://docs.conda.io/en/latest/miniconda.html
In fact, it is a OS default problem. That problem means that your Mac is not seeing Rosetta at first because you haven't used an application made for Intel chips yet.
To solve the problem, just initialize the .pkg, so that Mac asks you to install Rosetta (Just a one life thing).
https://support.apple.com/en-us/HT211861
Install Rosetta, exit installation from the .pkg and then you can bash Miniconda3-latest-MacOSX-x86_64.sh as usual.
You can also continue the installation with the .pkg installer, but I don't personally like it because it puts it into the /opt/miniconda3 folder by default and it doesn't asks you about the conda init script written into the .zshrc file.
This is important if you want to have both miniconda and miniforge as two separated instances.
https://www.youtube.com/watch?v=w2qlou7n7MA&list=RDCMUCR1-GEpyOPzT2AO4D_eifdw&index=1
Let us hope M1 chip developers keep working hard so that we will only use miniforge in the future to take all the juice from the M1 chip with GPU available!
I ran into the same issue. Make sure you download "Miniconda3 macOS Apple M1 ARM 64-bit bash" instead of "Miniconda3 macOS 64-bit bash" from the installer webpage.
Better than installing Miniconda, it is recommended to install ...Miniforge.
Miniforge is a conda implementation from the conda-forge channel,
and you can get installers for several platforms including Apple Silicon on this miniforge github.
Miniforge searches automatically for package wheels which are dedicated to Apple Silicon.
I just installed the latest version of Python from enter link description here. I expected the installer to query my CPU at installion time and install the a 64-bit version by default, since my CPU machine is 64-bit Intel version.
After installation, I am a unclear by the version data that shows in IDLE when I start Python:
Python 3.8.2 (tags/v3.8.2:7b3ab59, Feb 25 2020, 22:45:29) [MSC v.1916 32 bit (Intel)] on win32
I want to use highest performance Python for machine learning, database, and number crunching applications.
There is no "64-bit only" version on Python.org website. The only kit available is named Windows x86-64 executable installer Windows for AMD64/EM64T/x64.
Does the Python installer install both the 32-bit and 64-bit API? This is not reflected in the version information that is displayed.
Am I asking the wrong question, because the 64-bit and 32-bit APIs are both installed, and just the version displayed is not complete? How does Windows or Python know to switch to the 64-bit API for libraries like Numpy, Numba, etc. that work best with 64-bit code?
Is there a way to explicitly start the 64-bit version?
When should I do this explicitly versus letting Windows launch the default 32-bit version?
you should only download and install the Windows x86-64 executable installer Windows for AMD64/EM64T/x64. if you want 64bit. However do NOT expect python to be super fast, as a dynamic typing language, it will be at least 100 times slower than static typing language such as C/C++ or Java.
If you want your numpy/pandas/sklearn to be as fast as possible, you should focus on optimizing your workflow, don't commit to unnecessary task. Or you can check out intel's python distribution if you're on Intel CPU. Or explore other multi-process pandas solution when on a multi-core AMD cpu.
I have been using conda as a package manager for a lot of my work and its really helped keep the environments of multiple people in check with both Python and binary packages. Its been all sunshine and rainbows while all of my users have been on 64-bit Linux machines.
Now I need to support a handful of 32-bit machines. Is there any way to build 32-bit versions of my packages on my 64-bit machine?
I've found this answer on SO, How to compile a 32-bit binary on a 64-bit linux machine with gcc/cmake but I can't figure out how to get it to compile and upload both 32 and 64 bit versions.
conda assumes that the entire installation is 64-bit, so the first thing you'll need to do is create a separate Miniconda installation for 32-bit building. Then build your recipe. If the package links against any system libraries, you'll need to have the 32-bit versions installed. I personally find it easiest to build 32-bit packages on a 32-bit VM, as then you know that everything is 32-bit, but building on a 64-bit machine is possible and it should work (although I would recommend testing the package on a 32-bit machine).
I've been looking around the internet for days now and cannot find a solution to my problem. I've learned all the basics to programming in Python 2.7 and I want to add Pip to my copy of 2.7. I found the link to download the unoffical 64-Bit installer (www.lfd.uci.edu/~gohlke/pythonlibs/), but when I downloaded it and ran it, it said I needed to have Python 2.7 (which I do) and it couldn't find it in the registry. I went to Pip's website and downloaded the official Windows installer and unpacked it using WinRAR.
I then tried opening Command Prompt and changed the directory to where the get-pip.py is located and running get-pip.py install but it says it failed to install.
I am completely lost and really need detailed and clear help. Please answer!
It doesn't matter what kind of machine you have. You can run 32-bit Windows on a 64-bit machine. And you can run 32-bit Python on 64-bit Windows.
If you have 32-bit Python, you need to install 32-bit pip. (Or you need to switch to 64-bit Python.)
From your description, you most likely have 32-bit Python on 64-bit Windows, and tried to use a 64-bit pip.
PS, if you want to install it manually instead of using Gohlke's installer, nobody can help you debug your problem based on "it says it failed to install". It produces a lot more output than that, and without that output, it's impossible to know which of the billion things that could possibly go wrong actually did.
PPS, just installing pip is sufficient to install any pure-Python packages. But if you want to install packages that include C extensions, you will need to set up a compiler (either MSVC, or MinGW/gcc), as explained in the pip documentation.
I just switched my python installation to the lovely Anaconda and am trying to get the packages I use often installed and working again. Unfortunately I'm having some problems getting h5py to work - the Python 2.7 installer available from h5py.org seems not to work. After the first screen, an error message pops up saying that Python Version 2.7 is required but was not found in the registry. Python 2.7 is the only version I have on this computer (specifically 2.7.5, Anaconda 1.8.0 (64-bit)). Has anyone else experienced this issue? Some people in a long-forgotten thread were worried it could be a 32 vs 64-bit python issue, but nothing ever came out of that. Any ideas / will I also need a 32-bit python installation for this to work?
Download 64-bit h5py from here and try again
http://www.lfd.uci.edu/~gohlke/pythonlibs/#h5py
(as recommended by http://www.h5py.org/dl/)