requirements.txt

问题 I have a Virtual env for my django project, but when I hit pip freeze , I get what must be a global site package list, includes too many packages, like ubuntu packages and so much irrelevant stuff. This happens whether virtualenv is active or not. My site packages list looks a bit slim too, so I wonder whether venv has been working at all. (env)~/code/django/ssc/dev/env/lib/python2.7/site-packages> ls django Django-1.4-py2.7.egg-info easy-install.pth pip-1.0.2-py2.7.egg setuptools-0.6c11-py2

问题 In the requirements.txt for a Python library I am using, one of the requirements is specified like: mock-django~=0.6.10 What does ~= mean? 回答1: It means it will select the latest version of the package, greater or equal to 0.6.10, but still in the 0.6.* version, so it won't download 0.7.0 for example. It ensures you will get security fixes but keep backward-compatibility, if the package maintainer respects the semantic versioning (which states that breaking changes should occur only in major

问题 I'm installing several Python packages in Ubuntu 12.04 using the following requirements.txt file: numpy>=1.8.2,<2.0.0 matplotlib>=1.3.1,<2.0.0 scipy>=0.14.0,<1.0.0 astroML>=0.2,<1.0 scikit-learn>=0.14.1,<1.0.0 rpy2>=2.4.3,<3.0.0 and these two commands: $ pip install --download=/tmp -r requirements.txt $ pip install --user --no-index --find-links=/tmp -r requirements.txt (the first one downloads the packages and the second one installs them). The process is frequently stopped with the error:

问题 All tests are passing, but in in the end, it gives The command "make html" failed and exited with 2 during . This happens since I started using cache. Initially I just had cache: apt: true directories: - $HOME/virtualenv/python2.7/lib/python2.7/site-packages - node_modules in travis.yml but I also added - $HOME/virtualenv/bin and cleared my cache in master branch before I ran another build. It passed once, but then keeps failing. I cleared the cache multiple times but no avail. 来源： https:/

问题 This question already has answers here : pip: how to install a git pull request (2 answers) Closed 7 months ago . My English is bad. I'm going to state some Python 3 library in requirements.txt , but there is a bug in original version of code. In Pull requests one user commited the new version with bug fix that wasn't merged by Author if it affects something. The link looks like this: https://github.com/ramusus/kinopoiskpy/pull/47/commits/4c888bf4f6b330b115d11fac3e0b8bb177b597bb How should i

问题 I've seen the twiddle-wakka operator (~>) used in ruby's gem file (documentation) to specify the last point version compatible like this: '~> 0.3.1' is satisfied by 0.3.1, 0.3.2, 0.3.3, etc. '~> 0.3.1' is not satisfied by 0.3.0 '~> 0.3' is satisfied by 0.3.1, 0.4.0, 0.5.1, etc. '~> 0.3' is not satisfied by 0.2.0, 0.2.1, etc. I see that there's a >= operator in the requirements.txt that can be used to specify anything better than that, but I'm hoping to avoid any future package updates (major

问题 I am trying to install packages in a python 3.6.3 virtual environment. I keep getting errors. I have tried pip with --ignore-installed flag like: pip install -I -r package-list.txt . Here is part of what I have in package-list.txt . # This file may be used to create an environment using: # $ conda create --name <env> --file <this file> # platform: linux-64 _libgcc_mutex==0.1==main appdirs==1.4.3==pypi_0 asn1crypto==0.24.0==py36_0 beautifulsoup4==4.7.1==py36_1 blas==1.0==mkl bzip2==1.0.6=

问题 I'm using LDTP in my tests and it comes as two different packages for two different platforms: PyAtom on Mac OS; LDTP on Linux. It so happens, that both of them has platform-specific binaries and can't really be installed on other OSes. My question is, how do I make my requirements.txt to install packages dependent on platform? Ideally it should be something like: mac: -e git+https://github.com/pyatom/pyatom.git@1ca0c6a0343000286a328268899d1aab376d8e82#egg=atomac-master linux: ldtp==3.5.0

问题 I have defined a few different Cloud Dataflow jobs for Python in the Google AppEngine Flex Environment. I have defined my requirements in a requirements.txt file, included my setup.py file, and everything was working just fine. My last deployment was on May 3rd, 2018. Looking through logs, I see that one of my jobs began failing on May 22nd, 2018. The job fails with a stack trace resulting from a bad import, seen below. Traceback (most recent call last): File "/usr/local/lib/python2.7/dist

问题 I have a package that i have uploaded to test.pypi. I can install this package in a virtual environment on my machine without any issues using pip install --index-url https://test.pypi.org/simple/ package_name_here There is a list of requirements for the package in a 'requirements.txt' file, which are also included in 'install_requires' in the config dict fed to setup in setup.py. This works fine on my machine. When I try the same process within a clean virtual environment on one of my groups