Note that there are some explanatory texts on larger screens.

plurals
  1. POPython Install of Dropbox SDK Fails
    primarykey
    data
    text
    <p>I have the same problem as here.</p> <p><a href="https://stackoverflow.com/questions/14596744/dropbox-python-sdk-installation-error-on-windows-7-could-not-create-build">Dropbox Python SDK installation error on Windows 7 (could not create &#39;build&#39;)</a></p> <p>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.</p> <p>Here goes...</p> <p>I installed Python 2.7, then downloaded and tried to run setup.py of the Dropbox Python SDK.</p> <p>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...</p> <pre><code>C:\Python27\dropbox-python-sdk-1.5.1&gt;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&gt; </code></pre> <p>What have I done wrong? I know it hasn't installed because the Dropbox module isn't there. </p> <p>I'm using Windows Server 2008 64bit if that helps.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload