I want to use a new feature of httpie. This feature is in the github repo https://github.com/jkbr/httpie but not in the release on the python package index https://pypi.python.org/pypi/httpie How can I install the httpie package from the github repo? I tried pip install https://github.com/jkbr/httpie But I got an error ‘could not unpack’ In Nodejs, I … Read more
There is a --user option for pip which can install a Python package per user:
When I try to run app.py (Python 3.3, PyCrypto 2.6) my virtualenv keeps returning the error listed above. My import statement is just from Crypto.Cipher import AES. I looked for duplicates and you might say that there are some, but I tried the solutions (although most are not even solutions) and nothing worked.
we are trying to install couple of python packages without internet.
OS X (Mavericks) has Python 2.7 stock installed. But I do all my own personal Python stuff with 3.3. I just flushed my 3.3.2 install and installed the new 3.3.3. So I need to install pyserial again. I can do it the way I’ve done it before, which is:
Is there a way to upgrade the version of python used in a virtualenv (e.g. if a bugfix release comes out)?
I want to understand what is considered the correct minimalist way to use setuptools with a “src/ layout” in a way that dispenses using src. prefix in imports?
I have tried to set up a python development environment at my work place to create some basic applications. I can’t seem to get pip to work, for example I type in pip install numpy and get the following error message:
I’ve come across situations where a current version of a package seems not to be working and requires reinstallation. But pip install -U won’t touch a package that is already up-to-date. I see how to force a reinstallation by first uninstalling (with pip uninstall) and then installing, but is there a way to simply force an “update” to a nominally current version in a single step?
I have dependency_links in my setup.py: