3 ms·
You write "The documentation for pipenv and Python packaging didn’t make it clear early on pipenv was for applications, not libraries." The linked-to essay say
by eesmith 9y ago
You write "The documentation for pipenv and Python packaging didn’t make it clear early on pipenv was for applications, not libraries."
The linked-to essay says: "There is a misnomer that Pipenv is not useful for libraries. That is false. Try using $ pipenv install -e . and see what it does when you lock. It augments setup.py. I, as a library developer, find that extremely useful."
I can't help but conclude that the documentation doesn't make that clear because the author doesn't think it's true.
- pseudalopex 8y agoReitz is talking about development; everyone else is talking about packaging and distribution.
- eesmith 8y agoI confess that I don't understand the issues. Then again, I only last month migrated my tools from 'distutils' to 'setuptools', so I know I'm way behind the times. I have just now read https://docs.pipenv.org/advanced/#pipfile-vs-setuppy https://docs.pipenv.org/advanced/#pipfile-vs-setuppy on the topic and am still confused by the terminology. Eg, "Applications are different in that they usually are not depended on by other projects." I am used to writing command-line applications which are used as dependencies for other projects. But that is neither here nor there - no need to answer. Thanks for pointing out the nuance I did not recognize.