I would emphasize that setup.py is the way to go. Requirements.txt was only
ever intended to be a way for a developer to provide a dependency chain so that
other developers could duplicate the environment if necessary. Today's common
usage was never originally intended.
The `extras_require`
Hi!
Thanks for all the useful responses!
I am basically working on libraries that will be distributed on PyPi,
such as https://github.com/HDI-Project/BTB/ and
https://github.com/HDI-Project/ATM/ (Auto Machine Learning and Model
Tuning libraries developed by Data to AI lab, in MIT).
It looks
On Mon, May 07, 2018 at 11:33:44AM +0300, Marius Gedminas wrote:
> On Mon, May 07, 2018 at 08:48:23AM +0200, Carles Sala Cladellas wrote:
> > Hello here!
> >
> > TL;DR: Should I use requirements.txt, or should I have my dependencies only
> > listed inside setup.py?
>
> Short answer: only setup.py,
On Mon, May 07, 2018 at 08:48:23AM +0200, Carles Sala Cladellas wrote:
> Hello here!
>
> TL;DR: Should I use requirements.txt, or should I have my dependencies only
> listed inside setup.py?
Short answer: only setup.py, unless you find a reason to also use a
requirements.txt.
Long answer:
The recommendation is typically: setup.py for libraries,
requirements.txt for applications. But you may also use requirements.txt
for specific tasks associated with a library, like building the docs.
Donald wrote a blog post which better explains what these two
formats
On 5/7/18 at 8:48 AM, car...@pythiac.com (Carles Sala Cladellas) pronounced:
But then I came across this, https://stackoverflow.com/a/28842733, which
recommends using a `dev` entry in `extras_require` and then using `pip
install -e .[dev]` to install them, which could be easily extended to
also
What kind of project is it? For example, is it a software library e.g. to
put on PyPI, or a website application for a company to run? The answer to
this question will help people answer your question because it has a big
impact on what practice will be best for you.
—Chris
On Sun, May 6, 2018 at
