I am not able to install pywinauto in python 2.5.1
Version 2.5.1 don't have pip.
I tried to copy paste pywinauto from 2.7.1 but didn't work.
from the pywinauto documentation
Installation
(Python 2.5 and before is not supported)
So it's time to upgrade. Python 2.5 now belongs to retrocomputing.
The latest pywinauto is not compatible with Python 2.5 because statements like except Exception as exc: won't work in Py2.5 (they are required for Py3.x compatibility and work for Py2.6+). Though you have chances with pywinauto==0.4.2 and before. 0.4.2 can be downloaded here (see "Releases" tab in the repo): https://github.com/pywinauto/pywinauto/archive/0.4.2.zip
You need to unpack it and run C:\python25\python.exe setup.py install
Related
I have downloaded Anaconda 64 bit with Python 2.7 on my compter which works with Windows.
I also downloaded PyQt4 version 4.11.4.
However, when I run my code, I have this :
RuntimeError: the sip module implements API v9.0 to v9.2 but the PyQt4.QtGui module requires API v11.3
I tried to update the sip module, but I can't go further than version 4.18 due (I think) to the version of Python I use. However, I really need to use Python 2.7 since the code that I'm trying to run is old and written in Python 2.
I found out that PyQt4 version 4.9.6 requires a API version 9.1, so it would be supported by the sip module I have.
My problem is that only found that version of PyQt4 in zip file or in tag.gz file and I only know how to install .whl file (with the "pip install" in the anaconda prompt).
I was wondering if someone could please explain me how to install a zip or tag.gz file or if there is a web site that I could use to transform the zip (or tag.gz file) into a .whl file.
I have python 2 installed on my machine. I want to use the skbio module for some part of my code. I tried installing skbio (pip install scikit-bio) but it says it does not support python 2 it is only available in python 3. I even tried importing skbio from future in my code but it did not work. Is there any way out I can install and use skbio module for my python 2 version?
Thanks in advance.
scikit-bio dropped Python 2 support in version 0.5.0 and is now only compatible with Python 3.4+. Versions 0.4.2 and earlier are Python 2/3 compatible, so you could try out an older version:
pip install scikit-bio==0.4.2
I've just installed Python 3.5 to experience its functionality. The problem is that all the modules I use in my daily programming have been installed and run very well on it except Matplotlib. I installed it via pip and never faced any errors while installing, but when I wanted to import it, the error saying, DLL load failed: The specified module could not be found. popped up.
What's the matter with Python 3.5, or Matplotlib?
Uninstall the module using pip uninstall matplotlib then install it again using http://matplotlib.org/downloads.html
Obtain the .exe file that best fits your machine, in my case it would be matplotlib-1.4.3.win-amd64-py3.4.exe. This will be a more complete version of matplotlib for windows rather than using pip.
I would also consider rolling back to Python 3.4 unless you absolutely need 3.5. There shouldn't be a compatibility issue between 3.4 and 3.5 for Python, but as far as matplotlib it's been tested with 3.4, but if you run through problems on 3.5 I would roll back.
If you have Python 3.5 you should install MS's Redistributable DLLs to make matplotlib working on Windows... In my case, no need to reinstall matplotlib even...
Try this example without. If error appears install that and try with it (you must log in MS site and download version for arch you using - i tested x86 only, Windows 7, Python 3.5).
That case is included in matplotlib install documentation!
Remember, you should always read documentation before you ask!
How to install mechanize in python 3.4 on windows 8.1
I tried pip install mechanize
It had a few syntax errors in installation but finally it said Completed Successfully
Still import mechanize doesn't work
It says No module named 'mechanize'
From mechanize FAQ :
Which version of Python do I need?
Python 2.4, 2.5, 2.6, or 2.7. Python 3 is not yet supported.
But you could have a look to this other recent post from SO I get an error in python3 when importing mechanize if you want to test the version in developpement for python3.
By the way, did you try googling "mechanize python3" before asking on SO ?
If you have both python 2.X.Y and 3.z on your machine you will also have both pip and pip3 you may have installed machanize for python 2 rather than python 3.
Try:
pip3 install mechanize
try running
py -m install mechanicalsoup
it worked on my Windows 10 with Python 3.6
Good Luck
My system: Mac OS X 10.6.8, gcc 4.2, python 2.7, xcode 3.2.3
I use python 2.7 and I got error when tried to do: import objc, it returns: ImportError: No module named objc.
It looks like the objc module is not there. But actually I have the objc module installed already. Snow Leopard has got pyobjc preinstalled and I have also checked this using python2.6 (I have python 2.7 and 2.6 in my Mac). So if I invoke import objc using python2.6, I got no error which means objc exists and I can use that module without problems ... but if I import using python 2.7, I will got the ImportError: No module named objc error.
Does anyone have any solution? FYI, the python2.6 is coming preinstalled with OS X while 2.7 is manually installed. I've been using the 2.7 for couple of months without problems.
Python C extension modules like objc cannot be re-used between python versions. You'll have to install the objc module for 2.7 separately.
Generally, different python installations (such as 2.6 or 2.7, or 3.2) use separate module import locations, and you normally install extensions per python setup.
In general, packages installed with one python installation are not available to other python installations. You can make them available by messing with sys.path (or by setting PYTHONPATH in your environment) and installing your modules to a common place, however, as pointed out by #MartijnPieters, if it is a C extension, you'll need to re-build the module for python 2.7 (and then you can't put it in a common place). Usually, this is as easy as:
<sudo> python2.6 setup.py install #install for python 2.6
<sudo> python2.7 setup.py install #install for python 2.7
since the command python is generally just a (soft) link to your preferred python installation.
sudo may or may not be necessary depending on where your python implementations live on your path.
This works for pure python modules too by the way. Since the source code generally doesn't take up too much space, this may be a good way to install all your modules if you'll be switching back and forth between python 2.6 and python 2.7.
The same thing goes if you're using easy_install to install your packages:
easy_install-2.6 somepackage
easy_install-2.7 somepackage