Skip to content

description-content-type metadata field is not documented #1236

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
cmcginty opened this issue Dec 19, 2017 · 9 comments
Closed

description-content-type metadata field is not documented #1236

cmcginty opened this issue Dec 19, 2017 · 9 comments

Comments

@cmcginty
Copy link

cmcginty commented Dec 19, 2017

I can't find any docs that explicitly state what the kwarg value for "description-content-type" is supposed to be. If I find it i'll close the ticket.

==========

long_description_content_type

I guess this is the value, but where are the docs for this?

'long_description_content_type',

@xnuinside
Copy link

xnuinside commented Jan 17, 2018

@cmcginty, http://setuptools.readthedocs.io/en/latest/setuptools.html#metadata - inside this doc info about type of this variable long_description_content_type

what is this, you can find here:
https://packaging.python.org/specifications/core-metadata/#description-content-type-optional (link to this page was provided inside #1075

@cmcginty
Copy link
Author

cmcginty commented Jan 17, 2018

Thanks for the links.

Setup tools has a description and long_description field, so I think it's still ambiguous that Description-Content-Type applies to long_description_content_type in setuptools. Can the setuptools docs be modified to link to PyPA packaging docs you provided?

IMO I think the PyPA distinction between summary and description is clear enough. Why does setuptools deviate from the PyPA guidelines? So now description sets the Summary: field and long_description sets the Description: field. Should I open another bug for this one?

@jaraco
Copy link
Member

jaraco commented Feb 3, 2018

Can the setuptools docs be modified to link to PyPA packaging docs you provided?

Yes. Please send a PR.

Why does setuptools deviate from the PyPA guidelines?

Mainly for historical reasons. It probably evolved this way, refining the purpose as the use-cases were clarified. And while the naming in the metadata has evolved more rapidly, the API for Setuptools has evolved less so.

Should I open another bug for this one?

Perhaps, and especially if you wish to develop a PR to help transition the project from the current naming to a new one. The trick becomes doing that without breaking every build. There's probably a 2 year transition period where both names would need to be supported. If you have the patience for an effort like that, or have other ideas on how this change could be made with less trouble, then by all means, let's do it!

@brainwane
Copy link
Contributor

A contributor added info in pypa/packaging.python.org#457 to https://packaging.python.org/tutorials/distributing-packages/ that may be helpful here.

@pganssle pganssle added Needs Triage Issues that need to be evaluated for severity and status. help wanted good first issue Needs Implementation Issues that are ready to be implemented. documentation and removed Needs Triage Issues that need to be evaluated for severity and status. labels Oct 19, 2018
@vitoace
Copy link
Contributor

vitoace commented Oct 27, 2018

I will be working on it with Gene.

@genemat-zz
Copy link

Hi I'm Gene this is my first github project

@pganssle
Copy link
Member

Was this fixed in 6b65f6b?

@jaraco
Copy link
Member

jaraco commented Oct 27, 2018

That links to #1075.

@pganssle
Copy link
Member

Closed in #1539

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants