STINNER Victor added the comment:
This issue seems to be controversial. I suggest to open a discussion at te
Packaging forum https://discuss.python.org/c/packaging rather than using the
bug tracker. I close this issue.
--
nosy: +vstinner
resolution: -> out of date
stage: needs
Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
versions: +Python 3.5 -Python 3.2, Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1635217
___
Éric Araujo mer...@netwok.org added the comment:
Again, the stdlib docs do not document third-party projects. Use the pip doc
if you use pip.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1635217
anatoly techtonik techto...@gmail.com added the comment:
I am trying to get what's the proposed standard for users right now? How are
you going to define dependencies in distutils2?
--
___
Python tracker rep...@bugs.python.org
Éric Araujo mer...@netwok.org added the comment:
Right now the standard (i.e. official) way is Requires, which is unusable; the
de facto standard (but not blessed by any PEP) is setuptools’ install_requires.
The new standard is documented in d2 docs and there will be examples
Éric Araujo mer...@netwok.org added the comment:
It may be good to document that requires/provides/obsoletes are effectively
unused.
It is not appropriate for stdlib doc to talk about install_requires, which is
specific to setuptools, and it’s better to talk about the new standard fields
anatoly techtonik techto...@gmail.com added the comment:
PEP 345 completely misses practical side. I need to specify dependencies for my
package, so that people who checked out the source code could run `pip install
.` in virtualenv and get everything fetched.
People reading the docs are more
