Tarek Ziadé wrote:
The practice in the community is to create the long_description field
using a separate reStructuredText file
and reaching it in setup.py like this for example:
long_description = open('README.txt').read()
Having a callable that provides this feature in the template allows writing:
"""
[setup.cfg]
long_description: {$ long_description('README.txt') $}
"""
Exactly, so why have this complicated templating nonesense rather than
just having:
[setup.cfg]
long_description_path: README.txt
long_description_path can't be added in the final PKG-INFO because
we want a self-contained metadata static file that doesn't require an
extra resource (like an external file)
Why this requirement?
If this really is that strict, then only allow long_description_path in
setup.cfg.in....
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
