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.

Setup.py vs Pipfile

See original GitHub issue

My current strategy is to add my requirements (generally pinned) to setup.py and then have a requirements.txt file that specifies particular versions.

The workflow I’ve migrated to is: pipenv install "-e ." and pipenv install "-e .[test]" --dev. Looking at requests’s Pipfile this seems to be the same approach, with a couple caveats / notes:

the dev dependencies contains more installation requirements than requests[text]. This is probably fine, as I assume it means you want even more packages installed when developing requests(?).
your dependencies are "-e ." = {extras = ["socks"]}. This appears to be handcoded, as my output looks like: "e1839a8" = {path = ".", editable = true}. Is the first approach better? I.e. should I be manually adding "-e ." = {} to my dependencies?

Issue Analytics

State:
Created 6 years ago
Reactions:2
Comments:8 (8 by maintainers)

Top GitHub Comments

5reactions

dfeecommented, Sep 25, 2017

Can you help me understand what “e1839a8” means? At first glance it looks like the short hash of something. But I’m not sure what.

0reactions

kennethreitzcommented, Sep 25, 2017

it’s effectively nice filler content, that ensures no collisions.

Top Results From Across the Web

Pipenv vs setup.py - Stack Overflow

Thus, pipenv vs setup.py is a wrong formulation. They can't be against each other.

Simplifying Python Builds. A Single Source of Truth for…

We'll use the standard setup.py for building Python libraries and pipenv for managing ... Maintain my dependencies in both the Pipfile and the...

How to keep setup.py install_requires and Pipfile in sync #1263

In an ideal world, Pipfile replaces setup.py's install_requires , and be used to specify virtual dependencies, while the lock file is used to ......

Pipenv: A Guide to the New Python Packaging Tool

Pipfile; Represents the concrete requirements for your package; Pull the minimally required dependencies from setup.py by installing your package using ...

pipenv-setup - PyPI

A beautiful python package development tool: sync dependencies in Pipfile or Pipfile.lock to setup.py . Never need again to change dependencies manually in ......