On Tue, Aug 18, 2009 at 11:47 AM, Ben Finney<[email protected]> wrote:
> Jeff Rush <[email protected]> writes:
>
>> The long_description field is also a reStructuredText field and as
>> such, for the developer to preview it during its composure, it needs
>> to be left-aligned. While a developer -could- cut/paste it into a
>> separate text file each time he wants to test preview it, that would
>> be annoying.
Right, following my template proposal (setup.cfg.in), in your case,
the template engine
would require a feature to be able to inject a file in setup.cfg
>
> I get my ‘description’ and ‘long_description’ field not directly from a
> text file, but from the package docstring. Following the usual docstring
> interpretation conventions as per PEP 257, I trim all common leading
> indentation from non-blank lines:
>
> import textwrap
> import foopackage
>
> short_description, long_description = (
> textwrap.dedent(d).strip()
> for d in main_module.__doc__.split('\n\n', 1))
>
As said earlier in this thread, these could be pre-generated in you
release process,
in a static file that can be used by setup.cfg.in without requiring
your code to be shipped
to be able to get static metadata.
_______________________________________________
Distutils-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/distutils-sig
