Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Doesn't support -e git+https:// type links
See original GitHub issueHey @kennethreitz, was listening to you on Talk Python To Me so I played around with pipenv. I’m filing a couple of issues including this one.
Even when running pipenv lock --requirements there doesn’t seem to be a way for these types of links to be generated from the requirements.txt file
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (7 by maintainers)
Top Results From Across the Web
Git fatal: protocol 'https' is not supported - Stack Overflow
If you are using a Git Bash: Do not paste the link by pressing Ctrl + V . You can just type git...
Read more >4.1 Git on the Server - The Protocols
The negative aspect of SSH is that it doesn't support anonymous access to your Git repository. If you're using SSH, people must have...
Read more >About remote repositories - GitHub Docs
A remote URL is Git's fancy way of saying "the place where your code is stored. ... For example, you'd type the following...
Read more >Unable to clone Git repositories using the Eclipse Git Team ...
Symptom. Open the Git Repositories view (Window > Show View > Other... > Git > Git Repositories). Select to Clone a Git Repository....
Read more >Improving Git protocol security on GitHub | The GitHub Blog
We feel confident that rejecting these keys altogether will increase security with little or no user friction. We're also planning to remove ...
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 Free
Top 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
Just FYI, I’ve finally released 5.1.2, so this should be fixed going forward. Thanks again for your work @erinxocon and for everyone’s patience!
I can confirm this issue. When you are using
pipenv lock --requirementseverything is exported as expected, however when you create an environment fresh that only has a requirements file,pipenvwill convert the requirements file into a Pipfile, but it doesn’t translate custom VCS links properly. It just takes the egg name and puts ‘*’ as the version instead of creating a subsection. I ran into the same problem. I’m working on a patch!