installing packages from git broken
See original GitHub issueFresh install:
$ pipenv --version
pipenv, version 3.3.6
Simple Pipfile:
$ cat Pipfile
[[source]]
url = "https://pypi.python.org/simple"
verify_ssl = true
[packages]
crayons = { git="https://github.com/kennethreitz/crayons.git", ref="v0.1.2" }
Creates what seems to me a valid lock file:
$ cat Pipfile.lock
{
"_meta": {
"hash": {
"sha256": "39b2447b7dd6976804de490321577a2db0f4fc4327e0795a93436ea69afad9a8"
},
"requires": {},
"sources": [
{
"verify_ssl": true,
"url": "https://pypi.python.org/simple"
}
]
},
"default": {
"crayons from git+https://github.com/kennethreitz/crayons.git@v0.1.2#egg=crayons": {
"hash": "sha256:a292b7ef29131345fd329ff5a94d1e2e59569be4dbd9fa8b99ff7114d72102a6",
"version": "==0.1.2"
},
"colorama": {
"hash": "sha256:a4c0f5bc358a62849653471e309dcc991223cf86abafbec17cd8f41327279e89",
"version": "==0.3.7"
}
},
"develop": {}
}
And now installing breaks:
$ pipenv install
No package provided, installing all dependencies.
Pipfile found at /[...]/Pipfile. Considering this to be the project home.
Installing dependencies from Pipfile.lock...
An error occured while installing!
Invalid requirement: 'crayons from git+https://github.com/kennethreitz/crayons.git@v0.1.2#egg=crayons==0.1.2'
It looks like a path. Does it exist ?
To activate this project's virtualenv, run the following:
$ pipenv shell
These are the versions in my env:
$ pip freeze
appdirs==1.4.0
blindspin==2.0.0
click==6.7
click-completion==0.2.1
colorama==0.3.7
crayons==0.1.2
delegator.py==0.0.8
Jinja2==2.9.5
MarkupSafe==0.23
packaging==16.8
parse==1.6.6
pew==0.1.26
pexpect==4.2.1
pipenv==3.3.6
pipfile==0.0.1
ptyprocess==0.5.1
pyparsing==2.1.10
pythonz-bd==1.11.4
requests==2.13.0
requirements-parser==0.1.0
resumable-urlretrieve==0.1.4
six==1.10.0
toml==0.9.2
virtualenv==15.1.0
virtualenv-clone==0.2.6
Leaving out the ref attribute makes no difference.
Providing the editable
flag leaves the package out of the lock file altogether:
$ cat Pipfile
[[source]]
url = "https://pypi.python.org/simple"
verify_ssl = true
[packages]
crayons = { git="https://github.com/kennethreitz/crayons.git", ref="v0.1.2", editable=1 }
produces:
$ cat Pipfile.lock
{
"_meta": {
"sources": [
{
"url": "https://pypi.python.org/simple",
"verify_ssl": true
}
],
"requires": {},
"hash": {
"sha256": "fa6b6a1618451ef360028928588f70f6b3964f4dc8b0d371fb71a355b334abee"
}
},
"develop": {},
"default": {}
}
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:21 (12 by maintainers)
Top Results From Across the Web
How to fix broken packages using the Command Line · GitHub
To clear out the broken packages use the command: sudo aptitude -f. It brings up a beautiful interface to search, navigate, install, update...
Read more >Can't Fix Broken Git installation on Ubuntu - Stack Overflow
I resolved the problem with the commands below: sudo apt-mark hold git sudo dpkg -r --force-depends git. And then install git-core
Read more >Package marked as broken, install from Github source?
I have a package that fails to build in my Poudriere repository, databases/postgresql-plv8js, due to it being marked as broken.
Read more >Broken Git installation on my Mac. How do I fix it? - Ask Different
To debug this, start by executing: type -a git. and. echo $PATH. In OP's case, running the above commands gave the following output ......
Read more >what i need to fix to install git. that's the answer ... - Ask Ubuntu
Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: git : Depends: ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for opening this @evertlammerts, we realized last week that this was regressed in the 3.3.X releases of pipenv. I’m currently working on getting this functionality reintegrated, so bear with me while we get this tidied.
Since we hadn’t gotten around to making a formal issue for this, we’ll use this one to track this going forward.
This should be resolved with #242 and released in 3.5.0.