I've read that there's a nice text-to-speech package called pyttsx that can be included in my Python scripts. As soon as I try to install pyttsx things start falling apart fast. pyttsx is for Python 2.6 (2.7 maybe?) not 3.3. I have 2.7 and 3.3 (also Portable Python 2.7 and 3.2) installed but I can't get setuptools or easy_install to work. I got distribute partly installed but I'm might have seen some errors at the end of its installation so I'm not sure it's working and it won't install pyttsx anyway. There's a Windows .exe program that will let you install Python packages but it won't work for 64-bit Python. I've been searching for answers for days can can't come up with anything specific enough.
How do I install Python packages with 64-bit Python 3.3 on 64-bit Windows 7, or is that even possible?
Best source ever!
this man is a wicked fellow.
With distribute installed, launch the python.exe you want to use.
From within python interactive, run the following code:
from setuptools.command import easy_install
easy_install.main(["-U", "package"])
Substitute "package" for whatever you wish to install.
Related
I'm aware that Python 2.7 should not be used or upgraded as macOS comes with Python 2.7 for some pre installed software packages.
My question plainly is: Should the Python 3 version that comes with macOS not be used/upgraded?
For clarification I know Python 3 technically doesn't come pre installed like 2.7 does. According to this a clean installation of macOS will come with /usr/bin/python3 that is really just a stub for installing the command line developer tools, which includes and will install python3. I did go ahead and install the command line developer tools, therefore had Python 3.8.9 (at least this is what I had on a clean install of Monterey 12.1).
The reason for my question is that I wanted the newest version of Python 3 (3.10.1). So I installed it directly from python.org and used their installer (I did not use Home-brew or anything like that). After doing this 'python3 -V' will say 'Python 3.10.1'. This made me pause and wonder "if 2.7 should not be messed with, should that original Python 3.8.9 that came with installing the command line developer tools also not be messed with?"
Im trying to install kivy in my portable python with this installer:
http://www.lfd.uci.edu/~gohlke/pythonlibs/#kivy
(Its a pre-compiled version of kivy)
When executing the file, it says "Python 2.7 version required", but since the python version im using is portable, I guess this is normal.
So my question is, is there a workarround to install a precompiled package in portable python? By somehow registering the portable python installation?
More (maybe innecesary) information:
My guess would be registering portable python in the system (Windows 7
64), but I already tried by changing the "path" enviroiment variable to point all
the required python paths without success.
I cant use the kivy modules to install it by compiling it on my computer because its too hard for me,(cython wont work, or then another of the 7 different modules will give me problems, untill i destroy my python installation. I already destroyed my
previous python installation while doing so, and had to reinstall
windows to get python working again -_-
Thats why I want to migrate
into portable python, but if this is not possible I will just go back
to normal python and install kivy on it...
The Kivy package on windows includes a portable python installation with Kivy installed.
Double click on the kivy.bat.
You will have a console have easy_install and pip available. Compiler is set to Mingw, and cython is already installed. Everything will be installed in the portable installation, not your system installation.
Enjoy :)
Note: if you want to see how we do, just edit the kivy.bat.
I'm working on Mac Os 10.7 (Lion) and I have some questions:
What is the pre-installed version of python on Lion?
I've been working on this computer for some time now, and i've installed lots of software in order to do college work many times I didn't know what I was really doing. The thing is: now I hava on the /Library/Frameworks/Python.framework/Versions/ a folder called "7.0" I'm pretty sure there no python version 7. Is this folder native or a third-part program installation. Can I delete it? (it's using 1 Gb on disk).
Where is located the original python that comes with mac os?
I've choose Homebrew as my package manager, is there a easy way to manage python versions with it?
Lion uses Python 2.7 by default; 2.5 and 2.6 are also available.
/Library/Frameworks/Python.framework does not exist on a stock install of Lion. My guess is that you've ended up with this by installing some application.
The default Python install is primarily installed in /System/Library/Frameworks/Python.framework, although some components are located elsewhere.
Yes - you can brew install python#2 to get a Python 2.7 separate from the system version, or brew install python to get Python 3.7. Both will install to /usr/local, like any other Homebrew recipe.
I think that is Python 2.7 but you can check typing python on a command terminal. It will tell you the version.
I couldn't tell that you can deleting it, because I don't know what it has... can you give more info about it?
Just type "which python" and it will tell you
You should use virtualenv and pip: http://jontourage.com/2011/02/09/virtualenv-pip-basics/
I have three versions of Python on my Mac: 2.6.1 (built-in), 2.5.4 (Google App Engine development), and 2.7.2 (general Python programming).
I installed BeautifulSoup with python setup.py install. However, only 2.7.2 is able to work with it.
How do I install it for 2.5.4 as well?
/path/to/other/python setup.py install
It can be helpful to make aliases for your various system Pythons (e.g. python25, and so on) in your .bashrc.
In regards to changing what python points to from the default system Python, I know that this will work if you alias to a newer version, but it may cause issues with an older version, so be careful (just my $.02).
Set your PYTHONPATH environmental variable to point to the installation you want to install it for, and make sure you're using that version of Python when you run python setup.py install. Something like PYTHONPATH=/usr/lib/python25 /usr/bin/python25 setup.py install.
OS X 10.5.8 came with Python 2.5, and had PyObjC already installed.
I installed Python 2.6 from the python.org site, and PyObjC isn't there.
I can't find a download to install PyObjC on my Python 2.6 install. Is checking out the PyObjC trunk and trying to build it my only choice? Will that work "out of the box"?
Apple includes PyObjC with their Pythons that come with OS X 10.5 and 10.6. It is not part of the python.org installers. But it should be easy enough to install. Just install setuptools to the python.org python 2.6 following the instructions here. Then use easy_install-2.6 (which will have been installed in /Library/Frameworks/Python.framework/Versions/2.6/bin and may already be on your $PATH) to do:
easy_install-2.6 pyobjc==2.2b2
as described here. If you want to live on the bleeding edge, you could try installing directly from the svn repository as there has been a lot of work recently, primarily in support of 10.6.
If that seems like too much work, you could install an older version and all dependencies including python via MacPorts:
sudo port install py26-pyobjc2
You should probably try to build PyObjC from trunk, which will work fine on the official Python 2.6 distribution, but not on Python 2.5. There are quite a lot of fixes in the trunk right now that weren't in 2.2b2, which afaik. is the most current version available through easy_install.
There are some little snags that you may run into when building with py2app on 10.5 + 2.6 + PyObjC 2.2 (which for a lot of reasons is what you should probably do, instead of using the Xcode templates from 10.5 that build differently), especially if you still have Python 2.5 installed somewhere, so you'll probably want to build and install py2app from trunk as well, this particular issue I ran into with PyObjC 2.2 on 2.6 on 10.5 has been fixed by now.
If your goal is to write software that will work on other people's computers, you shouldn't touch the default Python installation. If you simply cannot live without 2.6, then you're responsible for re-creating everything on your own, and that's not going to be a point-and-click process by any means.