From a9d403889def99bdb1a1d02b47b8247b3af0817a Mon Sep 17 00:00:00 2001 From: Igor Starikov Date: Wed, 12 Apr 2017 12:06:37 +0700 Subject: Docs: notes on setup.cfg and ez_setup (see # 1006) --- docs/setuptools.txt | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/setuptools.txt b/docs/setuptools.txt index bf5bb8ce..eb9fdbd3 100644 --- a/docs/setuptools.txt +++ b/docs/setuptools.txt @@ -1176,6 +1176,8 @@ Distributing a ``setuptools``-based project Using ``setuptools``... Without bundling it! --------------------------------------------- +.. warning:: **ez_setup** is deprecated in favor of PIP with **PEP-518** support. + Your users might not have ``setuptools`` installed on their machines, or even if they do, it might not be the right version. Fixing this is easy; just download `ez_setup.py`_, and put it in the same directory as your ``setup.py`` @@ -2277,6 +2279,11 @@ New in 20.1: Added keyring support. Configuring setup() using setup.cfg files ----------------------------------------- +.. note:: New in 30.3.0 (8 Dec 2016). + +.. important:: ``setup.py`` with ``setup()`` function call is still required even + if your configuration resides in ``setup.cfg``. + ``Setuptools`` allows using configuration files (usually `setup.cfg`) to define package’s metadata and other options which are normally supplied to ``setup()`` function. -- cgit v1.2.3