Update Pipfile.lock after update pipfile - pip

I have pipfile and Pipfile.lock in my project. I have manually updated one of the libraries in my pipfile
When I compile the code, I get an error saying that sha256 is not matching.
How do I update the Pipfile.lock so that this error doesn't occur.

Related

Unity: None of your spec sources contain a spec satisfying the dependency: `Firebase/Analytics (= 10.0.0)`

We are trying to use Firebase Analytics but when we build our Unity project we get a CocoaPods installation failure:
None of your spec sources contain a spec satisfying the dependency: `Firebase/Analytics (= 10.0.0)`.
You have either:
* out-of-date source repos which you can update with `pod repo update` or with `pod install --repo-update`.
* mistyped the name or version.
* not added the source repo that hosts the Podspec to your Podfile.
Ignoring ffi-1.13.1 because its extensions are not built. Try: gem pristine ffi --version 1.13.1
Ignoring json-1.8.6 because its extensions are not built. Try: gem pristine json --version 1.8.6
pod repo update output:
Updating spec repo `cocoapods`
$ /usr/bin/git -C /Users/josephhopkins/.cocoapods/repos/cocoapods fetch origin --progress
$ /usr/bin/git -C /Users/josephhopkins/.cocoapods/repos/cocoapods rev-parse --abbrev-ref HEAD
master
$ /usr/bin/git -C /Users/josephhopkins/.cocoapods/repos/cocoapods reset --hard origin/master
HEAD is now at 7b2edeb16678 [Add] SwiftCurrent 5.1.10
Updating spec repo `trunk`
CocoaPods 1.11.3 is available.
To update use: `gem install cocoapods`
For more information, see https://blog.cocoapods.org and the CHANGELOG for this version at https://github.com/CocoaPods/CocoaPods/releases/tag/1.11.3
We are using Unity 2020.3.8f1. We tried deleting the Library cache folder but error still happens. How do we fix this problem?
I was able to fix by deleting all Firebase related files and reinstalling.

pip install from local directory doesnt add [build-system] dependencies

In our project (Locust) we use setuptools_scm for versioning, so it is needed for all installations from local directory.
We used to have this specified in setup.py:
setup(
setup_requires=["setuptools_scm>=6.2"],
...
)
But we have upgraded to use setup.cfg and pyproject.toml
[build-system]
requires = ["setuptools_scm>=6.2", ...]
This works nicely in most cases, but it does not install setuptools_scm if someone does pip install -e . (it doesnt work for pip install . either but that is less important)
With no setuptools_scm installed the local version becomes 0.0.0:
~/git/locust pip install -e .
Looking in indexes: https://pypi.org/simple
...
Running setup.py develop for locust
Successfully installed locust-0.0.0
... and that makes me very sad.
What is the appropriate way make pip install setuptools_scm when installing from source?
I could of course add it as a regular dependency in setup.cfg, but that would make thousands of users download setuptools_scm even when it is not needed (when installing from PyPi)

pipenv install packages failes

I'm trying to install packages from a Pipfile with pipenv but I keep getting an error I don't know how debug.
pip --version
pip 18.1
pipenv --version
version 2018.10.9
The error I'm getting is:
pipenv install --dev --deploy
Courtesy Notice: Pipenv found itself running within a virtual environment, so it will automatically use that environment, instead of creating its own for any project. You can set PIPENV_IGNORE_VIRTUALENVS=1 to force pipenv to ignore that environment and create its own instead. You can set PIPENV_VERBOSITY=-1 to suppress this warning.
Installing dependencies from Pipfile.lock (917af8)…
An error occurred while installing backports-ssl-match-hostname==3.5.0.1 --hash=sha256:502ad98707319f4a51fa2ca1c677bd659008d27ded9f6380c79e8932e38dcdf2! Will try again.
🐍 β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰ 185/185 β€” 00:00:33
Installing initially failed dependencies…
Collecting backports-ssl-match-hostname==3.5.0.1 :00
Could not find a version that satisfies the requirement backports-ssl-match-hostname==3.5.0.1 (from -r /tmp/pipenv-qlbc3amj-requirements/pipenv-akfm2pt_-requirement.txt (line 1)) (from versions: )
No matching distribution found for backports-ssl-match-hostname==3.5.0.1 (from -r /tmp/pipenv-qlbc3amj-requirements/pipenv-akfm2pt_-requirement.txt (line 1))
☀ β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰β–‰ 0/1 β€” 00
Looking at the Pipfile.lock I can find the backports package defined as:
"backports.ssl-match-hostname": {
"hashes": [
"sha256:502ad98707319f4a51fa2ca1c677bd659008d27ded9f6380c79e8932e38dcdf2"
],
"version": "==3.5.0.1"
},
Running everything with the verbose flag, the backports package is a dependency from recurly which is in the Pipfile:
recurly = ">=2.8.6"
Downgrade your pip version to 18.0.0 while your pipenv shell is active
python -m pip install pip==18.0.0
It worked for me

Conda doesn't recognize package updated by PIP and link error(337)

Recently I use conda update --all to update all packages. But there is an error:
ERROR conda.core.link:_execute_actions(337): An error occurred while installing package 'conda-forge::wheel-0.30.0-py_1'.
So I update wheel by pip. After that I use conda update --all again while the error still remains. It looks like that conda doesn't know that the version of wheel has been 0.30 so that there is no need to install it.

How to avoid installing an "install_requires" package of a pip requirement?

When installing with pip from a requirements.txt file, is there a way to override a requirement's dependencies which are installed due to being listed under install_requires in setup.py of the package?
My specific case is south being installed as a dependency of django-paypal, even though I'm using Django 1.8 so I don't want south installed - it just confuses django's own migrate command.

Resources