G'day
AIM: i'm trying to use Drive API with Python 2.7.3 to read and write files.
PROBLEM: is with the install of "easy_install" (ironic, i know)
1. I have enabled the drive api
2. I can see that the google client library must be there because the files are in c:/program files/python/scripts
BUT when i type easy_install into cmd window it is not recognised
-i have tried running the file: easy_install-2.7.exe
-i have updated the directory path in my computer/properties/advanced/ to include C:/Program Files/Python/Scripts
- i have downloaded the PyWin32 installer (i am running XP) for Python 2.7
http://stackoverflow.com/questions/4016151/how-to-use-pythons-easy-install-… mentions that "you should see that your winpexpect package has been installed correctly." winexpect. where is this located? how is this done?
thanks!
Dav-o
Hi All,
This is driving me nuts, I hope someone can help.
So, pre-amble, I'm on a Mac, I have a few python installations, the ones
in play here are:
buzzkill:xlutils chris$ which python
/Library/Frameworks/EPD64.framework/Versions/Current/bin/python
buzzkill:xlutils chris$ which python2.6
/usr/local/bin/python2.6
buzzkill:xlutils chris$ which python2.7
/Library/Frameworks/EPD64.framework/Versions/Current/bin/python2.7
The buildout I'm working with is here:
https://github.com/python-excel/xlutils/blob/master/buildout.cfg
My python2.7 has a site-packages xlrd (it's EPD, which includes a bunch
of packages), so I'm using python2.6 on this machine, since it doesn't
(it's a plain source install on python).
Okay, so, as you'll see from github above, I have the latest
bootstrap.py, and the initial bootstrap looks fine:
buzzkill:xlutils chris$ python2.6 bootstrap.py
Downloading
http://pypi.python.org/packages/source/d/distribute/distribute-0.6.35.tar.gz
Extracting in /var/folders/m6/tsd59qsj7pd_lldh4mhwh6kh0000gn/T/tmpxnVlCD
Now working in
/var/folders/m6/tsd59qsj7pd_lldh4mhwh6kh0000gn/T/tmpxnVlCD/distribute-0.6.35
Building a Distribute egg in
/var/folders/m6/tsd59qsj7pd_lldh4mhwh6kh0000gn/T/tmpg4hxVn
/var/folders/m6/tsd59qsj7pd_lldh4mhwh6kh0000gn/T/tmpg4hxVn/distribute-0.6.35-py2.6.egg
buzzkill:xlutils chris$ cat bin/buildout
#!/usr/local/bin/python2.6
import sys
sys.path[0:0] = [
'/Users/chris/buildout-eggs/distribute-0.6.35-py2.6.egg',
'/Users/chris/buildout-eggs/zc.buildout-2.1.0-py2.6.egg',
]
import zc.buildout.buildout
if __name__ == '__main__':
sys.exit(zc.buildout.buildout.main())
Okay, so now try running that buildout:
buzzkill:xlutils chris$ bin/buildout
Upgraded:
distribute version 0.6.26;
restarting.
Generated script '/Users/chris/LocalGIT/xlutils/bin/buildout'.
Develop: '/Users/chris/LocalGIT/xlutils/.'
Develop: '/Users/chris/LocalGIT/xlutils/../xlrd'
Traceback (most recent call last):
File "/var/folders/m6/tsd59qsj7pd_lldh4mhwh6kh0000gn/T/tmpwnpB08",
line 13, in <module>
exec(compile(open('/Users/chris/LocalGIT/xlutils/../xlrd/setup.py').read(),
'/Users/chris/LocalGIT/xlutils/../xlrd/setup.py', 'exec'))
File "/Users/chris/LocalGIT/xlutils/../xlrd/setup.py", line 18, in
<module>
from xlrd.info import __VERSION__
ImportError: No module named info
While:
Installing.
Processing develop directory '/Users/chris/LocalGIT/xlutils/../xlrd'.
An internal error occured due to a bug in either zc.buildout or in a
recipe being used:
<snip>
File
"/Users/chris/buildout-eggs/zc.buildout-2.1.0-py2.6.egg/zc/buildout/easy_install.py",
line 129, in call_subprocess
% repr(args)[1:-1])
Exception: Failed to run command:
'/usr/local/bin/python2.6',
'/var/folders/m6/tsd59qsj7pd_lldh4mhwh6kh0000gn/T/tmpwnpB08', '-q',
'develop', '-mxN', '-d',
'/Users/chris/LocalGIT/xlutils/develop-eggs/tmpUg8rV8build'
Okay, so, a few comments:
- "upgrading" to distribute version 0.6.26 from 0.6.35. Whu?!
- The xlrd in /Users/chris/LocalGIT/xlrd certainly does have an info module.
Now the really crazy bit:
buzzkill:xlutils chris$ cat bin/buildout
#!/usr/local/bin/python2.6
import sys
sys.path[0:0] = [
'/Users/chris/buildout-eggs/zc.buildout-2.1.0-py2.6.egg',
'/Library/Frameworks/EPD64.framework/Versions/7.3/lib/python2.7/site-packages',
]
import zc.buildout.buildout
if __name__ == '__main__':
sys.exit(zc.buildout.buildout.main())
Come again?! Why is site-packages from a *different python installation*
ending up in bin/buildout?
Any help here would be very gratefully received...
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
Hi,
I spend some more time on bandersnatch and I'm ready for a stable
release, I guess.
Updates
------------
* Add a specific user agent to XML-RPC and plain HTTP calls
* Add a specific user agent to the logging to support debugging
* Provide a default (10s) network timeout and a config option to customize
* Clean up README
PIP
---
I'd be happy to cut a release now. Holger Krekel asked me whether I
could ensure that bandersnatch is pip installable. Looking through the
PIP documentation I don't see how I can make a simple "pip install
bandersnatch" repeatable.
Especially if someone would run a public mirror I would prefer if they
would use an installation method that makes their deployment
repeatable. From my own experience and background I would prefer
buildout in the following style:
$ hg clone https://bitbucket.org/ctheune/bandersnatch
$ cd bandersnatch
$ hg co 1.0
$ virtualenv-2.7 .
$ bin/python bootstrap.py
$ bin/buildout
$ bin/bandersnatch
Thoughts?
Contacting mirror owners
----------------------------------
All this work is directed towards getting the existing official mirrors
back to a "green bar" situation soon. Can someone help me contact the
existing mirror owners to convince them to switch tools?
Also, I'd be happy to run a couple vhosts around the world to extend
the network if some people throw in some money (gittip?)
Cheers,
Christian
Hi,
when developing bandersnatch I saw some checksum errors for the md5sums
of downloaded package files that I didn't understand.
I just saw another one and just want to check back whether this is
true: I can go to PyPI, delete a package version, and upload a
different file later.
True?
This would explain that I can see a file that I downloaded successfully
changing it's hash over time.
Feels like a bad idea to me, but I guess this is part of the "PyPI
doesn't have an oppinion" deal …
Christian
Some of the pypa people have been discussing beginning a "packaging-user"
mailing list.
- It would be open to *any* packaging or install user issues.
- It would be on python.org
- pip/virtualenv would use it instead of our "virtualenv" list
- Other projects could(would) use it too: Setuptools (old and new),
Distribute, wheel, buildout, bento? etc...
I think python users would appreciate the simplicity of this, and the
support would be better too I think.
distutils-sig would maintain it's current focus as a place for development
discussions.
thoughts?
Marcus
I'm trying to use buildout to pull in 4 github repositories and combine
their wsgi applications together using paste's urlmap. A few things aren't
working the way I expect and so I'm looking for some more information:
This is my buildout.cfg:
https://github.com/sontek/notaliens.com/blob/master/buildout.cfg
1. I had to declare a [pyramid] section that pulls in Pyramid with the
zc.recipe.egg recipe so that it would drop the entry_point scripts in the
generated bin/ folder. Is there a way for it to do this from dependencies
declared in my install_requires in setup.py rather than being declared in
the buildout?
2. The 2nd problem is after I run buildout, I'm not able to import
paste.deploy:
I see the egg in my sys.path:
bin/py
>>> import sys
>>> sys.path
<cut>
'/home/sontek/code/test_notaliens/
notaliens.com/eggs/PasteDeploy-1.5.0-py2.7.egg',
but if I try to import from it:
>>> from paste.deploy import loadserver
Traceback (most recent call last):
File "<console>", line 1, in <module>
ImportError: No module named deploy
PasteDeploy is defined as a dependency and gets pulled in properly but for
some reason the interpreter isn't seeing it.
any ideas?
