I have the same problem as here.
Dropbox Python SDK installation error on Windows 7 (could not create 'build')
The user didn't say how they fixed the issue (I have tried starting again, and reinstalling Python). I asked the user to elaborate and my post was deleted because I wasn't answering the question. Sorry, I'm new here. But re-posting seems counter intuitive to me.
Here goes...
I installed Python 2.7, then downloaded and tried to run setup.py of the Dropbox Python SDK.
It asked me to add the setuptools, so I did, and then tried to install the Dropbox setup.py from a CMD. After which I got the below...
C:\Python27\dropbox-python-sdk-1.5.1>setup.py install
running install
running bdist_egg
running egg_info
writing dropbox_python_sdk.egg-info\PKG-INFO
writing top-level names to dropbox_python_sdk.egg-info\top_level.txt
writing dependency_links to dropbox_python_sdk.egg-info\dependency_links.txt
reading manifest file 'dropbox_python_sdk.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'dropbox_python_sdk.egg-info\SOURCES.txt'
installing library code to build\bdist.win-amd64\egg
running install_lib
running build_py
creating build
error: could not create 'build': Cannot create a file when that file already exists
C:\Python27\dropbox-python-sdk-1.5.1>
What have I done wrong? I know it hasn't installed because the Dropbox module isn't there.
I'm using Windows Server 2008 64bit if that helps.
Answer as per piokuc's comment. He/She did not mark an answer (for quite some time) so I am leaving it here for others to find.
"Remove the build directory you see complaints about. – piokuc"
I found that trying to install the Dropbox python module without 'Easy Install' if fails, leaving the Dropbox module install half finished. Simply delete the file in question and start again.
Related
First of all, I am running Python 2.7.5 on a Mac. I am trying to install a package and can't get it to work despite different approaches. The package is called python-fs-stack and is available here. https://pypi.python.org/pypi/python-fs-stack. I tried pip install python-fs-stack, sudo pip install python-fs-stack, easy_install python-fs-stack, sudo easy_install python-fs-stack and nothing worked. I then downloaded the package and got an error about a README.rst not being found. I commented out this line in the setup.py file and re-ran it. It got a lot farther, but then there was another error. Here is the output:
>>sudo python /Downloads/python-fs-stack-0.2/setup.py install
running install
running bdist_egg
running egg_info
writing python_fs_stack.egg-info/PKG-INFO
writing top-level names to python_fs_stack.egg-info/top_level.txt
writing dependency_links to python_fs_stack.egg-info/dependency_links.txt
warning: manifest_maker: standard file 'setup.py' not found
error: package directory 'familysearch' does not exist
I would really like to be able to get this package up and running, but I am at a loss. What should I try?
I'm fairly new to Pydev in Aptana Studio 3, but thanks to some great tutorial videos I've got Python 3.3 running in Pydev just fine on Windows 7.
My reason for using Aptana/Pydev is for all the linty code-tidying goodness, but the bit of code I've been given which I need to refactor uses the Rpi.GPIO module.
Works just find when I apt-get the module on the Pi, of course, but I need to do some massive tidying on Windows, then I can go back to IDLE3 on the Pi later.
It looks like you can't just dump the folder in a Pydev path and expect it to run, so I read the INSTALL readme, and the following thing happened:
D:\RPi.GPIO>python setup.py install
running install
running bdist_egg
running egg_info
writing dependency_links to RPi.GPIO.egg-info\dependency_links.txt
writing RPi.GPIO.egg-info\PKG-INFO
writing top-level names to RPi.GPIO.egg-info\top_level.txt
reading manifest file 'RPi.GPIO.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'RPi.GPIO.egg-info\SOURCES.txt'
installing library code to build\bdist.win-amd64\egg
running install_lib
running build_py
running build_ext
building 'RPi.GPIO' extension
error: Unable to find vcvarsall.bat
So if anyone knows how to simply get Pydev to recognise this library, I'd be very grateful.
The error:
error: Unable to find vcvarsall.bat
is happening because you don't have Visual Studio C++ compiler installed which is needed to compile the code.
Also, checkout this answer for more info.
I was hoping to get some help. I am trying to install the Python SDK for Dropbox on Windows 7 (have Python 2.7.3 installed). Following the instructions in the readme file, I ran the following on the command prompt: "python setup.py install -f". I received the following error. Any thoughts? Many thanks in advance.
running install
running bdist_egg
running egg_info
writing dropbox_python_sdk.egg-info\PKG-INFO
writing top-level names to dropbox_python_sdk.egg-info\top_level.txt
writing dependency_links to dropbox_python_sdk.egg-info\dependency_links.txt
reading manifest file 'dropbox_python_sdk.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'dropbox_python_sdk.egg-info\SOURCES.txt'
installing library code to build\bdist.win32\egg
running install_lib
running build_py
creating build
error: could not create 'build': Cannot create a file when that file already exists
Sorry...I figured it out. I guess I goofed something up in the download/extraction process as I started from scratch and it worked this time around. 8)
I'm trying to start a Django app on Heroku using Windows and I'm getting stuck on the following error when I try to pip install psycopg2:
Downloading/unpacking psycopg2
Downloading psycopg2-2.4.5.tar.gz (719Kb): 719Kb downloaded
Running setup.py egg_info for package psycopg2
Error: pg_config executable not found.
Please add the directory containing pg_config to the PATH
or specify the full executable path with the option:
python setup.py build_ext --pg-config /path/to/pg_config build ...
or with the pg_config option in 'setup.cfg'.
Complete output from command python setup.py egg_info:
running egg_info
creating pip-egg-info\psycopg2.egg-info
writing pip-egg-info\psycopg2.egg-info\PKG-INFO
writing top-level names to pip-egg-info\psycopg2.egg-info\top_level.txt
writing dependency_links to pip-egg-info\psycopg2.egg-info\dependency_links.txt
writing manifest file 'pip-egg-info\psycopg2.egg-info\SOURCES.txt'
warning: manifest_maker: standard file '-c' not found
I've googled the error and it seems you need libpq-dev python-dev as dependencies for postgres under Python. I also turned up a link that says you gt into trouble if you don't have the postgres bin folder in your Path so I installed Postgres manually and tried again. This time I get:
error: Unable to find vcvarsall.bat
I am still a python N00b so I am lost. Could someone point me in a general direction?
You can use Cygwin and install all the dependencies, but I went through that issue last week and then I realized it was far easier to use a Virtual Box with Ubuntu as my Guest OS. I still did the development on Windows but used Ubuntu just to communicate/push to heroku
I found the answer to my problem. I believe the problem is that pip is looking to compile the dependency from source. The solution is to find a link to pre-compiled version of the dependency. You can then pass this link to the easyinstall library installed in your virtualenv. Easyinstall will download and install the pre-compiled version of the dependency.
I am running into a bizarre problem where I try to install my python package (using setuptools) on a Linux system and it tries to install pywin32 as a dependency. This only happens if I run it from a specific directory. If I move the whole tree to a different directory, it installs fine.
My setup.py does reference pywin32 for win32 platforms, but even when I remove this it makes no difference. I've also removed all the other requirements without any change in behavior. My setup.py has nothing in it other than setuptools initialization and a call to setup().
I have a virtualenv active and have tried switching to a new clean virtualenv without a change in behavior. I see the following when I run setup.py develop:
python setup.py develop
running develop
running egg_info
deleting foo.egg-info/requires.txt
writing foo.egg-info/PKG-INFO
writing top-level names to foo.egg-info/top_level.txt
writing dependency_links to foo.egg-info/dependency_links.txt
reading manifest file 'foo.egg-info/SOURCES.txt'
writing manifest file 'foo.egg-info/SOURCES.txt'
running build_ext
Creating /home/user/foo-env2/lib/python2.7/site-packages/foo.egg-link (link to .)
foo 1.0 is already the active version in easy-install.pth
Installed /home/user/magicdirectory/magic
Processing dependencies for foo==1.0
Searching for pywin32
Reading http://pypi.python.org/simple/pywin32/
Reading http://sf.net/projects/pywin32
Now, I may have accidentally tried to install a win32 egg of this package at some point, but that was in the original virtual environment and I can't figure out what it could have done to cause this.
How do I debug this? Where else could setuptools be searching for dependencies from?
UPDATE: It appears that it's not the name of the directory that matters, but where it is. If I move the package directory up one level, it will install fine. The directory in question here has been deleted and recreated multiple times so it doesn't appear to be related to anything inside the directory.
Try removing the *.egg-info in the dist develop directory. If that doesn't work, try starting with a fresh, untouched checkout of your code without any of the other setuptools/dist artifacts and see if that reproduces the problem. If it doesn't then you know it's one of the setuptools/dist artifacts that just needs to be cleaned up.